Loading...
Loading...
Found 276 Skills
Create PRDs through the gather-criticize loop, sync existing PRDs, push amendments, and check PRD status.
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.
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
Creates well-formed tasks following a template that engineers can implement. Triggers on: 'create tasks', 'define work items', 'break this down', creating tasks from PRD, converting requirements into actionable tasks, feature breakdown, sprint planning.
Generate structured PRD documents for n8n automation workflows. Use when planning n8n workflows, creating automation requirements, starting a new n8n project, or preparing workflow specifications before building.
Convert bug reports into prd.json user stories for autonomous fixing. Use after running test-and-break skill. Triggers on: convert bugs to stories, fix these bugs, add bugs to prd, create fix stories.
Update PRD based on design decisions and strategic changes made during conversations
Product Requirements Document creation and feature specification writing. Use when writing PRDs, technical specs, feature documentation, or requirements. Triggers on "PRD", "product requirements", "feature spec", "technical requirements", "functional spec".
AI Native Camp Day 3 Clarify & GitHub. Clarify 플러그인으로 모호한 요구사항을 명확하게 만들고, 나만의 스킬을 만들고, PRD를 작성하여 GitHub에 첫 PR을 제출한다. "3일차", "Day 3", "clarify", "클래리파이", "PRD", "GitHub" 요청에 사용.
PRD Document Management, provides creation and update functions for main PRD and module PRD. Supports quick generation using natural language requirement templates. Call when you need to create or update PRD documents.
Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".
Translate PRDs into detailed UX specifications including user flows, screen descriptions, components, and interaction patterns. Use when a user has a PRD and needs to define the concrete UI/UX before generating development prompts. Bridges product requirements to implementation details.