tomevault-io Implement Step
Execute the next incomplete step from a tracking document.
Usage
/implement-step CLEANUP.md # Implement next step from CLEANUP.md
/implement-step docs/PLAN.md # Any path to a tracking doc
/implement-step TODO.md step 3 # Target a specific step
Arguments
| Argument | Description |
|---|---|
| First arg (required) | Path to the tracking document |
step N |
Optional: target a specific step number instead of the next incomplete one |
Workflow
- Read the tracking document and identify the next incomplete step (or the specified one)
- Explore the relevant files to understand the change needed
- Implement the actual code changes — do NOT just write a plan or analysis
- Run tests —
bin/wealthbox rspecfor Ruby,bin/wealthbox exec yarn testfor JS (adjust paths to relevant specs) - Run linters —
bin/wealthbox exec bundle exec rubocop -aon changed Ruby files,bin/wealthbox exec yarn tsc --noEmitfor TypeScript - Fix any test failures or lint errors before proceeding
- Update the tracking document to mark the step as done
- Summarize what was changed and what the next step would be
Critical Rules
- Execute, don't plan. The whole point of this skill is to make code changes, not produce analysis. If you find yourself writing a plan instead of editing files, stop and start editing.
- One step at a time. Complete one step fully before moving to the next. Don't batch multiple steps.
- Stop on ambiguity. If a step is unclear or requires an architectural decision, explain the options and stop — don't guess.
- Never commit with failing tests. If tests fail and you can't fix them, report the failure and leave the step incomplete.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.