generate-plan

Pass the spec file path as input; the skill extracts provenance from the file preamble, dispatches the planner subagent to read the artifact from disk, and writes a dated plan to docs/plans/. The plan then goes through the refine-plan review-edit loop before being offered for execution.

Provide the idea ID (e.g., IDEA-7ef7d441); the skill reads the idea body with the built-in idea tool and inlines it into the planner prompt, since the planner subagent lacks the idea tool. The resulting plan is refined and validated like any other input source.

Yes. File inputs are passed by path rather than inlined, so large specs, RFCs, and design docs never pollute the orchestrator's context window. The planner reads the full artifact from disk itself.

When refine-plan returns not_approved_within_budget, the skill reports the status, commit state, plan path, and review paths, then stops without offering execution. You inspect the saved plan and review files manually and can invoke execute-plan yourself if desired.

The planner must emit a PLAN_ARTIFACT marker matching the expected output path, and the file must exist, be non-empty, and be freshly written. If validation fails, the skill surfaces the failure JSON and stops before refinement.