Loading...
Loading...
Found 18 Skills
Diagnose requirements problems and guide discovery of real needs and constraints
Create and validate product requirements documents (PRD). Use when writing requirements, defining user stories, specifying acceptance criteria, analyzing user needs, or working on product-requirements.md files in docs/specs/. Includes validation checklist, iterative cycle pattern, and multi-angle review process.
Use this skill when you need to analyze requirements, identify test points, boundaries, dependencies, and risks before test design; triggers include the term 'requirements analysis' whether expressed in Chinese or English.
Analyze and refine product requirements. Use when clarifying scope, identifying gaps, or validating requirements. Covers requirement types and analysis techniques.
Requirements Analysis SKILL, which can further interact with users to clarify requirements
Requirements clarification and decomposition, identify stakeholders and label requirement items with their corresponding owners and business entities; only produce structured requirement descriptions without modeling definitions, which can be used as input for subsequent modeling
Critical-thinking brainstorming partner that acts as a requirements analyst. Use when users present ideas, feature requests, or problems they want to solve. Triggers include "I want to build", "help me validate", "users need", "I'm thinking of creating", or any request involving problem/solution validation. This skill aggressively challenges assumptions, questions perceived problems, demands evidence, and ensures solutions address genuine needs before exploring implementation.
Use for deep requirements analysis, technical specifications, agile documentation, or architecture/design reviews.
Product discovery and requirements analysis specialist. Conducts stakeholder interviews, market research, problem discovery, and creates product briefs. Use for product brief, brainstorm, research, discovery, requirements gathering, problem analysis, user needs, competitive analysis, and setting foundation before product planning. Hands off to product manager when analysis complete.
Transform vague intent or incomplete requirements into validated, testable requirements through diagnostic state progression and structured dialogue. Use when user has an idea, feature request, problem statement, or existing requirements document that needs clarification or validation before design or implementation.
Agent skill for specification - invoke with $agent-specification
Event Storming 기법을 사용하여 PlantUML 시퀀스 다이어그램을 작성하고 유저스토리 개발을 준비합니다. 기획 구체화 시 사용하세요.