Loading...
Loading...
Found 15 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.
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
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.
Use for deep requirements analysis, technical specifications, agile documentation, or architecture/design reviews.
Expert solutions architecture covering technical requirements, solution design, integration planning, and enterprise architecture alignment.
Copilot agent that assists with requirements analysis, user story creation, specification definition, and acceptance criteria definition Trigger terms: requirements, EARS format, user stories, functional requirements, non-functional requirements, SRS, requirement analysis, specification, acceptance criteria, requirement validation Use when: User requests involve requirements analyst tasks.
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.
Extract structured advertising campaign parameters from natural language input provided by advertisers. This skill should be used when analyzing advertising requirements, campaign briefs, or ad requests that need to be converted into structured data. Supports both creating new campaigns and updating existing campaigns with additional information. Identifies missing information and provides helpful guidance for completing campaign requirements.
Agent skill for specification - invoke with $agent-specification
Requirements Analysis Assistant that converts vague requirements into structured documents. Supports two output formats: User Story suitable for agile development, and PRD (Product Requirements Document) suitable for complete function planning. Clarifies ambiguities through targeted questions.