kbd-plan

To convert project-phase assessments into an ordered change plan, you can use a phase-aware planning tool that reads assessment data and project constraints to generate a prioritized list of changes. This process translates scattered assessment inputs into a structured, actionable plan.md file.

An OpenSpec command in project change planning is an optional output emitted when available, used to define project changes natively. When OpenSpec is not available, the planning process defaults to creating standard change files within a changes directory.

Yes, you can generate a project change list for any active project phase. The planning mechanism reads the active phase identity and its specific constraints to produce a phase-aware, prioritized change plan tailored to that stage.

Yes, this project planning approach works without pre-existing OpenSpec dependencies. If OpenSpec commands are not available in your environment, the system automatically falls back to creating native change files and updating waypoint files directly.

The best way to manage scattered project constraints during workflow planning is to consolidate them through an automated planning protocol. This protocol reads identity, active phase, and constraints simultaneously to refresh waypoints and output a ready-to-follow plan.

To update waypoint files when planning project changes, the plan protocol automatically reads project identity and constraints, then refreshes the current waypoint. This ensures your waypoint files accurately reflect the newly generated ordered change list.