ready-to-implement

To verify work items before implementation, validate the active collaboration session, read the design document, and parse the Work Items section to check for any pending entries. If pending items are found, return to the work item loop until all are fully documented.

If pending work items are found during the design-to-implementation transition, the process halts and returns to the work item loop. This gatekeeping mechanism ensures no undocumented items proceed to the rough-draft phase, reducing mid-stream ambiguity and rework.

You need a gatekeeping workflow for design documents when you want to enforce strict phase transitions. It ensures an active collaboration session is verified and all design document work items are resolved before delegating the phase change to the rough-draft implementation flow.

To transition a collaboration session to the rough-draft implementation phase, confirm all work items are documented. The workflow then prompts for user confirmation and delegates the phase change via the complete_skill operation to the ready-to-implement flow.

Yes, an active collaboration session is required to validate design-to-implementation readiness. The workflow first verifies that a collaboration session is active before reading the design document and checking the Work Items section for pending tasks.

Your implementation phase starts with missing work item documentation because the gatekeeping process was bypassed. Enforcing a workflow that parses the design document and checks the Work Items section prevents undocumented tasks from moving to the rough-draft phase.