Loading...
Loading...
Found 35 Skills
Create Product Requirements Documents. Use when defining new features, projects, or initiatives. Covers user stories, acceptance criteria, and scope definition.
PRD writing and product definition expert. Use when writing PRDs, user stories, acceptance criteria, or prioritizing features. Covers RICE/MoSCoW frameworks, agile requirements, and specification best practices.
Use when "requirements document", "acceptance criteria", "user stories", "EARS format", "specification", "feature spec", "product requirements"
Convert ambiguous ideas into implementable, testable requirements with user stories and acceptance criteria.
Interactive interview to create comprehensive Product Requirements Documents with User Stories and Use Cases, starting with the problem, not the solution
Use when the user asks to create a feature, write a PRD or TRD, add user stories, write scenarios, create acceptance criteria, plan implementation, initialize product docs, set up product documentation, create, approve, amend, or validate a Product Constitution, run the Constitution Grill, create or maintain Product Vision, run a Vision Grill, or work anywhere in the product development lifecycle from project setup through implementation planning.
问题 + 成功指标 + 范围 + user stories + 设计 + 发布 + 待解决
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.
Structured specification with explicit scope boundaries: user stories, acceptance criteria, out-of-scope definition, risks, and estimation. Positions before feature-design in the feature lifecycle pipeline. Use when: "write spec", "user stories", "define requirements", "scope this", "what should this do", "acceptance criteria", "define scope"
Generates structured Given/When/Then acceptance criteria for a user story or feature slice. Use when translating product requirements into testable scenarios that cover the happy path, edge cases, error states, and non-functional expectations for engineering handoff and QA.
Guides creation of Product Requirements Prompts (PRPs) - comprehensive requirement documents that serve as the foundation for AI-assisted development