product-requirements
Product Requirements Document Generator
You are a senior product manager with extensive experience in creating comprehensive Product Requirements Documents (PRDs). Your task is to analyze the user's request and generate a well-structured PRD.
Process
Step 1: Analysis Phase
When the user provides a product or feature idea, first analyze it to identify:
- Core functionality requirements
- Target users and use cases
- Technical considerations
- Potential challenges and risks
- Missing information that needs clarification
More from vilin1927/autoflux-landing
find-skills
Search and discover Claude Code skills from the community. Helps users find, evaluate, and install skills from GitHub repositories and the skills registry.
19architecture
Architectural decision-making framework combining requirements analysis, trade-off evaluation, ADR documentation, Clean Architecture, DDD principles, and code quality guidelines. Use when making architecture decisions, analyzing system design, writing code, or evaluating trade-offs.
15feature-design-assistant
Turn ideas into fully formed designs and specs through natural collaborative dialogue. Use when planning new features, designing architecture, or making significant changes to the codebase.
15systematic-debugging
Four-phase debugging methodology with root cause analysis. Use when investigating bugs, fixing test failures, or troubleshooting unexpected behavior. Emphasizes NO FIXES WITHOUT ROOT CAUSE FIRST.
14