dev-coding
Implement features from specs with backend and frontend skills
debrief
Analyze customer requirements and deliver market research, tiered proposals, and recommendations
dev-coding-backend
Backend implementation patterns and workflows
dev-coding-frontend
Frontend implementation patterns and workflows
dev-review
Code review with focus on quality, security, and best practices
dev-scout
Explore and document existing codebases at various depths
dev-specs
Generate implementation specifications from BRD use cases
diagram
Create and validate Mermaid diagrams in markdown files
docs-graph
View and query the documentation knowledge graph
dev-arch
Architecture decisions and technical design for features. Use when: (1) New feature requires structural decisions, (2) Validating if current architecture supports requirements, (3) Choosing technology for new capability (payments, real-time, etc.), (4) Greenfield project architecture
dev-changelog
Document implementation results with developer summary and user impact analysis. Use when: (1) After /dev-review passes, (2) End of sprint or milestone, (3) Before handoff to another developer, (4) Need to track what changed for users (release notes, user guides)
dev-test
Automated UI testing using Playwright browser tools. Use when: (1) After completing feature implementation, (2) After fixing bugs, (3) Before code review, (4) Verifying acceptance criteria from specs
utils/diagram
Create and validate Mermaid diagrams in markdown files
utils/gemini
Large context processing using Gemini Flash for codebase scanning and summarization