Loading...
Loading...
Found 15 Skills
Analyzes Figma designs and generates implementation-ready PRDs with detailed visual specifications. Use when user provides Figma link or uploads design screenshots. Requires Figma MCP server connection.
Sets up a Ralph autonomous development loop for any project. First generates a full PRD from the user's description, then derives a task plan from it. Wraps Claude Code in an intelligent while-true loop with circuit breakers, exit detection, session persistence, and progress tracking. Use when you want Claude to autonomously work through a task list until done.
Clarify ambiguous requirements through focused dialogue before implementation. Use when requirements are unclear, features are complex (>2 days), or involve cross-team coordination. Ask two core questions - Why? (YAGNI check) and Simpler? (KISS check) - to ensure clarity before coding.
Specification generator - 6 phase document chain producing product brief, PRD, architecture, and epics. Triggers on "generate spec", "create specification", "spec generator", "workflow:spec".
Prioritize features and define MVP boundaries based on problem framing and user models. Use when a user has validated their problem and understands their users but needs to decide what to build first. Outputs feature priorities, MVP scope, and explicit cuts that feed into PRD generation.
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.
Ideation: Use for /ideation or when organizing messy brain dumps into structured specs. NOT for existing tickets (use /spec instead).
Score startup idea through S.E.E.D. niche check + STREAM 6-layer analysis + Devil's Advocate inversion, auto-pick stack, and generate PRD with acceptance criteria. Use when user says "validate idea", "score this idea", "should I build this", "go or kill", "generate PRD", or "evaluate opportunity". Do NOT use for deep research (use /research first) or decision-only framework (use /stream).
PM Agent Team - Automated product discovery, strategy, and PRD generation. Runs 4 specialized PM agents in parallel to produce a comprehensive PRD before PDCA Plan phase. Integrates pm-skills frameworks (MIT). Use proactively when user wants product analysis before development, needs a PRD, or asks for PM-level planning. Triggers: /pdca pm, pm analysis, product discovery, PRD, pm team, PM 분석, 제품 기획, 제품 발견, PM팀, PRD 작성, PM分析, プロダクト分析, 产品分析, 产品发现, análisis PM, descubrimiento de producto, analyse PM, découverte produit, PM-Analyse, Produktentdeckung, analisi PM, scoperta prodotto Do NOT use for: implementation, code review, existing PDCA phases (plan/design/do/check).
Generate structured prd.json files for autonomous agent loops (Ralph Wiggum pattern). Use when planning bulk/batch tasks, migrations, refactoring campaigns, or any work that can be decomposed into independent items with verification steps.
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.
Use when the user wants a full feature-development chain: clarify a rough feature idea into a prompt, review it with the user, then hand it to grill-with-docs, to-prd, to-issues, and tdd.