Feature Forge — Development skill for Claude Code

Feature Forge

**A full feature lifecycle for coding agents: crucible, brief, wireframe, architecture, plan, TDD build loop, adversarial review, ship. Docs are the source of truth, sub-agents do the work, and a human reviews at three gates.**

[](LICENSE) [](#status) [](#status)

Status

**Coming soon.** Watch this repo if you want to know when the code lands.

Why

Agents are good at writing code and bad at deciding what to write. Handed a one-line feature request, an agent will start editing files inside of a minute, and you find out three hours later that it built the wrong thing, or built the right thing with no tests, or quietly rewrote a module nobody asked it to touch.

The Feature Forge puts the thinking before the typing. A feature moves through phases, and each phase produces a document that the next phase has to answer to. Different sub-agents read those documents from different angles: a PM challenges the brief, a security reviewer challenges the architecture, an engineering manager challenges the plan, and an adversary reads everyone else's findings and goes looking for what they all missed.

The human reads a compiled HTML page at three gates and comments in the browser. Everything else runs on its own.

The lifecycle

1. Setup. Branch and worktree first, so no doc and no commit ever lands on the shared tree.
2. Crucible. Challenge the idea before writing anything down. Is this worth building?
3. Brief. What we're building and why. Problem, user, requirements, success criteria. No architecture.
4. Wireframe. Interactive wireframes for anything a person looks at. Human gate.
5. Architecture. The technical design, with alternatives considered. No step-by-step plan.
6. Plan. Ordered, dispa