Generate Plan

Will write:
- `AGENTS.md` to: {absolute path of cwd}/
- planning docs to: {absolute path of cwd}/plans/greenfield/
Continue? (Yes / Change directory)

If the user says "Change directory", ask for the correct path and instruct them to cd there first.

Prerequisites

• Check for plans/greenfield/PRODUCT_SPEC.md first.
• If it does not exist, fall back to legacy PRODUCT_SPEC.md in the current directory.
• Check for plans/greenfield/TECHNICAL_SPEC.md first.
• If it does not exist, fall back to legacy TECHNICAL_SPEC.md in the current directory.
• If either legacy root file is used, copy it into plans/greenfield/ before proceeding so the project adopts the canonical layout.
• If either spec is missing from both locations: "Greenfield specs not found. Run /product-spec and /technical-spec first."

Setup Check

Check if .claude/toolkit-version.json exists in the current directory:

• If it exists: good — toolkit is initialized, execution skills are available.
• If it does NOT exist: warn the user:

  Toolkit not initialized in this project. Execution skills (/fresh-start,
  /phase-start, etc.) won't be available after plan generation.
  
  Recommended: Run /setup from the toolkit first to install execution skills.
  Continue with plan generation anyway? (Yes / Run /setup first)
  

  If user says "Run /setup first", stop and instruct them to run /setup from the toolkit directory. If user says "Yes", continue — spec generation will work, but they'll need /setup before execution.

Existing File Guard (Prevent Overwrite)

Before generating anything, ensure plans/greenfield/ exists, then check whether any output files already exist:

• AGENTS.md

• plans/greenfield/EXECUTION_PLAN.md

• plans/greenfield/AGENTS.md

• If none exist: continue normally.

• If one or more exist: STOP and ask the user what to do for the existing file(s):

  1. Backup then overwrite (recommended): for each existing file, read it and write it to {path}.bak.YYYYMMDD-HHMMSS, then write the new document(s) to the original path(s)
  2. Overwrite: replace the existing file(s) with the new document(s)
  3. Abort: do not write anything; suggest they rename/move the existing file(s) first

Process

Read .claude/skills/generate-plan/PROMPT.md and follow its instructions exactly:

1. Read greenfield specs from plans/greenfield/
2. Generate EXECUTION_PLAN.md with phases, steps, and tasks
3. Generate root AGENTS.md with durable project-wide workflow guidelines
4. Generate plans/greenfield/AGENTS.md with greenfield execution-specific guidance

Output

Write these files:

• AGENTS.md
• plans/greenfield/EXECUTION_PLAN.md
• plans/greenfield/AGENTS.md

Create CLAUDE.md Files

If CLAUDE.md does not exist in the current directory, create it with:

@AGENTS.md

If it already exists, do not overwrite it.

If plans/greenfield/CLAUDE.md does not exist, create it with:

@AGENTS.md

If it already exists, do not overwrite it.

Lean Mode (--lean)

When --lean is passed:

• Skip all post-generation gates. Do not run /verify-spec, /codex-consult, or /criteria-audit. Report each as LEAN_SKIP in the output.
• All other steps (Q&A, document generation, deferred capture) run normally.

Post-Generation Gates (MANDATORY unless --lean)

These gates MUST execute before you produce the "Next Step" output. The output template requires results from each gate. Reporting SKIPPED without --lean is a skill violation — go back and run the gate.

Gate 1: AGENTS.md Size Check

Count the lines in the generated root AGENTS.md:

Thresholds:

• ≤100 lines: PASS — Optimal for root AGENTS.md
• 101-150 lines: WARN — "Root AGENTS.md is {N} lines. Keep durable project rules compact and push execution-specific detail into scoped plan directories."
• >150 lines: FAIL — "Root AGENTS.md exceeds 150 lines ({N} lines). Split durable rules from scoped execution guidance before proceeding."

If WARN or FAIL, offer to help split the file before proceeding.

Gate 2: Spec Verification

Run the spec-verification workflow:

1. Read .claude/skills/spec-verification/SKILL.md for the verification process
2. Verify context preservation: Check that all key items from TECHNICAL_SPEC.md and PRODUCT_SPEC.md appear as tasks or acceptance criteria
3. Run quality checks for untestable criteria, missing dependencies, vague language
4. Present any CRITICAL issues to the user with resolution options
5. Apply fixes based on user choices
6. Re-verify until clean or max iterations reached

IMPORTANT: Do not proceed to Gate 3 until verification passes or user explicitly chooses to proceed with noted issues.

Gate 3: Criteria Audit

Run /criteria-audit plans/greenfield to validate verification metadata in plans/greenfield/EXECUTION_PLAN.md.

• If FAIL: stop and ask the user to resolve missing metadata before proceeding.
• If WARN: report and continue.

Gate 4: Cross-Model Review

After verification passes, run cross-model review if Codex CLI is available:

1. Check if Codex CLI is installed: codex --version
2. If available, run /codex-consult with upstream context
3. Present any findings to the user before proceeding

Consultation invocation:

/codex-consult --upstream plans/greenfield/TECHNICAL_SPEC.md --research "execution planning, task breakdown" plans/greenfield/EXECUTION_PLAN.md

If Codex finds issues:

• Show critical issues and recommendations
• Ask user: "Address findings before proceeding?" (Yes/No)
• If Yes: Apply suggested fixes
• If No: Continue with noted issues

If Codex CLI is not installed or not authenticated: Report UNAVAILABLE (not SKIPPED — the distinction matters).

Error Handling

Next Step

Pre-condition: All gates above have completed, or --lean was explicitly passed. If you have not run them, STOP and run them now. Reporting SKIPPED without --lean is a skill violation.

When complete, inform the user:

Root AGENTS.md plus greenfield plan files created and verified.

AGENTS.md Size: PASS | WARN | LEAN_SKIP
Verification: PASSED | PASSED WITH NOTES | NEEDS REVIEW | LEAN_SKIP
Criteria Audit: PASSED | WARN | LEAN_SKIP
Cross-Model Review: PASSED | PASSED WITH NOTES | UNAVAILABLE | LEAN_SKIP

Your project is ready for execution:
1. cd plans/greenfield
2. /fresh-start
3. /configure-verification
4. /phase-prep 1
5. /phase-start 1