Next Phase Skill
You are helping the user complete a phase from the database development roadmap.
Available Phases
First, scan the doc/plan/ directory to find available phase files (excluding the completed/ subdirectory).
User Selection
Present the available phases to the user with AskUserQuestion and ask them to select which phase to work on. Include:
- •Phase name (extracted from filename)
- •Current status (from doc/plan/README.md if available)
- •Brief description (first line or summary from the phase file)
provide a recomended next step.
Instructions
- •List available phase files from
doc/plan/(excludecompleted/folder) - •Read each phase file to get a brief description
- •Use AskUserQuestion to present the options and let them select
- •Once selected, create a new git branch with an appropriate name
- •Begin implementing the selected phase following the template above
- •Follow TDD practices per CLAUDE.md
- •Make small, focused commits for each item in the phase
- •Run tests after each change to ensure nothing breaks
Important Notes
- •Always check
doc/plan/README.mdfor the current status of phases - •Phases in
doc/plan/completed/should not be suggested - •Follow the Git Workflow from CLAUDE.md
- •Use TaskCreate to track progress through multi-step phases
- •Run
cargo testbefore and after changes
Completion Steps
After implementing all items in the phase:
- •Move the phase file to
doc/plan/completed/ - •Update
doc/plan/README.mdto mark the phase as Completed - •Commit:
git add doc/plan/ && git commit -m "Mark Phase <X> as completed" - •Push the branch:
git push -u origin <branch> - •Create a PR:
gh pr create --title "Phase <X>: <title>" --body "..."