Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From Product Management
Generates structured technical specifications for a feature, covering system architecture, API design, data models, technical requirements, implementation plan, and risks.
How this command is triggered — by the user, by Claude, or both
Slash command
/product-mgmt:specs feature nameThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Technical Specifications: $ARGUMENTS Ask @system-analyst and @architect to create detailed tech specs: ## 1. System Architecture - Components involved - Data flow diagrams - Integration points ## 2. API Design - Endpoints needed - Request/response formats - Authentication requirements ## 3. Data Models - Database schema changes - Relationships - Migrations needed ## 4. Technical Requirements - Performance requirements - Scalability considerations - Security requirements ## 5. Implementation Plan - Development phases - Testing strategy - Deployment approach ## 6. Risks & Mitigation ...
Ask @system-analyst and @architect to create detailed tech specs:
Output as detailed Markdown artifact.
npx claudepluginhub jhamidun/claude-code-config-pack --plugin product-mgmt/specsLaunches a roundtable discussion to define functional requirements, reading project context and producing a structured requirements document. Supports optional flags for format, strategy, session management, and diagnostic output.