Loading...
Loading...
Found 405 Skills
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.
Start working on a PRD implementation
Create, update, validate, or analyze a PRD. Use when the user wants help producing, editing, validating, or analyzing a PRD.
Interview the user and write a PRD for Ralph in .prd/prd-<feature>.md.
Plan features interactively. Asks clarifying questions, then generates a detailed PRD document.
Integrated Collaboration for PRD + Executable Test Cases (Development Paradigm v2 Definition Section). Input is a finalized split task/requirement; outputs 4 files: PRD-MD and Test Case-MD (fact sources for AI) + two template-based review HTMLs (for human review, strictly 1:1 with MD). Co-write and iterate with users: autonomously read code after understanding requirements before writing; story-driven + phased single-point confirmation; UI stories include ASCII wireframes + Mermaid capabilities. Triggers: organizing/writing/refining PRDs, requirement documents, user stories, acceptance criteria, test cases, test benchmarks, test plans. Not applicable to: ambiguous requirements not split into tasks (use issue-pool first), unexplored interface solutions (use design-exploration first, whose output requirement-summary.md is exactly the input for this skill), small requirements for modifying an already launched feature (use req-change-workflow), long HTML articles/retrospectives/reports for human reading (use readable-output), project-level framework plans and version roadmaps (use issue-pool), writing code or running tests (this skill only produces documents, does not implement or execute cases).
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".
Transform PRD (Product Requirements Document) into actionable engineering specifications. Creates detailed technical specs that developers can implement step-by-step without ambiguity. Covers data modeling, API design, business logic, security architecture, deployment, and agent system design. Use when: converting product requirements to technical specs, validating PRD completeness, planning technical implementation, creating task breakdowns, or defining test specifications. Triggers: 'PRD to spec', 'convert requirements', 'technical spec from PRD', 'engineering doc from requirements', 'validate PRD'.
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
Write PRD — Product Requirements Documents with structured 8-section templates, user stories, acceptance criteria, and value proposition validation. Use when writing PRDs, defining product requirements, creating user stories with INVEST criteria, or building go/no-go decision frameworks.
Map user missions from trigger to value moment, organizing features into coherent paths during PRD v0.4 User Journeys. Triggers on requests to map user journeys, define user flows, describe how users accomplish goals, or when user asks "map user journeys", "define user flows", "user missions", "how do users accomplish X?", "journey mapping", "what steps do users take?", "pain to value flow". Consumes PER- (Persona Definition), FEA- (Feature Value Planning), KPI- (Outcome Definition). Outputs UJ- entries with step flows, pain points, and value moments. Feeds v0.4 Screen Flow Definition.
Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic.