spec-workflow
Spec-driven development workflow for systematic feature development. Use when starting a new feature to ensure proper research, requirements, design, tasks, and execution phases.
technical-discussion
Collaborative technical discussion with proactive requirements gathering
workflows-plan
This skill should be used when transforming feature descriptions, bug reports, or improvement ideas into well-structured project plans following project conventions and best practices.
interview-skill
Deep-dive technical discovery and requirement gathering before coding. Use when a task is broad, ambiguous, or requires architectural decisions.
review-design-doc
Review a design document and provide feedback on implementation challenges, alternative approaches, and underspecified areas. Use when asked to review a design doc or feature spec.
project-interview
Conducts project specification interviews to clarify architecture, tech stack, and requirements. Use when starting a new project, planning architecture, gathering requirements, making tech decisions, or when asked to interview, create a spec, help plan, or define what to build. Creates SPEC.md with complete project specification.
feature-revision
Guide feature modification process with structured proposal document. Use when user requests feature changes, bug fixes requiring spec changes, or modifications to existing functionality. Manages requirements gathering, proposal creation, design documentation, and TDD workflow planning through phased user confirmation.
refinery-agent-pattern
Transform raw ideas into structured Product Requirements Documents (PRDs) using systematic refinement
project-context
Business goals, stakeholders, and high-level context for this project.
project-plan
How to organize, structure, and keep a project plan up to date.
kanban-architect
Kanban Architect role. USE WHEN user says /kanban-architect OR wants to plan, assign, or monitor kanban tasks.
product-manager
Product management: PRDs, RICE prioritization, metrics
sdlc-planning
Use when creating implementation plans, breaking down tasks, sequencing changes, planning TDD cycles, or creating a roadmap for implementing a user story.
sprint-planner
Plan and manage sprints using beads, with velocity tracking, capacity planning, and sprint goal optimization
scrum-master
Expert Scrum mastery covering sprint facilitation, team coaching, impediment removal, and agile transformation.
mvp-builder
MVP development toolkit using BMAD methodology. Transform ideas into working products through structured phases - product brief, technical spec, sprint planning, and iterative development. Optimized for vibe coding workflows.
flow-analysis
Comprehensive user journey analysis with multi-flow comparison
aico-pm-prd-writing
Create comprehensive Product Requirements Documents (PRD) that define what to build and why, focusing on goals, scope, user stories, and success criteria without implementation details. Use this skill when: - User asks to "write a PRD", "create PRD", "write requirements document" - User mentions "requirements document", "product requirements", "product spec" - Running /pm.plan command to create version planning document - Starting a new product, major feature, or initiative that needs formal requirements - Need to document goals, scope, user stories, functional requirements, and success criteria Output: ALWAYS write PRD files to docs/reference/pm/versions/{version-name}.md
interview
Conduct in-depth feature interviews to gather requirements. Use when a user wants to discuss a new feature idea, needs help defining requirements, or says "interview me about" a feature. Covers technical implementation, UI/UX, concerns, tradeoffs, and edge cases. Supports full-stack, web/UI, and infrastructure/DevOps features.
