Loading...
Loading...
Found 207 Skills
Generate comprehensive Product Requirements Documents (PRD) from idea validation files. Use when users ask to "create a PRD", "generate product requirements", "write a PRD", or want to turn validated ideas into actionable product specs. Works with idea.md and validate.md files from the idea-validator skill.
Save progress and generate a continuation prompt. Updates PRD status markers, captures git state, and writes checkpoint.md for the next session.
Guide product managers through PM workflows using the PM Brain framework library. Use when working on product management tasks, braindumping ideas, assessing opportunities, writing PRDs, conducting research, or planning strategy. Supports thinking-first approach before jumping to templates.
Generates professional PRD (Product Requirements Document) files optimized for AI coding tools. Takes a rough product idea, asks clarifying questions, and outputs a structured PDF ready to feed into AI coding assistants.
Generate Product Requirements Documents through structured discovery. 3 phases: Discovery interview, Analysis & Scoping, Technical Drafting. Use when: defining new products, planning features, documenting requirements. Triggers on "create PRD", "define product", "product requirements", "write PRD".
Interview the user and write a PRD for Ralph in .prd/prd-<feature>.md.
Specification generator - 6 phase document chain producing product brief, PRD, architecture, and epics. Triggers on "generate spec", "create specification", "spec generator", "workflow:spec".
Generate an Information Architecture (IA) document from a service plan, PRD, or product idea. Outputs a structured screen hierarchy as Markdown nested lists and saves to SCREENS.md.
Translate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes constraints, invariants, interfaces, and unresolved decisions before multi-service work starts. Use when the user needs an ECC-native PRD-to-SRS lane instead of vague planning prose.
PRD writing and product definition expert. Use when writing PRDs, user stories, acceptance criteria, or prioritizing features. Covers RICE/MoSCoW frameworks, agile requirements, and specification best practices.
Write a clear, decision-ready PRD (and optionally a PR/FAQ, AI eval spec, and prompt set) for cross-functional alignment.
Analyze HM Desktop PRD documents, extract requirement information, verify completeness, check chapter order (Requirement Source → Requirement Background → Requirement Value Analysis → Competitor Analysis → Requirement Description), inspect KEP definitions, detect requirement conflicts, and generate structured analysis reports. Applicable to user requests: (1) Analyze or review PRD documents, (2) Extract KEP lists from requirements, (3) Check PRD completeness or consistency, (4) Map requirements to module architecture, (5) Verify PRD format compliance, (6) Verify completeness of competitor analysis chapters. Keywords: PRD analysis, requirement extraction, KEP verification, completeness check, chapter order validation, competitor analysis check, analyze PRD, requirement extraction, completeness check, chapter order validation