Loading...
Loading...
Found 57 Skills
Write feature specifications that capture requirements and acceptance criteria. Use when (1) writing a new feature spec, (2) documenting functional requirements, (3) defining acceptance criteria for a feature, (4) capturing design goals and constraints for planned work, or (5) structuring a product idea into a formal specification.
Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
Reviews feature specifications for completeness, testability, and implementation readiness. Validates acceptance criteria, edge cases, and technical constraints. Use when reviewing feature specs before implementation or during sprint planning.
Use before merging PR - final gate ensuring all tests pass, review complete, CI green, and acceptance criteria verified
Fast Track for Feature Process - When requirements are clear and scope is small, skip the complete design process, write a compact {slug}-design.md, and proceed directly to implementation after one confirmation from the user. What is compressed is divergent discussions and phased reviews, not quality standards - code pointers, acceptance criteria, etc., must not be omitted. Trigger scenarios: User says "quick mode", "fastforward", "cut the steps", "just start working". Not suitable for complex features involving cross-subsystem integration, new terminology sorting, or more than 4 promotion steps - in these cases, proactively inform the user to revert to the complete process.
Generates user stories with clear acceptance criteria from product requirements or feature descriptions. Use when breaking down features for sprint planning, writing tickets, or communicating requirements to engineering.
Run the SPARC Specification phase — gather requirements, define acceptance criteria, identify constraints, and store the spec in memory
Create clear, concise user stories that combine Mike Cohn's user story format with Gherkin-style acceptance criteria. Use this to translate user needs into actionable development work that focuses on
XP 프랙티스에 맞는 사용자 스토리를 AI와 대화 형식으로 함께 작성하고 TrackerBoot(MCP)에 자동 등록하는 스킬.
Expert product specification and documentation writer. Use when creating PRDs, user stories, acceptance criteria, technical specifications, API documentation, edge case analysis, design handoff docs, feature flag plans, or success metrics. Covers the full spectrum from high-level requirements to implementation-ready specifications.
Create a structured format for documenting feature requirements as user stories. JSON files with testable acceptance criteria that AI agents can verify and track.
Use when writing effective BDD scenarios including acceptance criteria, edge cases, and scenario organization. Use when defining behavior specifications.