Skill Claude CodeCodex
Use for SpecForge Stage 3 — implement strictly from 04-execution-spec.md. Treat the spec as the single source of truth; if it is not in the spec it does not exist; ask on ambiguity instead of guessing; follow the project's own AGENTS.md/CLAUDE.md for code style.
Skill Claude CodeCodex
Use for SpecForge Stage 1 — solution-space exploration with a high-reasoning model. Clarify the problem, propose 2-4 approaches, compare trade-offs, let the user choose, then write 02-solution-options.md and 03-solution-hld.md. No code, no spec generation.
Skill Claude CodeCodex
Use for SpecForge Stage 2 — generate the Execution-Spec. Consume 03-solution-hld.md, fill the 04 template with final decisions only (no alternatives), then self-check with sf-validate.sh before handoff to the executor.
Skill Claude CodeCodex
Use when starting or resuming a SpecForge task — the orchestrator that scaffolds the task directory, detects the current phase, and routes to the explore, spec, or execute stage skill. Triggers on "specforge", "execution spec", "spec-driven implementation".
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: