From product-builder
Use when ready to decide on technology stack after PRD. Triggers: "choose tech stack", "what technology", "technical decisions". Requires PRD to exist.
How this skill is triggered — by the user, by Claude, or both
Slash command
/product-builder:tech-stackThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Guide technology choices based on product requirements and constraints.
Guide technology choices based on product requirements and constraints.
Same-session handoff: If user just completed /pm-prd in this conversation, use that context directly and proceed to Step 2.
New session: Check for existing documents:
docs/prd/prd.md - Requireddocs/prd/user-flow.md - Optional (helps understand flow complexity)Missing PRD → Suggest using /pm-prd first
Gather these four constraints:
How to gather: Check what's inferable from PRD and context, then ask about remaining unknowns in a single question. For solo indie projects, default to simpler stacks unless user indicates otherwise.
Based on constraints, recommend stack with reasoning:
Present 2-3 options with:
Categories to cover:
Generate docs/tech/stack.md:
# Technology Stack
## Platform
- **Target:** [Web/Mobile/Both]
- **Primary:** [Main platform]
## Frontend
- **Framework:** [Choice]
- **UI Components:** [Choice - e.g., shadcn/ui, Ant Design, Material UI]
- **Reasoning:** [Why]
- **Key libraries:** [List]
## Backend
- **Approach:** [Choice - e.g., serverless, traditional, BaaS]
- **Reasoning:** [Why]
- **Key services:** [List]
## Database
- **Type:** [Choice]
- **Reasoning:** [Why]
## Infrastructure
- **Hosting:** [Choice]
- **CI/CD:** [Choice]
## Constraints for UI Design
- [Technical constraint that affects UI]
- [Another constraint]
## Not Using (and Why)
- [Technology]: [Reason for exclusion]
After generating, suggest: "Stack decided. Ready for /ui-spec to design pages or /tech-arch for system architecture."
npx claudepluginhub sparktech-ai/skills --plugin product-builderRecommends full technology stacks for new projects based on requirements, team expertise, and constraints like scale, performance, budget, and time-to-market.
Opinionated tech stack recommendations and settled library references. Runs parallel researcher agents to compare candidates and emit a stack report + ADRs for greenfield projects, or routes direct references for coding with settled defaults.
Evaluates technology stacks using weighted decision matrix. Compares frameworks, languages, databases via scored criteria like performance, ecosystem, maintenance, security. For objective tech selection.