module-workflow

Orchestrate module development stages 2-6 by delegating each task to specialized subagents—Foundation, Shell, DSP, GUI, and Validation—while the workflow skill coordinates state transitions, maintains handoff files, and presents decision menus after each stage completes.

Yes, the workflow skill handles resumption from handoff files, enforcing precondition checks to verify prior stages completed correctly before proceeding, ensuring continuity across interrupted development sessions.

After each stage, the workflow skill automatically commits changes, updates planning and status files, presents a numbered decision menu for the next action, and manages state transitions to maintain traceability throughout the module project.

No, the workflow skill automatically commits changes after each stage completes, removing the manual overhead and ensuring consistent version control discipline across Foundation, Shell, DSP, GUI, and Validation stages.

Stage 6 validation runs directly when preconditions are met and prior stages have completed successfully, eliminating unnecessary decision cycles and accelerating the final validation phase of module development.

Delegating to specialized subagents separates concerns across Foundation, Shell, DSP, and GUI work while the orchestrator coordinates handoffs and state, allowing focused expertise at each stage without central bottlenecks.