Loading...
Loading...
Found 101 Skills
Use when generating a Product Requirements Document from a high-level idea, feature request, or product vision — covers discovery questions, structured PRD drafting, section-by-section review, and transition to implementation planning
This skill should be used when the user needs to structure what to build and when by converting discovery opportunities into prioritized bets and roadmaps. Use when organizing product capability blocks, writing solution briefs, planning quarterly cycles, or communicating product direction without false precision.
Use when you have a rough product idea and want a complete PRD without sitting through an interactive grilling. Claude walks the full decision tree (edge cases, modules, schema, testing, security), self-answers with software-engineering best practices, streams the Q&A live so you can override, and writes the PRD locally with an option to push as a GitHub issue.
Create Product Requirements Documents (PRDs) that define the end state of a feature through iterative design interview. Use when planning new features, migrations, or refactors. Generates structured PRDs with acceptance criteria, testing strategy, and architectural decisions.
Creates detailed Product Requirements Documents in Markdown format. Use when writing PRDs, defining feature requirements, or creating specification documents for development teams.