spec-kitty-plan

To generate an implementation plan for a single-feature workflow, run the planning automation from the project root to produce a plan.md file and align with standard branch contracts. This ensures downstream integration artifacts are created consistently.

An IMPL_PLAN-driven workflow handles feature planning by automating plan generation and enforcing governance checks before execution. It produces plan artifacts and blocks further processing until the task implementation phase is explicitly invoked.

No, you do not need to manually create branch contracts before planning feature implementation. The automated planning process generates branch contracts and plan artifacts directly in the project root during the planning phase.

Feature planning workflows block execution after generating the plan to enforce standard IMPL_PLAN-driven governance. This intentional block ensures the generated plan.md and branch contracts are reviewed before the implementation phase is invoked.

The automated planning skill is designed for single-feature workflows executed from the project root. It focuses on producing aligned governance context and plan artifacts for one feature at a time rather than spanning multiple directories.