Skip to content

tobihagemann/turbo / claude/skills/implement

implement

Verified

Make an ad-hoc change no plan file governs, then run post-implementation QA. Use when the user asks to "just implement", "implement directly", "implement without a plan", or "apply the change".

FileKindSize
SKILL.mdskill md9.7 KB
references/step-implementer.mdmarkdown2.0 KB

references/step-implementer.md

View on GitHub
# Step Implementer Guidelines

Implement one Implementation Step of a plan. Other subagents implement the steps before and after it in the same working tree. The prompt names the plan, the step, what earlier steps already changed and left for this one, the skills to load, the checks to pass, and any cap on further verification.

## Process

1. Invoke `/code-style` via the Skill tool, then each skill the prompt names.
2. Read the plan file, then every file the step names. Read further files as the work calls for them.
3. Implement the step as the plan writes it. Do only this step's work: build on what earlier steps applied without redoing or reverting it, and leave later steps unimplemented.
4. Run the checks the prompt names and fix what they report.
5. Report in the format below.

## Rules

- Re-run the named checks as often as fixing them takes. Keep any further verification within the cap the prompt sets. When the cap is spent and doubt remains, report the doubt in place of running more.
- Run long work as a series of bounded commands. A message from the session that spawned you arrives between commands: act on it before starting the next one.
- Put a time limit on every wait, including a loop that polls for a condition, and stop every background command you started before reporting.
- When the plan's design cannot be implemented as written, stop and report what blocks it. Record any smaller departure under Deviations.
- Leave the result uncommitted in the working tree: no `git commit`, `git push`, `git stash`, or branch switch.
- Keep `.turbo/` content (filenames, acceptance criteria, step numbers, headings) out of code and comments.

## Report Format

```markdown
## Step <identifier>

**Status:** <done | blocked: what blocks it>
**Files:** <paths created, changed, or removed>
**Deviations:** <each departure from the plan, why, and whether it needs a decision>
**Checks:** <each check run and its result; further verification runs used against the cap>
**Unverified:** <what the checks leave unproven>
```
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall