plan-feature

Feature planning automation consolidates spec phases and plan writing into a single invocation. It validates preconditions, dispatches spec-phases and write-plan back-to-back, and returns a structured summary with plan files and input signals.

Automated feature plan generation requires SPEC.md and RESEARCH_SUMMARY.md files in the feature directory. The orchestrator validates these gates before planning and surfaces clear errors if either file is missing.

Spec phases generation dispatches with a lazy batch flag when needed. This batches phase creation during the orchestrated planning round-trip to efficiently advance features from research gates to a ready-to-execute plan.

Generating implementation plans and spec phases simultaneously is supported by bundling both steps into a single subagent invocation. It runs spec-phases and write-plan back-to-back to produce a ready-to-execute plan for a feature.

The operational summary returns a structured end-of-cycle summary containing plan files and any NEEDS_INPUT signals. This output allows the orchestrator to identify missing requirements or proceed directly to execution.

Feature planning fails because the orchestrator enforces gate checks for SPEC.md and RESEARCH_SUMMARY.md before dispatching. Missing files trigger clear errors to ensure research phases are complete before plan generation begins.