pkuppens/plan
skills/plan/SKILL.md
Breaks work into tasks, estimates, dependencies, branch strategy. Ensures implementation plans include feature-branch workflow and completion through PR with CI validation. Use when creating implementation plans, decomposing issues, or in plan mode.
testing
Updated Apr 17, 2026
$ install --global
skillsauthnpx skillsauth add pkuppens/pkuppens planInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 7:58 AM11.6s3 files scanned
SKILL.md
- name:
- plan
- description:
- Breaks work into tasks, estimates, dependencies, branch strategy. Ensures implementation plans include feature-branch workflow and completion through PR with CI validation. Use when creating implementation plans, decomposing issues, or in plan mode.
Plan
Decomposes work into tasks, dependencies, and branch strategy per SKILL_TREE §6. Plans must include validation before implementation, then the full workflow through PR and CI.
When to use
- Creating an implementation plan from an issue or task
- Plan mode (agent produces a plan before implementation)
- Decomposing work into ordered subtasks
Phase 1 — Validate (before any implementation)
Before creating branches or editing code:
- Check duplicates — Was this already implemented (fully or partially)? See issue-check-duplicates; search codebase,
git log, merged PRs. - Purpose alignment — Does the issue align with project goals? See issue-purpose-alignment.
- Work-down — What code, tests, or related issues exist? Which components, modules, or ADRs apply? See issue-work-down.
- Acceptance criteria — Are they clear and testable? See issue-acceptance-criteria.
- Architecture — Which components/sub-components exist? Must anything be added or inspected? Consult architecture docs and architecture-consult if placement is unclear.
Stop if the issue is obsolete, duplicate, or not ready. Do not proceed to implementation until validation is complete.
Phase 2 — Implementation workflow (mandatory in plans)
Every implementation plan must include these steps:
- Create feature branch and implement — Branch from
mainbefore any edits. Use a branch prefix per repo convention:feature/NNN-…,hotfix/NNN-…,chore/…,epic/…. See plan-branch-strategy. Execute all plan tasks on this branch; never implement onmain. - Quality gate — Run repo quality checks before commit: lint, format, tests. See quality-gate.
- Commit and push — Conventional commit with issue reference. See integration-commit.
- Open PR — Create PR linking to issue. See integration-pr.
- CI validation — Plan must include waiting for or verifying CI before considering work complete. Strategies vary by project: e.g. unit tests on PR, integration suite at merge to
main; or single pipeline on PR. Check.github/workflows/or equivalent for the repo’s setup. Confirm N/A for markdown-only repos.
Summary: Validate first; work from a feature branch; complete through PR; do not stop until PR is open and CI has validated (or N/A).
Optional: V-model and brownfield
When the project or issue calls for traceability (pairing specs/design with tests), follow v-model. On an existing codebase, default to touch-driven v-model-retrofit: strengthen tests and minimal docs only for the surfaces changed in this issue unless the user or issue explicitly requests a wider retrofit (retrofit:explicit).
Sub-skills
| Sub-skill | Use when | |-----------|----------| | plan-tasks (6.1) | Decomposing into ordered subtasks | | plan-dependencies (6.2) | Identifying task dependencies and critical path | | plan-branch-strategy (6.3) | Selecting branch prefix and creating feature branch |
Integration
- Feeds into architecture or design-consult when placement needed.
- Implementation follows implementation-construction.
- Completion flow: quality-gate → integration.
- See COOPERATION.md for issue → implementation → integration flow.
Related Skills
pkuppens/sync-branch
testing
VerifiedTrustedCommunity
Syncs remote default branch locally (checkout, fetch --prune, pull) and returns to the previous branch when it still exists. Reports stashes and worktrees not yet handled. Use when the user asks to sync main, update default branch, fetch/pull origin, or run /sync-branch.
SKILL.mdUpdated Jun 6, 2026
pkuppens/azure-devops-work-items
tools
VerifiedTrustedCommunity
Creates, queries, updates, and links Azure Boards work items via az boards CLI. Use when filing ADO work items, running WIQL queries, or setting area path, iteration, tags, and assignee.
SKILL.mdUpdated May 29, 2026
pkuppens/azure-devops-repos
tools
VerifiedTrustedCommunity
Creates, reviews, and completes Azure Repos pull requests and branch policies via az repos CLI. Use when opening ADO PRs, setting required reviewers, or configuring build validation policies.
SKILL.mdUpdated May 29, 2026
pkuppens/azure-devops-pipelines
development
VerifiedTrustedCommunity
Guides Azure Pipelines YAML structure, build validation on PRs, and staged deployment with environments and approvals. Use when authoring azure-pipelines.yml or configuring CI/CD on Azure DevOps.
SKILL.mdUpdated May 29, 2026