Loading...
Loading...
Found 47 Skills
Specification-driven development with structured phases: Initialize, Plan, Tasks, Implement+Validate. Creates structured feature specs with traceability to requirements. Use when: starting projects, planning features, implementing with verification, or tracking decisions across sessions. Also use when the user wants to break a feature into tasks, plan before coding, track implementation progress, set up a new project structure, or organize work into specs and plans. Triggers on "map codebase", "initialize", "initialize project", "create feature", "plan", "tasks", "implement", "validate", "archive", "break this into tasks", "plan this feature", "start a new project".
Generate structured task lists from specs or requirements. IMPORTANT: After completing ANY spec via ExitSpecMode, ALWAYS ask the user: "Would you like me to generate a task list for this spec?" Use when user confirms or explicitly requests task generation from a plan/spec/PRD.
Implement work on issues. Use when user asks to "start working on issue", "what should I work on", "pick up task", "continue work", or "find next task".
Use when you have specifications or requirements for multi-step tasks before touching code
Plan a new feature from concept to approved implementation plan. Activates Product Council for strategic evaluation, then Feature Council for technical planning. Produces a documented decision and scoped task breakdown. Use when starting any new feature work.
Turn ideas into fully formed designs and specs through natural collaborative dialogue. Use when planning new features, designing architecture, or making significant changes to the codebase.
Use when converting a design document, PRD, or task list into beads issues - ensures lossless conversion with proper epic hierarchy, validated dependencies for maximum parallelization, and three independent subagent review passes before execution
Use when you have a raw idea or request and want to run the full analytics pipeline automatically — from research through to an interlinked task list. Best for straightforward problems where the full pipeline can flow with minimal back-and-forth.
Creates structured development plans with phased task breakdowns, requirements, and QA checklists. Use when the user explicitly asks to create a dev plan, development plan, or document development requirements.
Generates structured .code-task.md files from descriptions or PDD implementation plans. Auto-detects input type, creates properly formatted tasks with Given-When-Then acceptance criteria.
Generates detailed implementation plans with milestones and tasks from business and technical requirements. Embeds best practices including task sizing (30m-2.5h), style anchors, TDD requirements, and quality constraints. Outputs milestones.yaml and milestone-m*.tasks.yaml files ready for development.
Spec-driven development framework for ecommerce features. Orchestrates from intent to implementation via structured specs and task breakdown. Triggers on "/spec.plan", "/spec.refine", "/spec.clarify", "/spec.tasks", "/spec.run", "I want to build", "I want to add", "create spec", "feature spec", "new feature", "implement feature".