Help us improve
Share bugs, ideas, or general feedback.
From dev-skills
Executes approved implementation plans phase by phase, producing working code with verification after each step. Useful when a clear plan exists and you want systematic, verified execution.
npx claudepluginhub teambrilliant/marketplace --plugin dev-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/dev-skills:implement-changeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Execute an implementation plan phase by phase, producing working code with verification at each step.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
Execute an implementation plan phase by phase, producing working code with verification at each step.
While implementing, consult references/software-design-philosophy.md for code-level design principles. Watch for red flags: shallow modules, information leakage, pass-through methods, temporal decomposition.
This skill expects an implementation plan (from /dev-skills:implementation-planning). If no plan exists, create one first — don't start coding without a plan.
Plan approval is the gate. Once a plan is approved, you have the authority to execute every phase to completion — do not check in between phases for confirmation. Verify, fix, proceed. Come back when the work is done, or when you hit something that genuinely needs the user's judgment.
Before pausing, classify the deviation:
Resolve and keep going (fix in scope, note it in passing, don't stop):
Pause and ask (these need the user):
The discriminator: does resolving this need information or judgment only the user has, and would guessing risk material rework? If no — resolve it and move on.
Read the plan completely. Read all files mentioned or related. Create a todo list tracking each phase.
If the plan has checkboxes, check for existing [x] marks — resume from first unchecked item.
For each phase:
When a deviation lands in the pause and ask lane (see Execution Contract), surface it:
Resolve-and-keep-going deviations don't need this — fix them in scope and note what you did. Reserve the stop for material mismatches.
Check the plan's Rollout & Rollback block before coding. Then:
See implementation-planning/references/rollout-primitives.md for the full decision tree.
After all phases complete:
Do:
Don't:
Use todos to track each phase, verification steps, and blockers.
Update the plan file checkboxes as you complete items:
- [x] Completed item
- [ ] Pending item
If picking up existing work:
[x] marks in the plan/dev-skills:qa-test for browser verification