product-implementation-spec

Coordinate product specification workflows across PRD, architecture, UX, implementation, test, and release phases.

4|1|Updated Apr 2, 2026

Search Tags:#workflow #architecture #documentation #specifications #prd #orchestrator

Ready to run

npx skills add https://github.com/AutisticAF/claude-code-apple-dev-plugin --skill product-implementation-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: product-implementation-spec
Source: https://github.com/AutisticAF/claude-code-apple-dev-plugin/tree/main/skills/product-implementation-spec
Command: npx skills add https://github.com/AutisticAF/claude-code-apple-dev-plugin --skill product-implementation-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates end-to-end product specification workflows by converting a product plan into a complete, ready-to-implement package.

Core Features & Use Cases

Master orchestration of PRD, Architecture, UX, Implementation, Test, and Release phases
Pauses for user approval at each phase gate to ensure alignment
Integrates with role-based skills (prd-generator, architecture-spec, ux-spec, implementation-guide, test-spec, release-spec)
Generates a cohesive docs/ package with outputs for each phase
Supports iterative refinement and re-generation after stakeholder feedback

Quick Start

Provide your product development plan and approval to begin generating the full specification package.

Frequently Asked Questions about product-implementation-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I coordinate end-to-end product specifications across PRD and architecture phases?▼

To coordinate end-to-end product specifications, you need an orchestrator that applies phase gates across PRD, architecture, UX, implementation, test, and release workflows to produce a ready-to-implement package.

What is the best way to generate a ready-to-implement documentation package from a product plan?▼

Generating a ready-to-implement documentation package requires orchestrating your product plan through gated approval phases, integrating sub-skills for each spec type, and outputting a cohesive docs package.

Can I pause the product specification workflow for stakeholder approvals between phases?▼

Yes, the product specification workflow pauses for user approval at each phase gate, ensuring alignment across PRD, architecture, UX, implementation, test, and release stages before proceeding.

How does a phase gate orchestrator handle iterative refinement after stakeholder feedback?▼

A phase gate orchestrator supports iterative refinement by allowing re-generation of specification outputs after stakeholder feedback, updating the docs package while maintaining gated approvals across all phases.

Do I need separate role-based specification skills to produce a complete product documentation package?▼

Producing a complete product documentation package requires integrating role-based skills like prd-generator, architecture-spec, ux-spec, implementation-guide, test-spec, and release-spec through a master orchestrator.

When do I need phase orchestration for product specification workflows?▼

You need phase orchestration for product specification workflows when converting a product plan into a complete, ready-to-implement package that requires gated approvals and cohesive documentation across all development phases.