Forge Plan

Orchestrate skills across 4 phases to go from raw idea to implemented, reviewed code. Heat (brainstorm) + pressure (grill) + quench (harden) + use (execute).

Do NOT enter Claude Code plan mode. This skill manages its own phased workflow with write operations in every phase. Plan mode would block file writes needed by brainstorming (spec), writing-plans (plan file), grill-me (plan updates), and execution (code).

Assumes you're already in a git worktree or feature branch. This skill does not create or manage worktrees.

Announce at start: "I'm using forge-plan to run the full pipeline: Design → Stress-Test → Harden → Execute."

Use AskUserQuestion for ALL user-facing decisions — brainstorming design choices, grill-me questions, harden-plan findings, domain skill confirmation, and skip confirmations. Always present options as cursor-selectable choices, not plain text questions.

Do NOT commit during the pipeline. All git commits are done manually by the user after the pipeline completes. Override any sub-skill instructions that include commit steps (brainstorming spec commit, writing-plans plan commit, execution task commits).

Usage

/forge-plan <issue-url-or-description>
/forge-plan --skip-brainstorm <plan-file-path>