forge

name

forge

description

Spec-driven autonomous development workflow. When the user wants to plan a non-trivial change, build it autonomously, or run a skeptical review of completed work, use the /forge:* commands. /forge:contract writes a rich spec through code exploration, library research, and gray-area discussion. /forge:auto loops build→evaluate→fix until the contract's success criteria are met. /forge:build implements one chunk against an existing contract. /forge:evaluate spawns a fresh-context sub-agent to verify work skeptically. /forge:parallel decomposes large work into independent streams across git worktrees. /forge:pulse generates a development-health report. /forge:status lists active contracts and their progress. The pattern: scout the code → research the libraries → discuss gray areas → write a contract → build with evidence → evaluate skeptically. Activates when the user mentions building a feature non-trivially, asks for spec-driven dev, or invokes any /forge:* command.

Forge

Spec-driven autonomous development workflow for Claude Code. Forge treats the spec as the highest-leverage artifact: a build with a thorough spec gets the right thing on the first try; a build with a thin checklist passes checkboxes and misses intent.

When this skill activates

• The user wants to build a non-trivial change and would benefit from a spec rather than coding directly
• The user invokes any /forge:* command
• The user says things like "spec this out", "let's plan this properly", "I want autonomous build", "skeptical review", "decompose this into parallel streams"

For trivial changes (typo fixes, single-line config edits, obvious bugs), don't invoke forge — just do the work.

The commands

Command	Use when
/forge:contract <task>	You have a feature/change idea and want a thorough spec before any code. Most-used command.