VilnaCRM-Org/core-service - Page 2

quick-flow-solo-dev

Quick one-off tasks, small changes. Use when the user asks about quick flow solo dev.

retrospective

Optional at epic end: Review completed work lessons learned and next epic or if major issues consider CC. Use when the user asks about retrospective.

shard-doc

shard doc. Use when the user asks about shard doc.

sm

Sprint planning, status, coordination. Use when the user asks about sm.

sprint-planning

Generate a sprint plan for development tasks. This kicks off the implementation phase by producing a sequence the implementation agents follow for each story. Use when the user asks about sprint planning.

sprint-status

Anytime: Summarize sprint status and route to next workflow. Use when the user asks about sprint status.

tech-spec

Use for quick one-off tasks, small changes, brownfield additions, and utilities without extensive planning. Do not suggest it for highly complex work unless the user explicitly asks to skip full BMAD planning. Use when the user asks about tech spec.

tech-writer

Documentation, technical writing. Use when the user asks about tech writer.

technical-research

Technical feasibility architecture options and implementation approaches. Use when the user asks about technical research.

ux-designer

User experience, wireframes. Use when the user asks about ux designer.

validate-architecture

Guided Workflow to document technical decisions. Use when the user asks about validate architecture.

validate-brief

A guided experience to nail down your product idea. Use when the user asks about validate brief.

validate-epics-stories

Create the Epics and Stories Listing. Use when the user asks about validate epics stories.

validate-prd

Validate PRD is comprehensive lean well organized and cohesive. Use when the user asks about validate prd.

validate-story

Story cycle start: Prepare first found story in the sprint plan that is next, or if the command is run with a specific epic and story designation with context. Once complete, then VS then DS then CR then back to DS if needed or next CS or ER. Use when the…

validate-ux

Guidance through realizing the plan for your UX, strongly recommended if a UI is a primary piece of the proposed project. Use when the user asks about validate ux.

complexity-management

Maintain and improve code quality using PHPInsights without decreasing quality thresholds. Use when PHPInsights fails, cyclomatic complexity is too high, code quality drops, or when refactoring for better maintainability. Always maintains 93% complexity for…

deptrac-fixer

Diagnose and fix Deptrac architectural violations automatically. Use when Deptrac reports dependency violations, layers are incorrectly coupled, or when refactoring code to respect hexagonal architecture boundaries. Never modifies deptrac.yaml - always fixes…

documentation-creation

Create comprehensive project documentation from scratch. Use when setting up INITIAL documentation for a new project or building a complete documentation suite. NOT for updating existing docs (use documentation-sync instead). Covers project analysis,…

load-testing

Create and manage K6 load tests for REST and GraphQL APIs. Use when creating load tests, writing K6 scripts, testing API performance, debugging load test failures, or setting up performance monitoring. Covers REST endpoints, GraphQL operations, data…

quality-standards

Overview of protected quality thresholds and quick reference for all quality tools. Use when you need to understand quality metrics, run comprehensive quality checks, or learn which specialized skill to use. For specific issues, use dedicated skills…

structurizr-architecture-sync

Maintain Structurizr C4 architecture diagrams in sync with code changes. Use when adding components, modifying relationships, changing architectural boundaries, or implementing new patterns. Ensures workspace.dsl accurately reflects the current system…

observability-instrumentation

Add business metrics using AWS EMF (Embedded Metric Format) to API endpoints. Focus on domain-specific metrics only - AWS AppRunner provides default SLO/SLA metrics. Use when implementing new endpoints, adding command handlers, or instrumenting business…

query-performance-analysis

Detect N+1 queries, analyze slow queries with EXPLAIN, identify missing indexes, and ensure safe online index migrations. Use when optimizing query performance, preventing performance regressions, or debugging slow endpoints. Complements database-migrations…

api-platform-crud

Create complete REST API CRUD operations using API Platform 4 with DDD and CQRS patterns. Use when adding new API resources, implementing CRUD endpoints, creating DTOs, configuring operations, or setting up state processors. Follows the repository's hexagonal…

database-migrations

Create, manage, and apply database migrations using Doctrine ODM for MongoDB. Use when modifying entities, adding fields, managing database schema changes, creating repositories, or troubleshooting database issues.

documentation-sync

Keep documentation in sync with code changes. Use when implementing features, modifying APIs, changing architecture, adding configuration, updating security, or making any changes that affect user-facing or developer-facing documentation.