sepehr/data_analysis
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial commit

Browse Source
This commit is contained in:
sepehr
2026-01-11 22:04:05 +01:00
commit 87a8b6b844
549 changed files with 96211 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

163
.claude/claude.md Normal file
View File

@@ -0,0 +1,163 @@
# CLAUDE.md - BMAD v6 Project Memory
## Project Identity
**Project Name**: [Your Project Name]
**Tech Stack**: Node.js 20+, Express, TypeScript, PostgreSQL, Jest
**Status**: Active Development
**Last Updated**: 2026-01-11
---
## 🎯 BMAD Agents & Their Roles (Never Deviate)
### Phase 1: Planning (Agentic Planning)
These agents create the **PRD** and **Architecture** documents:
- **Analyst Agent** (`/analyst`)
- INPUT: User brief, business goals
- OUTPUT: `docs/prd.md` (complete product requirements)
- Role: Deep requirements analysis, user stories gathering
- **PM Agent** (`/pm`)
- INPUT: PRD from Analyst
- OUTPUT: Epic backlog + prioritized stories
- Role: Refine PRD, create backlog for SM
- **Architect Agent** (`/architect`)
- INPUT: PRD + tech preferences
- OUTPUT: `docs/architecture.md` (system design, ADRs, constraints)
- Role: Technical decisions, architecture patterns, tech stack alignment
### Phase 2: Development (Context-Engineered Development)
These agents consume Story Files (created by SM):
- **Scrum Master Agent** (`/sm`)
- INPUT: Backlog from PM + Architecture from Architect
- OUTPUT: `docs/stories/X.Y.story-name.md` (implementation-ready)
- **CRITICAL**: SM embeds **full context** into each story:
- Architecture Decision References (ADRs)
- Acceptance Criteria (exact, testable)
- Implementation Guidance
- Dependencies & testing requirements
- Role: Create stories that Dev agent can execute with **zero ambiguity**
- **Dev Agent** (`/dev`)
- INPUT: A single Story File + referenced Architecture
- OUTPUT: Code implementation + tests + PR
- **CRITICAL**: Dev agent should ONLY read:
1. The current story file (reference with `@docs/stories/X.Y.story-name.md`)
2. Architecture from `docs/architecture.md` (or specific ADR)
3. Tech Stack patterns from `/src` code
- Role: Execute, don't invent
- **QA Agent** (`/qa`)
- INPUT: Dev's implementation + story file
- OUTPUT: Validation checklist, defect list or verification
- Role: Validate against acceptance criteria
---
## 📂 Context Locations (Where Each Agent Reads/Writes)
### Agent Reads
| Agent | Reads From | Purpose |
|-------|-----------|---------|
| Analyst | Business brief (input by you) | Understand requirements |
| PM | Analyst's PRD | Create backlog |
| Architect | PRD + tech preferences | Design system |
| SM | Backlog + Architecture + code patterns | Create story specs |
| Dev | Story file + Architecture refs | Implement feature |
| QA | Story file + Dev output | Validate |
### Agent Writes
| Agent | Writes To | Format |
|-------|-----------|--------|
| Analyst | `docs/prd.md` | Markdown |
| PM | Backlog (in chat or `docs/epics.md`) | Markdown |
| Architect | `docs/architecture.md` | Markdown (with ADR sections) |
| SM | `docs/stories/X.Y.description.md` | Markdown (detailed specs) |
| Dev | `src/`, `tests/` | Code + Test files |
| QA | Validation in chat + update story status | Markdown checklist |
---
## 🏗️ Architecture Constraints (MUST NOT BREAK)
**These are decided once, NEVER change mid-project without team review:**
### API Design Pattern
- Gateway Pattern: Single entry point (`/api`)
- Routes: RESTful `/api/v1/[resource]/[action]`
- Authentication: JWT at Gateway level (not per-route)
- Error responses: Standardized JSON with `code`, `message`, `details`
### Database Layer
- ORM: Prisma (never raw SQL)
- Migrations: One per feature, committed to git
- Schema: Timestamps (`createdAt`, `updatedAt`) on all tables
- Transactions: Always wrap multi-step operations
### Async Processing
- Queue Library: Bull
- Message Broker: Redis
- Pattern: Email sends, notifications, heavy computation → queued
- Retry policy: 3 attempts, exponential backoff
### Authentication & Security
- Password hashing: bcrypt (library: bcryptjs)
- JWT signing key: Stored in `.env`, never in code
- CORS: Whitelist explicit domains
- Rate limiting: 100 req/minute per IP
### Testing
- Framework: Jest
- Coverage minimum: 80%
- Tests near code: `*.test.ts` in same folder as source
- Test data: Use fixtures in `tests/fixtures/`
### Code Style
- Language: TypeScript (strict mode always)
- Linter: ESLint + Prettier
- Commit format: `feat(module): description` or `fix(module): description`
- Branch strategy: Feature branches only, PR + review before merge
---
## 📝 Story File Structure (How SM Formats Each Story)
When SM creates a story, it MUST include ALL of this (Dev relies on it):
```markdown
# Story X.Y: [Feature Name]
## Objective
[One sentence: What we're building and why]
## Acceptance Criteria (Gherkin Format)
Given [context]
When [action]
Then [result]
[Repeat for each criterion]
## Architecture References
- See: docs/architecture.md → "API Design Pattern" section
- See: docs/architecture.md → "Authentication" ADR
- Pattern used: [Specific pattern name]
## Implementation Guidance
- Files to create: [list]
- Files to modify: [list]
- Patterns to follow: [reference code examples]
- Tests required: [specific test cases]
## Dependencies
- Depends on: Story X.Y (must be DONE first)
- Blocks: Story X.Z (cannot start until this is merged)
## Definition of Done
- [ ] Code passes linter (ESLint)
- [ ] Tests written & passing (Jest, >80% for this file)
- [ ] Database migration added (if needed)
- [ ] Story status updated in docs/stories/
- [ ] PR created with reference to this story

14
.claude/commands/bmad/bmm/agents/analyst.md Normal file
View File

@@ -0,0 +1,14 @@
---
name: 'analyst'
description: 'analyst agent'
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmm/agents/analyst.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

14
.claude/commands/bmad/bmm/agents/architect.md Normal file
View File

@@ -0,0 +1,14 @@
---
name: 'architect'
description: 'architect agent'
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmm/agents/architect.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

14
.claude/commands/bmad/bmm/agents/dev.md Normal file
View File

@@ -0,0 +1,14 @@
---
name: 'dev'
description: 'dev agent'
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmm/agents/dev.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

14
.claude/commands/bmad/bmm/agents/pm.md Normal file
View File

@@ -0,0 +1,14 @@
---
name: 'pm'
description: 'pm agent'
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmm/agents/pm.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

14
.claude/commands/bmad/bmm/agents/quick-flow-solo-dev.md Normal file
View File

@@ -0,0 +1,14 @@
---
name: 'quick-flow-solo-dev'
description: 'quick-flow-solo-dev agent'
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmm/agents/quick-flow-solo-dev.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

14
.claude/commands/bmad/bmm/agents/sm.md Normal file
View File

@@ -0,0 +1,14 @@
---
name: 'sm'
description: 'sm agent'
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmm/agents/sm.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

14
.claude/commands/bmad/bmm/agents/tea.md Normal file
View File

@@ -0,0 +1,14 @@
---
name: 'tea'
description: 'tea agent'
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmm/agents/tea.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

14
.claude/commands/bmad/bmm/agents/tech-writer.md Normal file
View File

@@ -0,0 +1,14 @@
---
name: 'tech-writer'
description: 'tech-writer agent'
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmm/agents/tech-writer.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

14
.claude/commands/bmad/bmm/agents/ux-designer.md Normal file
View File

@@ -0,0 +1,14 @@
---
name: 'ux-designer'
description: 'ux-designer agent'
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmm/agents/ux-designer.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

5
.claude/commands/bmad/bmm/workflows/check-implementation-readiness.md Normal file
View File

@@ -0,0 +1,5 @@
---
description: 'Critical validation workflow that assesses PRD, Architecture, and Epics & Stories for completeness and alignment before implementation. Uses adversarial review approach to find gaps and issues.'
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md, READ its entire contents and follow its directions exactly!

13
.claude/commands/bmad/bmm/workflows/code-review.md Normal file
View File

@@ -0,0 +1,13 @@
---
description: 'Perform an ADVERSARIAL Senior Developer code review that finds 3-10 specific problems in every story. Challenges everything: code quality, test coverage, architecture compliance, security, performance. NEVER accepts `looks good` - must find minimum issues and can auto-fix with user approval.'
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/4-implementation/code-review/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

13
.claude/commands/bmad/bmm/workflows/correct-course.md Normal file
View File

@@ -0,0 +1,13 @@
---
description: 'Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation'
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

5
.claude/commands/bmad/bmm/workflows/create-architecture.md Normal file
View File

@@ -0,0 +1,5 @@
---
description: 'Collaborative architectural decision facilitation for AI-agent consistency. Replaces template-driven architecture with intelligent, adaptive conversation that produces a decision-focused architecture document optimized for preventing agent conflicts.'
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md, READ its entire contents and follow its directions exactly!

5
.claude/commands/bmad/bmm/workflows/create-epics-and-stories.md Normal file
View File

@@ -0,0 +1,5 @@
---
description: 'Transform PRD requirements and Architecture decisions into comprehensive stories organized by user value. This workflow requires completed PRD + Architecture documents (UX recommended if UI exists) and breaks down requirements into implementation-ready epics and user stories that incorporate all available technical and design context. Creates detailed, actionable stories with complete acceptance criteria for development teams.'
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md, READ its entire contents and follow its directions exactly!

13
.claude/commands/bmad/bmm/workflows/create-excalidraw-dataflow.md Normal file
View File

@@ -0,0 +1,13 @@
---
description: 'Create data flow diagrams (DFD) in Excalidraw format'
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/excalidraw-diagrams/create-dataflow/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/excalidraw-diagrams/create-dataflow/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

13
.claude/commands/bmad/bmm/workflows/create-excalidraw-diagram.md Normal file
View File

@@ -0,0 +1,13 @@
---
description: 'Create system architecture diagrams, ERDs, UML diagrams, or general technical diagrams in Excalidraw format'
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/excalidraw-diagrams/create-diagram/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/excalidraw-diagrams/create-diagram/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

13
.claude/commands/bmad/bmm/workflows/create-excalidraw-flowchart.md Normal file
View File

@@ -0,0 +1,13 @@
---
description: 'Create a flowchart visualization in Excalidraw format for processes, pipelines, or logic flows'
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/excalidraw-diagrams/create-flowchart/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/excalidraw-diagrams/create-flowchart/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

13
.claude/commands/bmad/bmm/workflows/create-excalidraw-wireframe.md Normal file
View File

@@ -0,0 +1,13 @@
---
description: 'Create website or app wireframes in Excalidraw format'
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/excalidraw-diagrams/create-wireframe/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/excalidraw-diagrams/create-wireframe/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

5
.claude/commands/bmad/bmm/workflows/create-prd.md Normal file
View File

@@ -0,0 +1,5 @@
---
description: 'Creates a comprehensive PRD through collaborative step-by-step discovery between two product managers working as peers.'
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/2-plan-workflows/prd/workflow.md, READ its entire contents and follow its directions exactly!

5
.claude/commands/bmad/bmm/workflows/create-product-brief.md Normal file
View File

@@ -0,0 +1,5 @@
---
description: 'Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.'
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md, READ its entire contents and follow its directions exactly!

13
.claude/commands/bmad/bmm/workflows/create-story.md Normal file
View File

@@ -0,0 +1,13 @@
---
description: 'Create the next user story from epics+stories with enhanced context analysis and direct ready-for-dev marking'
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/4-implementation/create-story/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

5
.claude/commands/bmad/bmm/workflows/create-tech-spec.md Normal file
View File

@@ -0,0 +1,5 @@
---
description: 'Conversational spec engineering - ask questions, investigate code, produce implementation-ready tech-spec.'
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.md, READ its entire contents and follow its directions exactly!

5
.claude/commands/bmad/bmm/workflows/create-ux-design.md Normal file
View File

@@ -0,0 +1,5 @@
---
description: 'Work with a peer UX Design expert to plan your applications UX patterns, look and feel.'
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md, READ its entire contents and follow its directions exactly!

13
.claude/commands/bmad/bmm/workflows/dev-story.md Normal file
View File

@@ -0,0 +1,13 @@
---
description: 'Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria'
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

13
.claude/commands/bmad/bmm/workflows/document-project.md Normal file
View File

@@ -0,0 +1,13 @@
---
description: 'Analyzes and documents brownfield projects by scanning codebase, architecture, and patterns to create comprehensive reference documentation for AI-assisted development'
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/document-project/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/document-project/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

5
.claude/commands/bmad/bmm/workflows/generate-project-context.md Normal file
View File

@@ -0,0 +1,5 @@
---
description: 'Creates a concise project-context.md file with critical rules and patterns that AI agents must follow when implementing code. Optimized for LLM context efficiency.'
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/generate-project-context/workflow.md, READ its entire contents and follow its directions exactly!

5
.claude/commands/bmad/bmm/workflows/quick-dev.md Normal file
View File

@@ -0,0 +1,5 @@
---
description: 'Flexible development - execute tech-specs OR direct instructions with optional planning.'
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md, READ its entire contents and follow its directions exactly!

5
.claude/commands/bmad/bmm/workflows/research.md Normal file
View File

@@ -0,0 +1,5 @@
---
description: 'Conduct comprehensive research across multiple domains using current web data and verified sources - Market, Technical, Domain and other research types.'
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/1-analysis/research/workflow.md, READ its entire contents and follow its directions exactly!

13
.claude/commands/bmad/bmm/workflows/retrospective.md Normal file
View File

@@ -0,0 +1,13 @@
---
description: 'Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic'
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

13
.claude/commands/bmad/bmm/workflows/sprint-planning.md Normal file
View File

@@ -0,0 +1,13 @@
---
description: 'Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle'
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

13
.claude/commands/bmad/bmm/workflows/sprint-status.md Normal file
View File

@@ -0,0 +1,13 @@
---
description: 'Summarize sprint-status.yaml, surface risks, and route to the right implementation workflow.'
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

13
.claude/commands/bmad/bmm/workflows/testarch-atdd.md Normal file
View File

@@ -0,0 +1,13 @@
---
description: 'Generate failing acceptance tests before implementation using TDD red-green-refactor cycle'
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/atdd/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/testarch/atdd/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

13
.claude/commands/bmad/bmm/workflows/testarch-automate.md Normal file
View File

@@ -0,0 +1,13 @@
---
description: 'Expand test automation coverage after implementation or analyze existing codebase to generate comprehensive test suite'
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/automate/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/testarch/automate/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

13
.claude/commands/bmad/bmm/workflows/testarch-ci.md Normal file
View File

@@ -0,0 +1,13 @@
---
description: 'Scaffold CI/CD quality pipeline with test execution, burn-in loops, and artifact collection'
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/ci/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/testarch/ci/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

13
.claude/commands/bmad/bmm/workflows/testarch-framework.md Normal file
View File

@@ -0,0 +1,13 @@
---
description: 'Initialize production-ready test framework architecture (Playwright or Cypress) with fixtures, helpers, and configuration'
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/framework/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/testarch/framework/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

13
.claude/commands/bmad/bmm/workflows/testarch-nfr.md Normal file
View File

@@ -0,0 +1,13 @@
---
description: 'Assess non-functional requirements (performance, security, reliability, maintainability) before release with evidence-based validation'
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

13
.claude/commands/bmad/bmm/workflows/testarch-test-design.md Normal file
View File

@@ -0,0 +1,13 @@
---
description: 'Dual-mode workflow: (1) System-level testability review in Solutioning phase, or (2) Epic-level test planning in Implementation phase. Auto-detects mode based on project phase.'
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/test-design/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/testarch/test-design/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

13
.claude/commands/bmad/bmm/workflows/testarch-test-review.md Normal file
View File

@@ -0,0 +1,13 @@
---
description: 'Review test quality using comprehensive knowledge base and best practices validation'
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/test-review/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/testarch/test-review/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

13
.claude/commands/bmad/bmm/workflows/testarch-trace.md Normal file
View File

@@ -0,0 +1,13 @@
---
description: 'Generate requirements-to-tests traceability matrix, analyze coverage, and make quality gate decision (PASS/CONCERNS/FAIL/WAIVED)'
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/trace/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/testarch/trace/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

13
.claude/commands/bmad/bmm/workflows/workflow-init.md Normal file
View File

@@ -0,0 +1,13 @@
---
description: 'Initialize a new BMM project by determining level, type, and creating workflow path'
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/workflow-status/init/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/workflow-status/init/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

13
.claude/commands/bmad/bmm/workflows/workflow-status.md Normal file
View File

@@ -0,0 +1,13 @@
---
description: 'Lightweight status checker - answers ""what should I do now?"" for any agent. Reads YAML status file for workflow tracking. Use workflow-init for new projects.'
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/workflow-status/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/workflow-status/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

14
.claude/commands/bmad/core/agents/bmad-master.md Normal file
View File

@@ -0,0 +1,14 @@
---
name: 'bmad-master'
description: 'bmad-master agent'
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/core/agents/bmad-master.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

9
.claude/commands/bmad/core/tasks/index-docs.md Normal file
View File

@@ -0,0 +1,9 @@
---
description: 'Generates or updates an index.md of all documents in the specified directory'
---
# Index Docs
LOAD and execute the task at: _bmad/core/tasks/index-docs.xml
Follow all instructions in the task file exactly as written.

5
.claude/commands/bmad/core/workflows/brainstorming.md Normal file
View File

@@ -0,0 +1,5 @@
---
description: 'Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods'
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/core/workflows/brainstorming/workflow.md, READ its entire contents and follow its directions exactly!

5
.claude/commands/bmad/core/workflows/party-mode.md Normal file
View File

@@ -0,0 +1,5 @@
---
description: 'Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations'
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/core/workflows/party-mode/workflow.md, READ its entire contents and follow its directions exactly!