Loading...
Loading...
Found 28 Skills
Run the SPARC Specification phase — gather requirements, define acceptance criteria, identify constraints, and store the spec in memory
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.
Systematic three-phase approach to feature development using Requirements, Design, and Tasks phases. Transforms vague feature ideas into well-defined, implementable solutions that reduce ambiguity, improve quality, and enable effective AI collaboration.
Interactive feature development workflow from idea to implementation. Creates requirements (EARS format), design documents, and implementation task lists. Use when creating feature specs, requirements documents, design documents, or implementation plans. Triggered by "kiro" or references to .kiro/specs/ directory.
Progressively gather requirements through automated codebase discovery and yes/no questions, then generate a comprehensive requirements spec. Use when starting a new feature, planning a build, or when you need structured requirements before implementation.
Use when a project needs requirements or design clarification before creative work like features, components, or behavior changes.
Socratic deep interview with mathematical ambiguity gating before autonomous execution
Senior Business Analyst with 10+ years bridging business and technical teams. Use when conducting market research, competitive analysis, gathering requirements, creating business process models, cost-benefit analysis, or validating assumptions with data.
Systematically gather comprehensive travel itinerary requirements through structured discovery questions, MCP-powered research (Perplexity, Exa), and expert detail gathering. Use when users request travel planning, itinerary creation, or trip assistance requiring deep research and personalized requirements gathering. Outputs detailed requirements specification with day-by-day itineraries.
Conducts structured interviews to derive technical requirements from business requirements. Requires completed business-requirements.yaml as input. Asks targeted technical questions about architecture, technology stack, data model, APIs, security, testing, and deployment. Generates technical-requirements.yaml output.
LOAD THIS SKILL when: gathering requirements for new features, user mentions 'requirements', 'requirements-start', 'requirements-end', 'requirements-status', 'requirements-current', 'requirements-list', 'requirements-remind'. Covers structured Q&A workflow with 5-phase requirements gathering, codebase analysis, and spec generation.
Proactive requirements gathering - systematically interviews the user to uncover ambiguities, preferences, and constraints BEFORE implementation begins.