implementation-spec

What it does

The skill acts as a central coordinator that triggers and sequences a set of specialized agents to produce a complete specification package from a product development plan. It activates in response to commands like "generate implementation specifications" and manages Phase-by-Phase generation, including PRD, Architecture, UI/UX, Implementation Guide, Test Spec, and Release Documentation. It pauses after each phase for user approval and gates progression with explicit decision options. It assumes prerequisites (an existing product plan, and optional competitive analysis and market research) and can perform an optional Market Research Enhancement phase if research files are missing. It communicates progress and locations of generated documents, and provides a detailed Step-by-Step Execution workflow with gated steps and output artifacts for each phase.

How it works

• Activation: Responds to trigger phrases such as "generate implementation specifications", "create implementation specs", "generate complete specifications".
• Phase sequence: Executes in order with user decision gates: Phase 0 (optional market research), Phase 1 PRD generation, Phase 2 Architecture, Phase 3 UI/UX, Phase 4 Implementation Guide, Phase 5 Test Specification, Phase 6 Release Documentation, then completes with a Complete Specification Package Generated.
• Step-by-step actions per phase: Each phase describes which specialized skill to invoke (e.g., prd-generator, architecture-spec, ux-spec, implementation-guide) and provides user-facing messages announcing generation, the location of outputs, and a summary of contents.
• User decisions: After each phase, the user is prompted to Approve and continue, Request changes, or Iterate. The workflow pauses to allow review before proceeding to the next phase.
• Inputs: Requires a Product Development Plan and optional competitive analysis and market research. Step 0 checks for market research and can propose running competitive-analysis and market-research if missing.
• Outputs: Produces a set of docs in a docs/ directory (e.g., PRD.md, ARCHITECTURE.md, UX_SPEC.md, DESIGN_SYSTEM.md, IMPLEMENTATION_GUIDE.md, TEST_SPEC.md, RELEASE_SPEC.md) and a final complete package when all phases are approved.

When to use it

Use this skill when you need to convert a product development plan into a complete, auditable specification package, with consistent cross-document alignment and built-in checkpoints for stakeholder approval.

What it can touch

• Invoked sub-skills: prd-generator, architecture-spec, ux-spec, implementation-guide, (and QA/Release counterparts implied by subsequent stages).
• Outputs: Writes and updates documentation files under the docs/ directory (PRD.md, ARCHITECTURE.md, UX_SPEC.md, DESIGN_SYSTEM.md, IMPLEMENTATION_GUIDE.md, TEST_SPEC.md, RELEASE_SPEC.md).

Caveats

• Requires user approvals at each gate; progress is not automatic to completion without confirmation.
• Optional Phase 0 depends on existence of market/competitive research; if not present, it prompts to run those skills.
• Locale and tooling references are tied to the environment and skills available in the repository (e.g., prd-generator, architecture-spec, ux-spec, implementation-guide).