kbd-reflect

Automate phase reflection by reading progress.json and archived change history to generate a structured reflection document. It verifies change completion, writes the reflection to markdown, and advances the waypoint to seed the next phase.

A phase reflection document summarizes goal achievement, delivered changes, technical debt, and lessons learned. You need one when closing a project phase to enable accurate evaluation and planning for the next phase.

Generate reflection.md by running the reflection command for the active phase. The tool collates progress data and constraints, loads archived changes, verifies completion, and writes the file to the phase directory.

Automated phase reflection supports project-agnostic operation across different KBD lifecycles. It applies to any project lifecycle where phases transition by collating progress, constraints, and change history.

Yes, the tool writes the reflection document and advances the waypoint to the next phase automatically. This closes the current phase and seeds the subsequent planning stage in one operation.

Phase reflection requires all changes in the phase to be complete before generating the document. The tool verifies change completion from archived data to ensure the reflection accurately captures the phase outcome.