Plan-first development workflow. Forces a research → plan → confirm → execute loop with atomic commits per unit. GSD-methodology equivalent for VS Code Copilot. Use when asked to implement, develop, build, create, or add a feature.
memory/decisions/ for prior decisions that constrain this taskmemory/patterns/ for established patterns to followPresent a structured plan in this exact format:
## Implementation Plan: <task name>
### Scope
- Files to create: [list]
- Files to modify: [list]
- Files to delete: [list — requires confirmation]
### Approach
<2-3 sentence explanation of the approach and why>
### Steps (in order)
1. [Step description] → commit: `type(scope): message`
2. [Step description] → commit: `type(scope): message`
...
### Assumptions
- [List any assumptions made]
### Out of Scope
- [What this plan explicitly does NOT include]
---
Reply `/approve` or describe changes to the plan.
STOP HERE. Do not write code until the user approves.
<hash>"After all steps complete:
Write a brief decision record if the task involved a non-obvious architectural choice:
memory/decisions/YYYY-MM-DD-<topic>.md — ADR if architecturalmemory/patterns/ — append to relevant pattern file if a new pattern emergedIf during execution you discover:
type(scope): imperative sentence (max 72 chars)feat, fix, refactor, docs, test, chore--no-verifyUse the memory-files MCP (filesystem) during Research phase:
memory/patterns/*.md for project patternsmemory/decisions/ for prior constraintsmemory/decisions/ if a decision was made