Impl Skill -- 15-Phase Implementation Workflow

A phased implementation workflow orchestrates software delivery from requirements to final sync across sequential stages. It enforces phase gates and artifact creation, validating design docs, code skeletons, and tests to ensure quality checks pass before progression.

Begin Phase 1 inline to establish task goals, then progress through phases 2-15 using designated agents and gates. The workflow adapts to existing artifacts or creates missing ones inline, ensuring prerequisites are validated before each phase.

Yes, the implementation workflow supports cooperative agent engagement to accelerate delivery. Agents act in a coach-like orchestration role, guiding the production of design artifacts, code skeletons, tests, and tracking reports across the phases.

No, existing documentation is not strictly required. The workflow adapts to existing artifacts if present, but executes inline creation when artifacts are missing, ensuring design docs and tests are produced during the pipeline.

This workflow enforces strict toolchain discipline across a 15-phase pipeline, rigorously validating prerequisites and gating phases. Unlike simpler flows, it mandates artifact creation at each step and surfaces a comprehensive completion report.

Avoid this workflow if your project lacks the scale to justify 15 sequential phases or if toolchain prerequisites cannot be validated. It enforces strict artifact creation and phase gates, which may bottleneck rapid prototyping or highly iterative contexts.