Loading...
Loading...
Found 207 Skills
Creates PRDs using persistent file-based planning. Use when user explicitly says "PRD", "product requirements document", or "产品需求文档". Combines PRD methodology with planning-with-files to avoid context switching.
Analyzes PRD documents, concept briefs, or feature specs and creates structured implementation plans with visual kanban tracking. Breaks requirements into epics, stories, and tasks with dependencies and estimates. Outputs to `.claude/` folder for integration with project-harness and other skills. Generates PROJECT.md for shared project context.
Write and iteratively refine PRD/requirements documents using a story-driven structure and strict staged confirmation mechanisms (including journey map alignment, per-story single-point confirmation, and final generation approval gate). This is applicable when users request to organize, write, or refine PRDs, requirements documents, user stories, and acceptance criteria, and hope to use ASCII wireframes and Mermaid (flowcharts/state diagrams/sequence diagrams) to reduce ambiguity and collaboratively complete the documents.
Implement an existing PRD (`Type: feat`/`fix`/`chore`), update tests/checks, and mark completed PRD checklist items. Triggers: implement prd, build feature from prd, execute prd checklist.
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.
Create a PRD from scratch. Use when the user says "lets create a product requirements document" or "I want to create a new PRD"
Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager.
Edit an existing PRD. Use when the user says "edit this PRD".
Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".
Interactive Product Owner skill for requirements gathering, analysis, and PRD generation. Triggers when users request product requirements, feature specification, PRD creation, or need help understanding and documenting project requirements. Uses quality scoring and iterative dialogue to ensure comprehensive requirements before generating professional PRD documents.
Runs autonomous loop fetching stories from GitHub Issues. Implements and closes issues as done. Triggers on "loop through my PRDs", "work on my issues", "start the autonomous loop", "implement my PRDs", or requests to work through GitHub issues autonomously.
Write structured product requirements documents (PRDs) with problem statements, user stories, requirements, and success metrics. Use when speccing a new feature, writing a PRD, defining acceptance criteria, prioritizing requirements, or documenting product decisions.