← ClaudeAtlas

forgelisted

Turn a PRD into a grounded tech-spec draft - ingest the WHY, ground in the code it lands in, surface the design forks for you to decide, then draft a spec structured to survive review. Pairs with gadfly (the critic) - forge authors, gadfly tempers. A grounded draft, not a finished spec.
sgtlaugh/skills · ★ 2 · Code & Development · score 76
Install: claude install-skill sgtlaugh/skills
# /forge - author a spec from a PRD, then temper it A blacksmith's forge: raw PRD in, drafted, stressed by gadfly, hardened spec out. forge writes the first grounded draft of a tech spec from a product requirements doc, hands it to **gadfly** for an independent adversarial pass, then revises once. An LLM drafts plausible-but-wrong architecture confidently, and a spec gets built. forge is safe only because it grounds every design claim in code (or tags it `[assumed]`), never decides a product fork for you, and lets gadfly - not itself - be the critic. The result is "survived one gadfly pass", never "correct". If you already have a human draft, skip forge and run gadfly. ## Usage ``` /forge <prd-path> # local PRD: .md / .txt / .pdf / .docx /forge <prd-url|page-id> # Confluence PRD /forge <prd> --repo <hint> # the repo(s) the feature lands in (else forge discovers) /forge <prd> --no-temper # draft only - skip the gadfly temper pass ``` Cost: ingest + ground + draft + a gadfly pass + revise, roughly 1.5-2x a gadfly run (measured $5.4-6.6 with the temper pass; gadfly alone $2.2-4.6). `--no-temper` skips gadfly. For a union of several critiques, run `/jury gadfly <forge-output> --prd <prd>` yourself on the finished draft. ## Who answers the forks Forks go to a human through `AskUserQuestion`. **When no human can answer** - a headless `claude -p` run, a subagent, a prompt that says so, or `AskUserQuestion` is unavailable or errors - never stop on a questi