workflow-kit-plan

To turn a technical spec into an implementation-ready plan, you generate a self-contained plan.md from an existing spec.md. This converts high-level WHAT and WHY into concrete architecture, files, contracts, risks, and testing strategy for the next agent to execute without guessing.

You create a technical planning document with risk and testing strategy by processing a spec.md through a documentation-first workflow. The output plan.md defines edit boundaries, scope management constraints, and testing protocols required before implementation tasks begin.

You need to create a research.md file during technical planning only when technical unknowns or decisions block a correct plan. It resolves TРЕБУЕТ УТОЧНЕНИЯ items and clarifies data models so the final plan remains accurate and implementable.

Generating code directly from a spec.md without a separate planning step is not recommended for this workflow. The planning step ensures no code is generated prematurely, preventing micro-tasking and ensuring the technical design is fully resolved before implementation.

Yes, workflow-kit-plan requires a pre-existing workspace and change-name created during the specification phase. It validates the workspace and required templates before resolving scope artifacts and producing the executable plan.

The best way to manage edit scope for an atomic change is to produce or update a scope.md file during planning. This establishes clear change boundaries so downstream execution agents can operate safely without conversation context.