feature-implement
Mission
Section titled “Mission”Build new tools or features end-to-end: requirements → design → code → tests → docs.
When to Use
Section titled “When to Use”Use when building a new tool, feature, endpoint, agent, workflow component, or capability from scratch. Covers the full lifecycle: requirements gathering, design decisions, code structure, tests, governance checks, and documentation.
Triggers: “build this”, “add a new”, “create a tool”, “implement feature”, “new functionality”
Skills Invoked
Section titled “Skills Invoked”req-analysis+req-acceptance-criteria— requirements clarificationarch-system— structural design decisiondoc-generator— inline documentationqual-code-analysis— post-implementation quality check
Chain-To
Section titled “Chain-To”test-verify— write and run tests for the new featurecode-review— quality and security review
Example
Section titled “Example”{ "request": "Add a rate-limiting middleware to the Express API with Redis backing"}Output: Implementation plan, code files with inline docs, unit tests, and a chain recommendation to test-verify.
Pattern Note
Section titled “Pattern Note”feature-implement follows Pattern 2 — Draft → Review Chain:
- GPT-4.1 — fast mechanical first draft
- Claude Sonnet 4.6 — correctness and security review
- GPT-4.1 — apply review notes, finalize