implement-feature

Imported from wpasc/toolbox (.agents/skills/implement-feature/SKILL.md). Install upstream with npx skills add wpasc/toolbox --skill implement-feature. Copyright stays with the author.

implement-feature (Codex Runtime Skill)

Canonical source: skills/implement-feature/SKILL.md

This file is self-contained for Codex runtime. Shared behavior belongs in the canonical source skill; regenerate this file after changing the source.

Codex Runtime Notes

• Prefer AGENTS.md for root guidance. Treat CLAUDE.md only as supplemental fallback when older Claude-specific text in the inlined body requires it.
• Use Codex-native tools and .agents/skills/; translate older Claude coordination wording in the body into explicit user requests, current tools, or durable artifacts when the workflow requires them.

Classification

• Migration category: Generate as Codex runtime skill
• Rationale: Workflow or reference guidance is useful in Codex as a self-contained runtime skill.

Skill-Specific Notes

• Prefer modern Codex planning, subagent, and verification patterns while preserving the source phase structure. Use explorer, worker, or default roles in prose, not fake invocation syntax.

Inlined Skill Body

Feature Implementation Workflow

Sequence a substantial feature through five phases. Each phase has an exit criterion; do not advance past a phase you cannot exit honestly.

Phases

1. Scout -- map the territory with read-only subagents: project type, conventions, integration points, prior art for similar features. Exit: you can name the files you will touch and the patterns to follow.

2. Clarify -- state assumptions, ask at most 3 focused questions (prefer options over open-ended), and confirm scope back to the user. Exit: testable acceptance criteria the user has confirmed, plus explicit out-of-scope items. If the user says "just do it", record the defaults you chose as assumptions.

3. Plan -- ordered steps, each paired with its own verification check. Decompose independent work directly with native subagents; keep sequential work in the main context. Exit: every acceptance criterion maps to at least one step.

4. Implement -- test-first per test-driven-development. Follow existing patterns exactly; no refactoring of unrelated code; nothing beyond the spec. Run the affected tests before calling the phase done. Exit: new tests pass and existing tests still pass.

5. Review -- review the diff against the spec per code-review. Fix and re-review; if convergence fails after about 3 cycles or the implementation has diverged from the spec, stop and report rather than force it through. Exit: review passes with fresh verification evidence (verification-before-completion).

Rules

• Never auto-commit; present the verified diff and let the user commit.
• Surface tradeoffs and simpler alternatives during Clarify, not after Review.
• If a later phase invalidates an earlier phase's output (wrong assumption, missing integration point), return to that phase explicitly -- do not patch around it.