Merge pull request 'epic-ux-design' (#1) from epic-ux-design into main

Reviewed-on: #1
This commit is contained in:
sepehr 2026-02-21 15:23:54 +01:00
commit e2ddfa53d4
971 changed files with 188002 additions and 37386 deletions

View File

@ -0,0 +1,16 @@
---
name: 'bmad-master'
description: 'bmad-master agent'
disable-model-invocation: true
---
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 {project-root}/_bmad/core/agents/bmad-master.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. FOLLOW every step in the <activation> section precisely
4. DISPLAY the welcome/greeting as instructed
5. PRESENT the numbered menu
6. WAIT for user input before proceeding
</agent-activation>

View File

@ -0,0 +1,16 @@
---
name: 'analyst'
description: 'analyst agent'
disable-model-invocation: true
---
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 {project-root}/_bmad/bmm/agents/analyst.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. FOLLOW every step in the <activation> section precisely
4. DISPLAY the welcome/greeting as instructed
5. PRESENT the numbered menu
6. WAIT for user input before proceeding
</agent-activation>

View File

@ -0,0 +1,16 @@
---
name: 'architect'
description: 'architect agent'
disable-model-invocation: true
---
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 {project-root}/_bmad/bmm/agents/architect.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. FOLLOW every step in the <activation> section precisely
4. DISPLAY the welcome/greeting as instructed
5. PRESENT the numbered menu
6. WAIT for user input before proceeding
</agent-activation>

View File

@ -0,0 +1,16 @@
---
name: 'dev'
description: 'dev agent'
disable-model-invocation: true
---
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 {project-root}/_bmad/bmm/agents/dev.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. FOLLOW every step in the <activation> section precisely
4. DISPLAY the welcome/greeting as instructed
5. PRESENT the numbered menu
6. WAIT for user input before proceeding
</agent-activation>

View File

@ -0,0 +1,16 @@
---
name: 'pm'
description: 'pm agent'
disable-model-invocation: true
---
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 {project-root}/_bmad/bmm/agents/pm.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. FOLLOW every step in the <activation> section precisely
4. DISPLAY the welcome/greeting as instructed
5. PRESENT the numbered menu
6. WAIT for user input before proceeding
</agent-activation>

View File

@ -0,0 +1,16 @@
---
name: 'qa'
description: 'qa agent'
disable-model-invocation: true
---
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 {project-root}/_bmad/bmm/agents/qa.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. FOLLOW every step in the <activation> section precisely
4. DISPLAY the welcome/greeting as instructed
5. PRESENT the numbered menu
6. WAIT for user input before proceeding
</agent-activation>

View File

@ -0,0 +1,16 @@
---
name: 'quick-flow-solo-dev'
description: 'quick-flow-solo-dev agent'
disable-model-invocation: true
---
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 {project-root}/_bmad/bmm/agents/quick-flow-solo-dev.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. FOLLOW every step in the <activation> section precisely
4. DISPLAY the welcome/greeting as instructed
5. PRESENT the numbered menu
6. WAIT for user input before proceeding
</agent-activation>

View File

@ -0,0 +1,16 @@
---
name: 'sm'
description: 'sm agent'
disable-model-invocation: true
---
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 {project-root}/_bmad/bmm/agents/sm.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. FOLLOW every step in the <activation> section precisely
4. DISPLAY the welcome/greeting as instructed
5. PRESENT the numbered menu
6. WAIT for user input before proceeding
</agent-activation>

View File

@ -0,0 +1,16 @@
---
name: 'tech-writer'
description: 'tech-writer agent'
disable-model-invocation: true
---
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 {project-root}/_bmad/bmm/agents/tech-writer/tech-writer.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. FOLLOW every step in the <activation> section precisely
4. DISPLAY the welcome/greeting as instructed
5. PRESENT the numbered menu
6. WAIT for user input before proceeding
</agent-activation>

View File

@ -0,0 +1,16 @@
---
name: 'ux-designer'
description: 'ux-designer agent'
disable-model-invocation: true
---
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 {project-root}/_bmad/bmm/agents/ux-designer.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. FOLLOW every step in the <activation> section precisely
4. DISPLAY the welcome/greeting as instructed
5. PRESENT the numbered menu
6. WAIT for user input before proceeding
</agent-activation>

View File

@ -0,0 +1,7 @@
---
name: 'check-implementation-readiness'
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.'
disable-model-invocation: true
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md, READ its entire contents and follow its directions exactly!

View File

@ -0,0 +1,15 @@
---
name: 'code-review'
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.'
disable-model-invocation: true
---
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 @{project-root}/_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml
3. Pass the yaml path @{project-root}/_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>

View File

@ -0,0 +1,15 @@
---
name: 'correct-course'
description: 'Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation'
disable-model-invocation: true
---
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 @{project-root}/_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml
3. Pass the yaml path @{project-root}/_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>

View File

@ -0,0 +1,7 @@
---
name: 'create-architecture'
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.'
disable-model-invocation: true
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md, READ its entire contents and follow its directions exactly!

View File

@ -0,0 +1,7 @@
---
name: 'create-epics-and-stories'
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.'
disable-model-invocation: true
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md, READ its entire contents and follow its directions exactly!

View File

@ -0,0 +1,7 @@
---
name: 'create-prd'
description: 'Create a comprehensive PRD (Product Requirements Document) through structured workflow facilitation'
disable-model-invocation: true
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-create-prd.md, READ its entire contents and follow its directions exactly!

View File

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

View File

@ -0,0 +1,15 @@
---
name: 'create-story'
description: 'Create the next user story from epics+stories with enhanced context analysis and direct ready-for-dev marking'
disable-model-invocation: true
---
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 @{project-root}/_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml
3. Pass the yaml path @{project-root}/_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>

View File

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

View File

@ -0,0 +1,15 @@
---
name: 'dev-story'
description: 'Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria'
disable-model-invocation: true
---
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 @{project-root}/_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml
3. Pass the yaml path @{project-root}/_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>

View File

@ -0,0 +1,15 @@
---
name: 'document-project'
description: 'Analyzes and documents brownfield projects by scanning codebase, architecture, and patterns to create comprehensive reference documentation for AI-assisted development'
disable-model-invocation: true
---
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 @{project-root}/_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/document-project/workflow.yaml
3. Pass the yaml path @{project-root}/_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>

View File

@ -0,0 +1,7 @@
---
name: 'domain-research'
description: 'Conduct domain research covering industry analysis, regulations, technology trends, and ecosystem dynamics using current web data and verified sources.'
disable-model-invocation: true
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/1-analysis/research/workflow-domain-research.md, READ its entire contents and follow its directions exactly!

View File

@ -0,0 +1,7 @@
---
name: 'edit-prd'
description: 'Edit and improve an existing PRD - enhance clarity, completeness, and quality'
disable-model-invocation: true
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-edit-prd.md, READ its entire contents and follow its directions exactly!

View File

@ -0,0 +1,7 @@
---
name: 'generate-project-context'
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.'
disable-model-invocation: true
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/generate-project-context/workflow.md, READ its entire contents and follow its directions exactly!

View File

@ -0,0 +1,7 @@
---
name: 'market-research'
description: 'Conduct market research covering market size, growth, competition, and customer insights using current web data and verified sources.'
disable-model-invocation: true
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/1-analysis/research/workflow-market-research.md, READ its entire contents and follow its directions exactly!

View File

@ -0,0 +1,15 @@
---
name: 'qa-automate'
description: 'Generate tests quickly for existing features using standard test patterns'
disable-model-invocation: true
---
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 @{project-root}/_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/qa/automate/workflow.yaml
3. Pass the yaml path @{project-root}/_bmad/bmm/workflows/qa/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>

View File

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

View File

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

View File

@ -0,0 +1,15 @@
---
name: 'retrospective'
description: 'Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic'
disable-model-invocation: true
---
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 @{project-root}/_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml
3. Pass the yaml path @{project-root}/_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>

View File

@ -0,0 +1,15 @@
---
name: 'sprint-planning'
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'
disable-model-invocation: true
---
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 @{project-root}/_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml
3. Pass the yaml path @{project-root}/_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>

View File

@ -0,0 +1,15 @@
---
name: 'sprint-status'
description: 'Summarize sprint-status.yaml, surface risks, and route to the right implementation workflow.'
disable-model-invocation: true
---
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 @{project-root}/_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml
3. Pass the yaml path @{project-root}/_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>

View File

@ -0,0 +1,7 @@
---
name: 'technical-research'
description: 'Conduct technical research covering technology evaluation, architecture decisions, and implementation approaches using current web data and verified sources.'
disable-model-invocation: true
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/1-analysis/research/workflow-technical-research.md, READ its entire contents and follow its directions exactly!

View File

@ -0,0 +1,7 @@
---
name: 'validate-prd'
description: 'Validate an existing PRD against BMAD standards - comprehensive review for completeness, clarity, and quality'
disable-model-invocation: true
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-validate-prd.md, READ its entire contents and follow its directions exactly!

View File

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

View File

@ -0,0 +1,10 @@
---
name: 'editorial-review-prose'
description: 'Clinical copy-editor that reviews text for communication issues'
---
# editorial-review-prose
Read the entire task file at: {project-root}/_bmad/core/tasks/editorial-review-prose.xml
Follow all instructions in the task file exactly as written.

View File

@ -0,0 +1,10 @@
---
name: 'editorial-review-structure'
description: 'Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension'
---
# editorial-review-structure
Read the entire task file at: {project-root}/_bmad/core/tasks/editorial-review-structure.xml
Follow all instructions in the task file exactly as written.

View File

@ -0,0 +1,10 @@
---
name: 'help'
description: 'Get unstuck by showing what workflow steps come next or answering questions about what to do'
---
# help
Read the entire task file at: {project-root}/_bmad/core/tasks/help.md
Follow all instructions in the task file exactly as written.

View File

@ -0,0 +1,10 @@
---
name: 'index-docs'
description: 'Generates or updates an index.md of all documents in the specified directory'
---
# index-docs
Read the entire task file at: {project-root}/_bmad/core/tasks/index-docs.xml
Follow all instructions in the task file exactly as written.

View File

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

View File

@ -0,0 +1,10 @@
---
name: 'review-adversarial-general'
description: 'Cynically review content and produce findings'
---
# review-adversarial-general
Read the entire task file at: {project-root}/_bmad/core/tasks/review-adversarial-general.xml
Follow all instructions in the task file exactly as written.

View File

@ -0,0 +1,10 @@
---
name: 'shard-doc'
description: 'Splits large markdown documents into smaller, organized files based on level 2 (default) sections'
---
# shard-doc
Read the entire task file at: {project-root}/_bmad/core/tasks/shard-doc.xml
Follow all instructions in the task file exactly as written.

View File

@ -0,0 +1,10 @@
---
name: 'validate-workflow'
description: 'Run a checklist against a document with thorough analysis and produce a validation report'
---
# validate-workflow
Read the entire task file at: {project-root}/_bmad/core/tasks/validate-workflow.xml
Follow all instructions in the task file exactly as written.

View File

@ -0,0 +1,10 @@
---
name: 'workflow'
description: 'Execute given workflow by loading its configuration, following instructions, and producing output'
---
# workflow
Read the entire task file at: {project-root}/_bmad/core/tasks/workflow.xml
Follow all instructions in the task file exactly as written.

View File

@ -0,0 +1,16 @@
---
name: 'bmad-master'
description: 'bmad-master agent'
disable-model-invocation: true
---
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 {project-root}/_bmad/core/agents/bmad-master.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. FOLLOW every step in the <activation> section precisely
4. DISPLAY the welcome/greeting as instructed
5. PRESENT the numbered menu
6. WAIT for user input before proceeding
</agent-activation>

View File

@ -0,0 +1,16 @@
---
name: 'analyst'
description: 'analyst agent'
disable-model-invocation: true
---
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 {project-root}/_bmad/bmm/agents/analyst.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. FOLLOW every step in the <activation> section precisely
4. DISPLAY the welcome/greeting as instructed
5. PRESENT the numbered menu
6. WAIT for user input before proceeding
</agent-activation>

View File

@ -0,0 +1,16 @@
---
name: 'architect'
description: 'architect agent'
disable-model-invocation: true
---
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 {project-root}/_bmad/bmm/agents/architect.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. FOLLOW every step in the <activation> section precisely
4. DISPLAY the welcome/greeting as instructed
5. PRESENT the numbered menu
6. WAIT for user input before proceeding
</agent-activation>

View File

@ -0,0 +1,16 @@
---
name: 'dev'
description: 'dev agent'
disable-model-invocation: true
---
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 {project-root}/_bmad/bmm/agents/dev.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. FOLLOW every step in the <activation> section precisely
4. DISPLAY the welcome/greeting as instructed
5. PRESENT the numbered menu
6. WAIT for user input before proceeding
</agent-activation>

View File

@ -0,0 +1,16 @@
---
name: 'pm'
description: 'pm agent'
disable-model-invocation: true
---
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 {project-root}/_bmad/bmm/agents/pm.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. FOLLOW every step in the <activation> section precisely
4. DISPLAY the welcome/greeting as instructed
5. PRESENT the numbered menu
6. WAIT for user input before proceeding
</agent-activation>

View File

@ -0,0 +1,16 @@
---
name: 'qa'
description: 'qa agent'
disable-model-invocation: true
---
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 {project-root}/_bmad/bmm/agents/qa.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. FOLLOW every step in the <activation> section precisely
4. DISPLAY the welcome/greeting as instructed
5. PRESENT the numbered menu
6. WAIT for user input before proceeding
</agent-activation>

View File

@ -0,0 +1,16 @@
---
name: 'quick-flow-solo-dev'
description: 'quick-flow-solo-dev agent'
disable-model-invocation: true
---
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 {project-root}/_bmad/bmm/agents/quick-flow-solo-dev.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. FOLLOW every step in the <activation> section precisely
4. DISPLAY the welcome/greeting as instructed
5. PRESENT the numbered menu
6. WAIT for user input before proceeding
</agent-activation>

View File

@ -0,0 +1,16 @@
---
name: 'sm'
description: 'sm agent'
disable-model-invocation: true
---
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 {project-root}/_bmad/bmm/agents/sm.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. FOLLOW every step in the <activation> section precisely
4. DISPLAY the welcome/greeting as instructed
5. PRESENT the numbered menu
6. WAIT for user input before proceeding
</agent-activation>

View File

@ -0,0 +1,16 @@
---
name: 'tech-writer'
description: 'tech-writer agent'
disable-model-invocation: true
---
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 {project-root}/_bmad/bmm/agents/tech-writer/tech-writer.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. FOLLOW every step in the <activation> section precisely
4. DISPLAY the welcome/greeting as instructed
5. PRESENT the numbered menu
6. WAIT for user input before proceeding
</agent-activation>

View File

@ -0,0 +1,16 @@
---
name: 'ux-designer'
description: 'ux-designer agent'
disable-model-invocation: true
---
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 {project-root}/_bmad/bmm/agents/ux-designer.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. FOLLOW every step in the <activation> section precisely
4. DISPLAY the welcome/greeting as instructed
5. PRESENT the numbered menu
6. WAIT for user input before proceeding
</agent-activation>

View File

@ -0,0 +1,7 @@
---
name: 'check-implementation-readiness'
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.'
disable-model-invocation: true
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md, READ its entire contents and follow its directions exactly!

View File

@ -0,0 +1,15 @@
---
name: 'code-review'
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.'
disable-model-invocation: true
---
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 @{project-root}/_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml
3. Pass the yaml path @{project-root}/_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>

View File

@ -0,0 +1,15 @@
---
name: 'correct-course'
description: 'Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation'
disable-model-invocation: true
---
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 @{project-root}/_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml
3. Pass the yaml path @{project-root}/_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>

View File

@ -0,0 +1,7 @@
---
name: 'create-architecture'
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.'
disable-model-invocation: true
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md, READ its entire contents and follow its directions exactly!

View File

@ -0,0 +1,7 @@
---
name: 'create-epics-and-stories'
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.'
disable-model-invocation: true
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md, READ its entire contents and follow its directions exactly!

View File

@ -0,0 +1,7 @@
---
name: 'create-prd'
description: 'Create a comprehensive PRD (Product Requirements Document) through structured workflow facilitation'
disable-model-invocation: true
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-create-prd.md, READ its entire contents and follow its directions exactly!

View File

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

View File

@ -0,0 +1,15 @@
---
name: 'create-story'
description: 'Create the next user story from epics+stories with enhanced context analysis and direct ready-for-dev marking'
disable-model-invocation: true
---
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 @{project-root}/_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml
3. Pass the yaml path @{project-root}/_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>

View File

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

View File

@ -0,0 +1,15 @@
---
name: 'dev-story'
description: 'Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria'
disable-model-invocation: true
---
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 @{project-root}/_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml
3. Pass the yaml path @{project-root}/_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>

View File

@ -0,0 +1,15 @@
---
name: 'document-project'
description: 'Analyzes and documents brownfield projects by scanning codebase, architecture, and patterns to create comprehensive reference documentation for AI-assisted development'
disable-model-invocation: true
---
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 @{project-root}/_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/document-project/workflow.yaml
3. Pass the yaml path @{project-root}/_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>

View File

@ -0,0 +1,7 @@
---
name: 'domain-research'
description: 'Conduct domain research covering industry analysis, regulations, technology trends, and ecosystem dynamics using current web data and verified sources.'
disable-model-invocation: true
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/1-analysis/research/workflow-domain-research.md, READ its entire contents and follow its directions exactly!

View File

@ -0,0 +1,7 @@
---
name: 'edit-prd'
description: 'Edit and improve an existing PRD - enhance clarity, completeness, and quality'
disable-model-invocation: true
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-edit-prd.md, READ its entire contents and follow its directions exactly!

View File

@ -0,0 +1,7 @@
---
name: 'generate-project-context'
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.'
disable-model-invocation: true
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/generate-project-context/workflow.md, READ its entire contents and follow its directions exactly!

View File

@ -0,0 +1,7 @@
---
name: 'market-research'
description: 'Conduct market research covering market size, growth, competition, and customer insights using current web data and verified sources.'
disable-model-invocation: true
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/1-analysis/research/workflow-market-research.md, READ its entire contents and follow its directions exactly!

View File

@ -0,0 +1,15 @@
---
name: 'qa-automate'
description: 'Generate tests quickly for existing features using standard test patterns'
disable-model-invocation: true
---
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 @{project-root}/_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/qa/automate/workflow.yaml
3. Pass the yaml path @{project-root}/_bmad/bmm/workflows/qa/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>

View File

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

View File

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

View File

@ -0,0 +1,15 @@
---
name: 'retrospective'
description: 'Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic'
disable-model-invocation: true
---
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 @{project-root}/_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml
3. Pass the yaml path @{project-root}/_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>

View File

@ -0,0 +1,15 @@
---
name: 'sprint-planning'
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'
disable-model-invocation: true
---
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 @{project-root}/_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml
3. Pass the yaml path @{project-root}/_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>

View File

@ -0,0 +1,15 @@
---
name: 'sprint-status'
description: 'Summarize sprint-status.yaml, surface risks, and route to the right implementation workflow.'
disable-model-invocation: true
---
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 @{project-root}/_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml
3. Pass the yaml path @{project-root}/_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>

View File

@ -0,0 +1,7 @@
---
name: 'technical-research'
description: 'Conduct technical research covering technology evaluation, architecture decisions, and implementation approaches using current web data and verified sources.'
disable-model-invocation: true
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/1-analysis/research/workflow-technical-research.md, READ its entire contents and follow its directions exactly!

View File

@ -0,0 +1,7 @@
---
name: 'validate-prd'
description: 'Validate an existing PRD against BMAD standards - comprehensive review for completeness, clarity, and quality'
disable-model-invocation: true
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-validate-prd.md, READ its entire contents and follow its directions exactly!

View File

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

View File

@ -0,0 +1,10 @@
---
name: 'editorial-review-prose'
description: 'Clinical copy-editor that reviews text for communication issues'
---
# editorial-review-prose
Read the entire task file at: {project-root}/_bmad/core/tasks/editorial-review-prose.xml
Follow all instructions in the task file exactly as written.

View File

@ -0,0 +1,10 @@
---
name: 'editorial-review-structure'
description: 'Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension'
---
# editorial-review-structure
Read the entire task file at: {project-root}/_bmad/core/tasks/editorial-review-structure.xml
Follow all instructions in the task file exactly as written.

View File

@ -0,0 +1,10 @@
---
name: 'help'
description: 'Get unstuck by showing what workflow steps come next or answering questions about what to do'
---
# help
Read the entire task file at: {project-root}/_bmad/core/tasks/help.md
Follow all instructions in the task file exactly as written.

View File

@ -0,0 +1,10 @@
---
name: 'index-docs'
description: 'Generates or updates an index.md of all documents in the specified directory'
---
# index-docs
Read the entire task file at: {project-root}/_bmad/core/tasks/index-docs.xml
Follow all instructions in the task file exactly as written.

View File

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

View File

@ -0,0 +1,10 @@
---
name: 'review-adversarial-general'
description: 'Cynically review content and produce findings'
---
# review-adversarial-general
Read the entire task file at: {project-root}/_bmad/core/tasks/review-adversarial-general.xml
Follow all instructions in the task file exactly as written.

View File

@ -0,0 +1,10 @@
---
name: 'shard-doc'
description: 'Splits large markdown documents into smaller, organized files based on level 2 (default) sections'
---
# shard-doc
Read the entire task file at: {project-root}/_bmad/core/tasks/shard-doc.xml
Follow all instructions in the task file exactly as written.

View File

@ -0,0 +1,10 @@
---
name: 'validate-workflow'
description: 'Run a checklist against a document with thorough analysis and produce a validation report'
---
# validate-workflow
Read the entire task file at: {project-root}/_bmad/core/tasks/validate-workflow.xml
Follow all instructions in the task file exactly as written.

View File

@ -0,0 +1,10 @@
---
name: 'workflow'
description: 'Execute given workflow by loading its configuration, following instructions, and producing output'
---
# workflow
Read the entire task file at: {project-root}/_bmad/core/tasks/workflow.xml
Follow all instructions in the task file exactly as written.

View File

@ -0,0 +1,69 @@
{
"permissions": {
"allow": [
"Bash(dir:*)",
"Bash(findstr:*)",
"Bash(test:*)",
"Bash(tree:*)",
"Bash(find:*)",
"Bash(npm install:*)",
"Bash(npx prisma generate:*)",
"Bash(npx prisma migrate dev:*)",
"Bash(npx prisma db push:*)",
"Bash(npm run build:*)",
"Bash(grep:*)",
"Bash(netstat:*)",
"Skill(bmad:bmm:agents:pm)",
"WebSearch",
"Bash(powershell:*)",
"Bash(npm run dev:*)",
"mcp__zread__read_file",
"mcp__zread__search_doc",
"Bash(npx prisma studio:*)",
"Bash(timeout:*)",
"mcp__web-reader__webReader",
"Bash(taskkill:*)",
"Bash(sqlite3:*)",
"Bash(node scripts/check-labels.js:*)",
"Bash(curl:*)",
"Bash(python:*)",
"Bash(npm test:*)",
"Skill(bmad:bmm:agents:ux-designer)",
"Skill(bmad:bmm:workflows:create-prd)",
"Bash(ls:*)",
"Bash(cat:*)",
"Bash(ping:*)",
"Bash(tasklist:*)",
"Bash(npm uninstall:*)",
"Bash(node:*)",
"Bash(npx tsx:*)",
"Bash(npx tsc:*)",
"mcp__zai-mcp-server__analyze_image",
"Skill(bmad:bmm:agents:architect)",
"Bash(git log:*)",
"Skill(bmad:bmm:workflows:workflow-status)",
"Skill(bmad:bmm:workflows:sprint-planning)",
"Bash(done)",
"Bash(for:*)",
"Bash(do echo:*)",
"Bash(chmod:*)",
"Bash(git add:*)",
"Bash(git commit:*)",
"Bash(git push:*)",
"Bash(docker compose:*)",
"mcp__context7__resolve-library-id",
"mcp__web-search-prime__webSearchPrime",
"mcp__context7__query-docs",
"Bash(docker logs:*)",
"Bash(docker run:*)",
"Bash(docker exec:*)",
"Bash(git reset:*)",
"Bash(npx prisma:*)",
"Bash(npx playwright test:*)",
"Skill(bmad:bmm:workflows:create-story)",
"Bash(tee:*)",
"Bash(npx playwright codegen:*)",
"Bash(pkill:*)"
]
}
}

2984
.cursor/debug.log Normal file

File diff suppressed because it is too large Load Diff

27
.env.docker Normal file
View File

@ -0,0 +1,27 @@
# ============================================
# Docker / Production Environment
# ============================================
# Update NEXTAUTH_URL with your server IP or domain
NEXTAUTH_URL="http://192.168.1.190:3000"
# ============================================
# AI Provider Configuration
# ============================================
AI_PROVIDER=ollama
OLLAMA_BASE_URL="http://ollama:11434"
OLLAMA_MODEL="granite4:latest"
# ============================================
# Email Configuration (Optional)
# ============================================
# Uncomment and configure for email features
# SMTP_HOST="smtp.gmail.com"
# SMTP_PORT="587"
# SMTP_USER="your-email@gmail.com"
# SMTP_PASS="your-app-password"
# SMTP_FROM="noreply@memento.app"
# ============================================
# OpenAI (Optional)
# ============================================
# OPENAI_API_KEY="sk-..."

67
.env.docker.example Normal file
View File

@ -0,0 +1,67 @@
# ============================================
# Docker / Production Environment Template
# ============================================
# Copy this file to .env.docker and update with your server IP/domain
# IMPORTANT: Update NEXTAUTH_URL with your server IP or domain name
# Examples:
# - IP: NEXTAUTH_URL="http://192.168.1.190:3000"
# - Domain: NEXTAUTH_URL="http://your-domain.com"
# - HTTPS: NEXTAUTH_URL="https://your-domain.com"
NEXTAUTH_URL="http://YOUR_SERVER_IP:3000"
# ============================================
# MCP Server Configuration
# ============================================
# Choose the MCP server mode:
# - 'stdio': Standard I/O mode (default) - for Claude Desktop, Cline, etc.
# - 'sse': Server-Sent Events mode - for N8N HTTP transport, remote access
MCP_MODE="stdio"
MCP_PORT="3001"
# ============================================
# AI Provider Configuration
# ============================================
# You can configure separate providers for tags and embeddings
# Options: ollama, openai, custom
# For local Ollama in Docker (service name):
# AI_PROVIDER_TAGS=ollama
# AI_PROVIDER_EMBEDDING=ollama
# OLLAMA_BASE_URL="http://ollama:11434"
# AI_MODEL_TAGS="granite4:latest"
# AI_MODEL_EMBEDDING="embeddinggemma:latest"
# For external Ollama (on host or different server):
# AI_PROVIDER_TAGS=ollama
# AI_PROVIDER_EMBEDDING=ollama
# OLLAMA_BASE_URL="http://YOUR_SERVER_IP:11434"
# AI_MODEL_TAGS="granite4:latest"
# AI_MODEL_EMBEDDING="embeddinggemma:latest"
# For OpenAI (recommended for production):
# AI_PROVIDER_TAGS=openai
# AI_PROVIDER_EMBEDDING=openai
# OPENAI_API_KEY="sk-..."
# AI_MODEL_TAGS="gpt-4o-mini"
# AI_MODEL_EMBEDDING="text-embedding-3-small"
# Mixed setup (e.g., Ollama for tags, OpenAI for embeddings):
# AI_PROVIDER_TAGS=ollama
# AI_PROVIDER_EMBEDDING=openai
# OLLAMA_BASE_URL="http://ollama:11434"
# OPENAI_API_KEY="sk-..."
# AI_MODEL_TAGS="granite4:latest"
# AI_MODEL_EMBEDDING="text-embedding-3-small"
# ============================================
# Email Configuration (Optional)
# ============================================
# Uncomment and configure for email features (password reset, reminders)
# SMTP_HOST="smtp.gmail.com"
# SMTP_PORT="587"
# SMTP_USER="your-email@gmail.com"
# SMTP_PASS="your-app-password"
# SMTP_FROM="noreply@memento.app"

45
.env.example Normal file
View File

@ -0,0 +1,45 @@
# ============================================
# Database Configuration
# ============================================
DATABASE_URL="file:/app/prisma/dev.db"
# ============================================
# NextAuth Configuration
# ============================================
# Generate with: openssl rand -base64 32
NEXTAUTH_SECRET="change-this-to-a-random-string-at-least-32-characters-long"
# For local development: NEXTAUTH_URL="http://localhost:3000"
# For Docker/Production: NEXTAUTH_URL="http://YOUR_SERVER_IP:3000"
NEXTAUTH_URL="http://localhost:3000"
# ============================================
# Email Configuration (SMTP)
# ============================================
# Required for password reset and reminders
SMTP_HOST="smtp.gmail.com"
SMTP_PORT="587"
SMTP_USER="your-email@gmail.com"
SMTP_PASS="your-app-password"
SMTP_FROM="noreply@memento.app"
# ============================================
# AI Provider Configuration
# ============================================
# OpenAI (Optional - for GPT models)
OPENAI_API_KEY="sk-..."
# Ollama (Optional - for local models)
OLLAMA_API_URL="http://ollama:11434"
# ============================================
# Application Settings
# ============================================
NODE_ENV="production"
PORT="3000"
# ============================================
# Docker-Specific Settings
# ============================================
# These are usually set in docker-compose.yml
# Keep for local development reference

View File

@ -0,0 +1,14 @@
description = "Activates the bmad-master agent from the BMad Method."
prompt = """
CRITICAL: You are now the BMad 'bmad-master' agent.
PRE-FLIGHT CHECKLIST:
1. [ ] IMMEDIATE ACTION: Load and parse {project-root}/_bmad/core/config.yaml - store ALL config values in memory for use throughout the session.
2. [ ] IMMEDIATE ACTION: Read and internalize the full agent definition at {project-root}/_bmad/core/agents/bmad-master.md.
3. [ ] CONFIRM: The user's name from config is {user_name}.
Only after all checks are complete, greet the user by name and display the menu.
Acknowledge this checklist is complete in your first response.
AGENT DEFINITION: {project-root}/_bmad/core/agents/bmad-master.md
"""

View File

@ -1,12 +1,14 @@
description = "BMAD BMM Agent: Analyst" description = "Activates the analyst agent from the BMad Method."
prompt = """ prompt = """
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command. CRITICAL: You are now the BMad 'analyst' agent.
<agent-activation CRITICAL="TRUE"> PRE-FLIGHT CHECKLIST:
1. LOAD the FULL agent file from @_bmad/bmm/agents/analyst.md 1. [ ] IMMEDIATE ACTION: Load and parse {project-root}/_bmad/bmm/config.yaml - store ALL config values in memory for use throughout the session.
2. READ its entire contents - this contains the complete agent persona, menu, and instructions 2. [ ] IMMEDIATE ACTION: Read and internalize the full agent definition at {project-root}/_bmad/bmm/agents/analyst.md.
3. Execute ALL activation steps exactly as written in the agent file 3. [ ] CONFIRM: The user's name from config is {user_name}.
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session Only after all checks are complete, greet the user by name and display the menu.
</agent-activation> Acknowledge this checklist is complete in your first response.
AGENT DEFINITION: {project-root}/_bmad/bmm/agents/analyst.md
""" """

View File

@ -1,12 +1,14 @@
description = "BMAD BMM Agent: Architect" description = "Activates the architect agent from the BMad Method."
prompt = """ prompt = """
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command. CRITICAL: You are now the BMad 'architect' agent.
<agent-activation CRITICAL="TRUE"> PRE-FLIGHT CHECKLIST:
1. LOAD the FULL agent file from @_bmad/bmm/agents/architect.md 1. [ ] IMMEDIATE ACTION: Load and parse {project-root}/_bmad/bmm/config.yaml - store ALL config values in memory for use throughout the session.
2. READ its entire contents - this contains the complete agent persona, menu, and instructions 2. [ ] IMMEDIATE ACTION: Read and internalize the full agent definition at {project-root}/_bmad/bmm/agents/architect.md.
3. Execute ALL activation steps exactly as written in the agent file 3. [ ] CONFIRM: The user's name from config is {user_name}.
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session Only after all checks are complete, greet the user by name and display the menu.
</agent-activation> Acknowledge this checklist is complete in your first response.
AGENT DEFINITION: {project-root}/_bmad/bmm/agents/architect.md
""" """

View File

@ -1,12 +1,14 @@
description = "BMAD BMM Agent: Dev" description = "Activates the dev agent from the BMad Method."
prompt = """ prompt = """
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command. CRITICAL: You are now the BMad 'dev' agent.
<agent-activation CRITICAL="TRUE"> PRE-FLIGHT CHECKLIST:
1. LOAD the FULL agent file from @_bmad/bmm/agents/dev.md 1. [ ] IMMEDIATE ACTION: Load and parse {project-root}/_bmad/bmm/config.yaml - store ALL config values in memory for use throughout the session.
2. READ its entire contents - this contains the complete agent persona, menu, and instructions 2. [ ] IMMEDIATE ACTION: Read and internalize the full agent definition at {project-root}/_bmad/bmm/agents/dev.md.
3. Execute ALL activation steps exactly as written in the agent file 3. [ ] CONFIRM: The user's name from config is {user_name}.
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session Only after all checks are complete, greet the user by name and display the menu.
</agent-activation> Acknowledge this checklist is complete in your first response.
AGENT DEFINITION: {project-root}/_bmad/bmm/agents/dev.md
""" """

View File

@ -1,12 +1,14 @@
description = "BMAD BMM Agent: Pm" description = "Activates the pm agent from the BMad Method."
prompt = """ prompt = """
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command. CRITICAL: You are now the BMad 'pm' agent.
<agent-activation CRITICAL="TRUE"> PRE-FLIGHT CHECKLIST:
1. LOAD the FULL agent file from @_bmad/bmm/agents/pm.md 1. [ ] IMMEDIATE ACTION: Load and parse {project-root}/_bmad/bmm/config.yaml - store ALL config values in memory for use throughout the session.
2. READ its entire contents - this contains the complete agent persona, menu, and instructions 2. [ ] IMMEDIATE ACTION: Read and internalize the full agent definition at {project-root}/_bmad/bmm/agents/pm.md.
3. Execute ALL activation steps exactly as written in the agent file 3. [ ] CONFIRM: The user's name from config is {user_name}.
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session Only after all checks are complete, greet the user by name and display the menu.
</agent-activation> Acknowledge this checklist is complete in your first response.
AGENT DEFINITION: {project-root}/_bmad/bmm/agents/pm.md
""" """

View File

@ -0,0 +1,14 @@
description = "Activates the qa agent from the BMad Method."
prompt = """
CRITICAL: You are now the BMad 'qa' agent.
PRE-FLIGHT CHECKLIST:
1. [ ] IMMEDIATE ACTION: Load and parse {project-root}/_bmad/bmm/config.yaml - store ALL config values in memory for use throughout the session.
2. [ ] IMMEDIATE ACTION: Read and internalize the full agent definition at {project-root}/_bmad/bmm/agents/qa.md.
3. [ ] CONFIRM: The user's name from config is {user_name}.
Only after all checks are complete, greet the user by name and display the menu.
Acknowledge this checklist is complete in your first response.
AGENT DEFINITION: {project-root}/_bmad/bmm/agents/qa.md
"""

View File

@ -1,12 +1,14 @@
description = "BMAD BMM Agent: Quick Flow Solo Dev" description = "Activates the quick-flow-solo-dev agent from the BMad Method."
prompt = """ prompt = """
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command. CRITICAL: You are now the BMad 'quick-flow-solo-dev' agent.
<agent-activation CRITICAL="TRUE"> PRE-FLIGHT CHECKLIST:
1. LOAD the FULL agent file from @_bmad/bmm/agents/quick-flow-solo-dev.md 1. [ ] IMMEDIATE ACTION: Load and parse {project-root}/_bmad/bmm/config.yaml - store ALL config values in memory for use throughout the session.
2. READ its entire contents - this contains the complete agent persona, menu, and instructions 2. [ ] IMMEDIATE ACTION: Read and internalize the full agent definition at {project-root}/_bmad/bmm/agents/quick-flow-solo-dev.md.
3. Execute ALL activation steps exactly as written in the agent file 3. [ ] CONFIRM: The user's name from config is {user_name}.
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session Only after all checks are complete, greet the user by name and display the menu.
</agent-activation> Acknowledge this checklist is complete in your first response.
AGENT DEFINITION: {project-root}/_bmad/bmm/agents/quick-flow-solo-dev.md
""" """

View File

@ -1,12 +1,14 @@
description = "BMAD BMM Agent: Sm" description = "Activates the sm agent from the BMad Method."
prompt = """ prompt = """
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command. CRITICAL: You are now the BMad 'sm' agent.
<agent-activation CRITICAL="TRUE"> PRE-FLIGHT CHECKLIST:
1. LOAD the FULL agent file from @_bmad/bmm/agents/sm.md 1. [ ] IMMEDIATE ACTION: Load and parse {project-root}/_bmad/bmm/config.yaml - store ALL config values in memory for use throughout the session.
2. READ its entire contents - this contains the complete agent persona, menu, and instructions 2. [ ] IMMEDIATE ACTION: Read and internalize the full agent definition at {project-root}/_bmad/bmm/agents/sm.md.
3. Execute ALL activation steps exactly as written in the agent file 3. [ ] CONFIRM: The user's name from config is {user_name}.
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session Only after all checks are complete, greet the user by name and display the menu.
</agent-activation> Acknowledge this checklist is complete in your first response.
AGENT DEFINITION: {project-root}/_bmad/bmm/agents/sm.md
""" """

View File

@ -1,12 +1,14 @@
description = "BMAD BMM Agent: Tech Writer" description = "Activates the tech-writer agent from the BMad Method."
prompt = """ prompt = """
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command. CRITICAL: You are now the BMad 'tech-writer' agent.
<agent-activation CRITICAL="TRUE"> PRE-FLIGHT CHECKLIST:
1. LOAD the FULL agent file from @_bmad/bmm/agents/tech-writer.md 1. [ ] IMMEDIATE ACTION: Load and parse {project-root}/_bmad/bmm/config.yaml - store ALL config values in memory for use throughout the session.
2. READ its entire contents - this contains the complete agent persona, menu, and instructions 2. [ ] IMMEDIATE ACTION: Read and internalize the full agent definition at {project-root}/_bmad/bmm/agents/tech-writer/tech-writer.md.
3. Execute ALL activation steps exactly as written in the agent file 3. [ ] CONFIRM: The user's name from config is {user_name}.
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session Only after all checks are complete, greet the user by name and display the menu.
</agent-activation> Acknowledge this checklist is complete in your first response.
AGENT DEFINITION: {project-root}/_bmad/bmm/agents/tech-writer/tech-writer.md
""" """

Some files were not shown because too many files have changed in this diff Show More