Stats
Actions
Tags
From ticket-flow
Implement an approved plan from thoughts/shared/plans/ phase-by-phase, ticking checkboxes and stopping when reality diverges from the plan. Use after a plan is approved, or via /ticket-flow:implement.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ticket-flow:implementThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Implement the plan at: **$ARGUMENTS** (a path under `thoughts/shared/plans/`).
Implement the plan at: $ARGUMENTS (a path under thoughts/shared/plans/).
Only run this AFTER a human has approved the plan.
- [x] checkmarks (resume where it left off).Plans are carefully designed, but reality is messy. Follow the plan's intent while
adapting. Implement each phase fully before the next, and tick its - [x] boxes as you go.
If the code doesn't match the plan, STOP and ask rather than improvising:
Issue in Phase [N]:
Expected: [what the plan says]
Found: [actual situation]
Why it matters: [explanation]
How should I proceed?
When all phases are done, run the plan's automated success criteria and confirm they pass before handing off to validation.
npx claudepluginhub alexanderop/ticket-flowGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.