recursive-planning-spec

Recursive planning decomposes features from intent through nonterminal expansion into terminal InteractionSpecs. Start with a target feature, iteratively expand plan nodes, verify completion proofs (P1–P13), and generate delta-only artifacts until all leaves reach interaction-spec granularity.

Nonterminal expansion breaks down abstract planning nodes into more concrete child nodes until reaching terminal InteractionSpecs. It ensures leaf-level granularity, enforces OpenQuestion gating, and maintains deterministic task order with proof validation at each step.

Completion-proof validation (P1–P13) verifies each node satisfies functional and technical requirements. Run proofs after each expansion pass, confirm delta outputs are deterministic, and iterate until all leaves are terminal InteractionSpecs with no unresolved OpenQuestions.

Yes. Recursive planning generates UI projections for screens, components, and navigation flows alongside InteractionSpecs. Delta outputs capture screen contracts and UI implications, enabling UI-centric software design within the same planning workflow.

Recursive planning outputs delta-format artifacts—only new or changed nodes—rather than full graph dumps. Outputs include deterministic task ordering, completion proofs, InteractionSpecs, and UI-projection metadata for screens and navigation contracts.

Yes. Recursive planning integrates with MCP (Model Context Protocol) to drive nonterminal expansion and proof validation. It applies across AI planning and UI-centric design, enforcing delta outputs and guardrails against guessing at each decomposition step.