tobihagemann/turbo / codex/skills/implement-backlog
implement-backlog
VerifiedValidate .turbo/backlog.md entries, recommend a working set, and run one lane: direct, investigate, or plan. Use when the user asks to "implement the backlog" or "implement improvements".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 17.2 KB |
| references/direct-lane.md | markdown | 842 B |
| references/investigate-lane.md | markdown | 1.9 KB |
| references/plan-lane.md | markdown | 864 B |
references/investigate-lane.md
View on GitHub# Implement Backlog: Investigate Lane
Diagnose each working-set entry via `$investigate`, then apply the concluded fixes via `$implement`.
The working set is the entries the user confirmed in SKILL.md Step 3.
## Task Tracking
Use `update_plan` to track each phase, restating SKILL.md's remaining steps and any remaining steps of a parent workflow alongside them:
1. Run `$investigate` skill for each working-set entry
2. Run `$implement` skill for the concluded fixes
## Phase 1: Run `$investigate` Skill for Each Working-Set Entry
Before starting the loop, add one sub-task per entry in the working set (e.g., `Investigate: <summary>`). Mark each sub-task `in_progress` before the corresponding `$investigate` run and `completed` after.
For each entry in the working set, run the `$investigate` skill. In the problem statement passed to `$investigate`, include the entry's summary and rationale, then append a note that this is a backlog entry likely to be a symptom and that `$investigate` must run `$consult-claude` regardless of how many hypotheses surface.
If `$investigate` surfaces complexity that exceeds a single-session fix (multi-subsystem change, architectural decision), stop that entry and re-classify it as `plan` (leave it in the backlog for a future run).
## Phase 2: Run `$implement` Skill for the Concluded Fixes
**When no investigation concluded a fix**, state that and leave `$implement` unrun.
**Otherwise**, in the turn that invokes `$implement`, write out each concluded fix as an explicit bullet: summary + files + change description. Being explicit matters here because `$investigate`'s earlier output has likely displaced continuation context, so `$implement` needs a fresh, self-contained description. Then run the `$implement` skill.
Then call `update_plan` to mark this step completed and continue with the next step of the active workflow.
## Rules
- Run the close-out only once (inside `$implement` in Phase 2), not once per investigation.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |