gspec-implement

Phase-based implementation follows discovery, planning, implementation, and verification phases guided by your specification documents. Each phase completes a gated checkpoint with tests and documentation updates, ensuring safe rollbacks and continuous alignment with the original requirements.

Phase-based planning connects code work to PRD requirements by tracing every implemented capability directly to the original feature specifications. This ensures your executable software remains fully compliant with the defined gspec architecture, testing standards, and deployment practices throughout the workflow.

Yes, you need existing gspec documents before starting implementation. The workflow requires profile.md, stack.md, style.md, and practices.md to be loaded initially, as these living specifications provide the architectural context and standards required to execute phase-based plans accurately.

The best way to maintain traceability when implementing specifications is to use incremental delivery with gated checkpoints. Completing each phase with validation tests and documentation updates ensures every capability is traced back to PRD requirements while enabling safe rollbacks.

To discover gaps in your specifications before coding, start Phase 1 planning to analyze your gspec documents against the desired software capabilities. This disciplined workflow identifies missing requirements and translates the available specifications into a comprehensive, executable implementation plan.