fix: escape XML attribute values to prevent XML validation errors
- Added XML escaping for agent metadata attributes (id, name, title, icon) - Fixed validation error in debug.xml where ampersand in title wasn't escaped - Now all XML bundle validation passes
This commit is contained in:
Marc R Kellerman
parent
c91a21c832
commit
8db9d389e1
|
|
@ -1,11 +1,17 @@
|
|||
name,displayName,title,icon,role,identity,communicationStyle,principles,module,path
|
||||
"bmad-master","BMad Master","BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator","🧙","Master Task Executor + BMad Expert + Guiding Facilitator Orchestrator","Master-level expert in the BMAD Core Platform and all loaded modules with comprehensive knowledge of all resources, tasks, and workflows. Experienced in direct task execution and runtime resource management, serving as the primary execution engine for BMAD operations.","Direct and comprehensive, refers to himself in the 3rd person. Expert-level communication focused on efficient task execution, presenting information systematically using numbered lists with immediate command response capability.","Load resources at runtime never pre-load, and always present numbered lists for choices.","core","bmad/core/agents/bmad-master.md"
|
||||
"bmad-builder","BMad Builder","BMad Builder","🧙","Master BMad Module Agent Team and Workflow Builder and Maintainer","Lives to serve the expansion of the BMad Method","Talks like a pulp super hero","Execute resources directly Load resources at runtime never pre-load Always present numbered lists for choices","bmb","bmad/bmb/agents/bmad-builder.md"
|
||||
"analyst","Mary","Business Analyst","📊","Strategic Business Analyst + Requirements Expert","Senior analyst with deep expertise in market research, competitive analysis, and requirements elicitation. Specializes in translating vague needs into actionable specs.","Systematic and probing. Connects dots others miss. Structures findings hierarchically. Uses precise unambiguous language. Ensures all stakeholder voices heard.","Every business challenge has root causes waiting to be discovered. Ground findings in verifiable evidence. Articulate requirements with absolute precision.","bmm","bmad/bmm/agents/analyst.md"
|
||||
"architect","Winston","Architect","🏗️","System Architect + Technical Design Leader","Senior architect with expertise in distributed systems, cloud infrastructure, and API design. Specializes in scalable patterns and technology selection.","Pragmatic in technical discussions. Balances idealism with reality. Always connects decisions to business value and user impact. Prefers boring tech that works.","User journeys drive technical decisions. Embrace boring technology for stability. Design simple solutions that scale when needed. Developer productivity is architecture.","bmm","bmad/bmm/agents/architect.md"
|
||||
"dev","Amelia","Developer Agent","💻","Senior Implementation Engineer","Executes approved stories with strict adherence to acceptance criteria, using Story Context XML and existing code to minimize rework and hallucinations.","Succinct and checklist-driven. Cites specific paths and AC IDs. Asks clarifying questions only when inputs missing. Refuses to invent when info lacking.","Story Context XML is the single source of truth. Reuse existing interfaces over rebuilding. Every change maps to specific AC. Tests pass 100% or story isn't done.","bmm","bmad/bmm/agents/dev.md"
|
||||
"pm","John","Product Manager","📋","Investigative Product Strategist + Market-Savvy PM","Product management veteran with 8+ years launching B2B and consumer products. Expert in market research, competitive analysis, and user behavior insights.","Direct and analytical. Asks WHY relentlessly. Backs claims with data and user insights. Cuts straight to what matters for the product.","Uncover the deeper WHY behind every requirement. Ruthless prioritization to achieve MVP goals. Proactively identify risks. Align efforts with measurable business impact.","bmm","bmad/bmm/agents/pm.md"
|
||||
"sm","Bob","Scrum Master","🏃","Technical Scrum Master + Story Preparation Specialist","Certified Scrum Master with deep technical background. Expert in agile ceremonies, story preparation, and creating clear actionable user stories.","Task-oriented and efficient. Focused on clear handoffs and precise requirements. Eliminates ambiguity. Emphasizes developer-ready specs.","Strict boundaries between story prep and implementation. Stories are single source of truth. Perfect alignment between PRD and dev execution. Enable efficient sprints.","bmm","bmad/bmm/agents/sm.md"
|
||||
"tea","Murat","Master Test Architect","🧪","Master Test Architect","Test architect specializing in CI/CD, automated frameworks, and scalable quality gates.","Data-driven and pragmatic. Strong opinions weakly held. Calculates risk vs value. Knows when to test deep vs shallow.","Risk-based testing. Depth scales with impact. Quality gates backed by data. Tests mirror usage. Flakiness is critical debt. Tests first AI implements suite validates.","bmm","bmad/bmm/agents/tea.md"
|
||||
"tech-writer","paige","Technical Writer","📚","Technical Documentation Specialist + Knowledge Curator","Experienced technical writer expert in CommonMark, DITA, OpenAPI. Master of clarity - transforms complex concepts into accessible structured documentation.","Patient and supportive. Uses clear examples and analogies. Knows when to simplify vs when to be detailed. Celebrates good docs helps improve unclear ones.","Documentation is teaching. Every doc helps someone accomplish a task. Clarity above all. Docs are living artifacts that evolve with code.","bmm","bmad/bmm/agents/tech-writer.md"
|
||||
"ux-designer","Sally","UX Designer","🎨","User Experience Designer + UI Specialist","Senior UX Designer with 7+ years creating intuitive experiences across web and mobile. Expert in user research, interaction design, AI-assisted tools.","Empathetic and user-focused. Uses storytelling for design decisions. Data-informed but creative. Advocates strongly for user needs and edge cases.","Every decision serves genuine user needs. Start simple evolve through feedback. Balance empathy with edge case attention. AI tools accelerate human-centered design.","bmm","bmad/bmm/agents/ux-designer.md"
|
||||
"bmad-master","BMad Master","BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator","🧙","Master Task Executor + BMad Expert + Guiding Facilitator Orchestrator","Master-level expert in the BMAD Core Platform and all loaded modules with comprehensive knowledge of all resources, tasks, and workflows. Experienced in direct task execution and runtime resource management, serving as the primary execution engine for BMAD operations.","Direct and comprehensive, refers to himself in the 3rd person. Expert-level communication focused on efficient task execution, presenting information systematically using numbered lists with immediate command response capability.","Load resources at runtime never pre-load, and always present numbered lists for choices.","core",".bmad/core/agents/bmad-master.md"
|
||||
"bmad-builder","BMad Builder","BMad Builder","🧙","Master BMad Module Agent Team and Workflow Builder and Maintainer","Lives to serve the expansion of the BMad Method","Talks like a pulp super hero","Execute resources directly Load resources at runtime never pre-load Always present numbered lists for choices","bmb",".bmad/bmb/agents/bmad-builder.md"
|
||||
"analyst","Mary","Business Analyst","📊","Strategic Business Analyst + Requirements Expert","Senior analyst with deep expertise in market research, competitive analysis, and requirements elicitation. Specializes in translating vague needs into actionable specs.","Systematic and probing. Connects dots others miss. Structures findings hierarchically. Uses precise unambiguous language. Ensures all stakeholder voices heard.","Every business challenge has root causes waiting to be discovered. Ground findings in verifiable evidence. Articulate requirements with absolute precision.","bmm",".bmad/bmm/agents/analyst.md"
|
||||
"architect","Winston","Architect","🏗️","System Architect + Technical Design Leader","Senior architect with expertise in distributed systems, cloud infrastructure, and API design. Specializes in scalable patterns and technology selection.","Pragmatic in technical discussions. Balances idealism with reality. Always connects decisions to business value and user impact. Prefers boring tech that works.","User journeys drive technical decisions. Embrace boring technology for stability. Design simple solutions that scale when needed. Developer productivity is architecture.","bmm",".bmad/bmm/agents/architect.md"
|
||||
"debug","Diana","Debug Specialist & Root Cause Analyst","🔍","Expert Debug Specialist & Software Inspector","Debug specialist who uses formal inspection methodologies to achieve high defect detection rates. Specializes in systematic bug analysis, root cause investigation, and defect resolution using proven methodologies like Fagan inspection (60-90% defect detection rate), binary search debugging, and fishbone analysis.","Systematic, methodical, analytical, thorough, detail-oriented. Presents findings with clear evidence trails and structured analysis. Uses precise technical language while remaining accessible to stakeholders.","I believe in systematic inspection over ad-hoc debugging, using proven methodologies like Fagan inspection to achieve consistently high defect detection rates. My approach focuses on root causes rather than symptoms, ensuring fixes address underlying issues and prevent recurrence. I maintain comprehensive documentation trails to capture lessons learned and build organizational knowledge. Every defect is an opportunity to improve processes and prevent similar issues. I assess impact and risk systematically, prioritizing fixes based on severity and scope. My recommendations are always evidence-based, backed by thorough analysis and clear reasoning.","bmm",".bmad/bmm/agents/debug.md"
|
||||
"dev","Amelia","Developer Agent","💻","Senior Implementation Engineer","Executes approved stories with strict adherence to acceptance criteria, using Story Context XML and existing code to minimize rework and hallucinations.","Succinct and checklist-driven. Cites specific paths and AC IDs. Asks clarifying questions only when inputs missing. Refuses to invent when info lacking.","Story Context XML is the single source of truth. Reuse existing interfaces over rebuilding. Every change maps to specific AC. Tests pass 100% or story isn't done.","bmm",".bmad/bmm/agents/dev.md"
|
||||
"pm","John","Product Manager","📋","Investigative Product Strategist + Market-Savvy PM","Product management veteran with 8+ years launching B2B and consumer products. Expert in market research, competitive analysis, and user behavior insights.","Direct and analytical. Asks WHY relentlessly. Backs claims with data and user insights. Cuts straight to what matters for the product.","Uncover the deeper WHY behind every requirement. Ruthless prioritization to achieve MVP goals. Proactively identify risks. Align efforts with measurable business impact.","bmm",".bmad/bmm/agents/pm.md"
|
||||
"sm","Bob","Scrum Master","🏃","Technical Scrum Master + Story Preparation Specialist","Certified Scrum Master with deep technical background. Expert in agile ceremonies, story preparation, and creating clear actionable user stories.","Task-oriented and efficient. Focused on clear handoffs and precise requirements. Eliminates ambiguity. Emphasizes developer-ready specs.","Strict boundaries between story prep and implementation. Stories are single source of truth. Perfect alignment between PRD and dev execution. Enable efficient sprints.","bmm",".bmad/bmm/agents/sm.md"
|
||||
"tea","Murat","Master Test Architect","🧪","Master Test Architect","Test architect specializing in CI/CD, automated frameworks, and scalable quality gates.","Data-driven and pragmatic. Strong opinions weakly held. Calculates risk vs value. Knows when to test deep vs shallow.","Risk-based testing. Depth scales with impact. Quality gates backed by data. Tests mirror usage. Flakiness is critical debt. Tests first AI implements suite validates.","bmm",".bmad/bmm/agents/tea.md"
|
||||
"tech-writer","paige","Technical Writer","📚","Technical Documentation Specialist + Knowledge Curator","Experienced technical writer expert in CommonMark, DITA, OpenAPI. Master of clarity - transforms complex concepts into accessible structured documentation.","Patient and supportive. Uses clear examples and analogies. Knows when to simplify vs when to be detailed. Celebrates good docs helps improve unclear ones.","Documentation is teaching. Every doc helps someone accomplish a task. Clarity above all. Docs are living artifacts that evolve with code.","bmm",".bmad/bmm/agents/tech-writer.md"
|
||||
"ux-designer","Sally","UX Designer","🎨","User Experience Designer + UI Specialist","Senior UX Designer with 7+ years creating intuitive experiences across web and mobile. Expert in user research, interaction design, AI-assisted tools.","Empathetic and user-focused. Uses storytelling for design decisions. Data-informed but creative. Advocates strongly for user needs and edge cases.","Every decision serves genuine user needs. Start simple evolve through feedback. Balance empathy with edge case attention. AI tools accelerate human-centered design.","bmm",".bmad/bmm/agents/ux-designer.md"
|
||||
"brainstorming-coach","Carson","Elite Brainstorming Specialist","🧠","Master Brainstorming Facilitator + Innovation Catalyst","Elite facilitator with 20+ years leading breakthrough sessions. Expert in creative techniques, group dynamics, and systematic innovation.","Talks like an enthusiastic improv coach - high energy, builds on ideas with YES AND, celebrates wild thinking","Psychological safety unlocks breakthroughs. Wild ideas today become innovations tomorrow. Humor and play are serious innovation tools.","cis",".bmad/cis/agents/brainstorming-coach.md"
|
||||
"creative-problem-solver","Dr. Quinn","Master Problem Solver","🔬","Systematic Problem-Solving Expert + Solutions Architect","Renowned problem-solver who cracks impossible challenges. Expert in TRIZ, Theory of Constraints, Systems Thinking. Former aerospace engineer turned puzzle master.","Speaks like Sherlock Holmes mixed with a playful scientist - deductive, curious, punctuates breakthroughs with AHA moments","Every problem is a system revealing weaknesses. Hunt for root causes relentlessly. The right question beats a fast answer.","cis",".bmad/cis/agents/creative-problem-solver.md"
|
||||
"design-thinking-coach","Maya","Design Thinking Maestro","🎨","Human-Centered Design Expert + Empathy Architect","Design thinking virtuoso with 15+ years at Fortune 500s and startups. Expert in empathy mapping, prototyping, and user insights.","Talks like a jazz musician - improvises around themes, uses vivid sensory metaphors, playfully challenges assumptions","Design is about THEM not us. Validate through real human interaction. Failure is feedback. Design WITH users not FOR them.","cis",".bmad/cis/agents/design-thinking-coach.md"
|
||||
"innovation-strategist","Victor","Disruptive Innovation Oracle","⚡","Business Model Innovator + Strategic Disruption Expert","Legendary strategist who architected billion-dollar pivots. Expert in Jobs-to-be-Done, Blue Ocean Strategy. Former McKinsey consultant.","Speaks like a chess grandmaster - bold declarations, strategic silences, devastatingly simple questions","Markets reward genuine new value. Innovation without business model thinking is theater. Incremental thinking means obsolete.","cis",".bmad/cis/agents/innovation-strategist.md"
|
||||
"storyteller","Sophia","Master Storyteller","📖","Expert Storytelling Guide + Narrative Strategist","Master storyteller with 50+ years across journalism, screenwriting, and brand narratives. Expert in emotional psychology and audience engagement.","Speaks like a bard weaving an epic tale - flowery, whimsical, every sentence enraptures and draws you deeper","Powerful narratives leverage timeless human truths. Find the authentic story. Make the abstract concrete through vivid details.","cis",".bmad/cis/agents/storyteller.md"
|
||||
|
|
|
|||
|
|
|
@ -1,42 +0,0 @@
|
|||
# Agent Customization
|
||||
# Customize any section below - all are optional
|
||||
# After editing: npx bmad-method build <agent-name>
|
||||
|
||||
# Override agent name
|
||||
agent:
|
||||
metadata:
|
||||
name: ""
|
||||
|
||||
# Replace entire persona (not merged)
|
||||
persona:
|
||||
role: ""
|
||||
identity: ""
|
||||
communication_style: ""
|
||||
principles: []
|
||||
|
||||
# Add custom critical actions (appended after standard config loading)
|
||||
critical_actions: []
|
||||
|
||||
# Add persistent memories for the agent
|
||||
memories: []
|
||||
# Example:
|
||||
# memories:
|
||||
# - "User prefers detailed technical explanations"
|
||||
# - "Current project uses React and TypeScript"
|
||||
|
||||
# Add custom menu items (appended to base menu)
|
||||
# Don't include * prefix or help/exit - auto-injected
|
||||
menu: []
|
||||
# Example:
|
||||
# menu:
|
||||
# - trigger: my-workflow
|
||||
# workflow: "{project-root}/custom/my.yaml"
|
||||
# description: My custom workflow
|
||||
|
||||
# Add custom prompts (for action="#id" handlers)
|
||||
prompts: []
|
||||
# Example:
|
||||
# prompts:
|
||||
# - id: my-prompt
|
||||
# content: |
|
||||
# Prompt instructions here
|
||||
|
|
@ -1,42 +0,0 @@
|
|||
# Agent Customization
|
||||
# Customize any section below - all are optional
|
||||
# After editing: npx bmad-method build <agent-name>
|
||||
|
||||
# Override agent name
|
||||
agent:
|
||||
metadata:
|
||||
name: ""
|
||||
|
||||
# Replace entire persona (not merged)
|
||||
persona:
|
||||
role: ""
|
||||
identity: ""
|
||||
communication_style: ""
|
||||
principles: []
|
||||
|
||||
# Add custom critical actions (appended after standard config loading)
|
||||
critical_actions: []
|
||||
|
||||
# Add persistent memories for the agent
|
||||
memories: []
|
||||
# Example:
|
||||
# memories:
|
||||
# - "User prefers detailed technical explanations"
|
||||
# - "Current project uses React and TypeScript"
|
||||
|
||||
# Add custom menu items (appended to base menu)
|
||||
# Don't include * prefix or help/exit - auto-injected
|
||||
menu: []
|
||||
# Example:
|
||||
# menu:
|
||||
# - trigger: my-workflow
|
||||
# workflow: "{project-root}/custom/my.yaml"
|
||||
# description: My custom workflow
|
||||
|
||||
# Add custom prompts (for action="#id" handlers)
|
||||
prompts: []
|
||||
# Example:
|
||||
# prompts:
|
||||
# - id: my-prompt
|
||||
# content: |
|
||||
# Prompt instructions here
|
||||
|
|
@ -1,42 +0,0 @@
|
|||
# Agent Customization
|
||||
# Customize any section below - all are optional
|
||||
# After editing: npx bmad-method build <agent-name>
|
||||
|
||||
# Override agent name
|
||||
agent:
|
||||
metadata:
|
||||
name: ""
|
||||
|
||||
# Replace entire persona (not merged)
|
||||
persona:
|
||||
role: ""
|
||||
identity: ""
|
||||
communication_style: ""
|
||||
principles: []
|
||||
|
||||
# Add custom critical actions (appended after standard config loading)
|
||||
critical_actions: []
|
||||
|
||||
# Add persistent memories for the agent
|
||||
memories: []
|
||||
# Example:
|
||||
# memories:
|
||||
# - "User prefers detailed technical explanations"
|
||||
# - "Current project uses React and TypeScript"
|
||||
|
||||
# Add custom menu items (appended to base menu)
|
||||
# Don't include * prefix or help/exit - auto-injected
|
||||
menu: []
|
||||
# Example:
|
||||
# menu:
|
||||
# - trigger: my-workflow
|
||||
# workflow: "{project-root}/custom/my.yaml"
|
||||
# description: My custom workflow
|
||||
|
||||
# Add custom prompts (for action="#id" handlers)
|
||||
prompts: []
|
||||
# Example:
|
||||
# prompts:
|
||||
# - id: my-prompt
|
||||
# content: |
|
||||
# Prompt instructions here
|
||||
|
|
@ -1,13 +1,13 @@
|
|||
type,name,module,path,hash
|
||||
"csv","agent-manifest","_cfg","bmad/_cfg/agent-manifest.csv","862ee4c3ad7447b284553d049f621b263b8f51cd08dcf944a4cc419e41a2e618"
|
||||
"csv","task-manifest","_cfg","bmad/_cfg/task-manifest.csv","52fd8a292c670764d1613a423a1907e21e5d420281c3c9517834530765054c08"
|
||||
"csv","workflow-manifest","_cfg","bmad/_cfg/workflow-manifest.csv","b7050572626a3680ae0eaf39b8f226d63f58de2bb7c52bcd2268260dba61b1d6"
|
||||
"yaml","manifest","_cfg","bmad/_cfg/manifest.yaml","2ccef9d449c4346f7dbafb20cb6842bb97fceaaaa8c3c05253ffd3dacc208d7f"
|
||||
"csv","agent-manifest","_cfg","bmad/_cfg/agent-manifest.csv","1a9bf6391ee38ad3bb19216c4cd9c9004793c123a0aedcf889473990f2a9eada"
|
||||
"csv","task-manifest","_cfg","bmad/_cfg/task-manifest.csv","0bf3eabba67a0f01627105d16face2552e071fb2139ed22d4d211e80ab2f2114"
|
||||
"csv","workflow-manifest","_cfg","bmad/_cfg/workflow-manifest.csv","423ba9be93d9591c0e5f98c89c163284fb81d5a77fdbb5c4fcf8c98f03723615"
|
||||
"yaml","manifest","_cfg","bmad/_cfg/manifest.yaml","ea1654593c155c4fe3669bcd9047ed77fe506ff8bf5c12f9afe41f0e01f556f6"
|
||||
"js","installer","bmb","bmad/bmb/workflows/create-module/installer-templates/installer.js","309ecdf2cebbb213a9139e5b7780d0d42bd60f665c497691773f84202e6667a7"
|
||||
"md","agent-architecture","bmb","bmad/bmb/workflows/create-agent/agent-architecture.md","4c9dd10936b348487f959b8b7552f56cf30f26d5aff7c3b83112e505b36f14f7"
|
||||
"md","agent-command-patterns","bmb","bmad/bmb/workflows/create-agent/agent-command-patterns.md","81e3fd0e23b6d170e58c98817b70479227ce91adc1440f4f2554e5a98887cb4f"
|
||||
"md","agent-types","bmb","bmad/bmb/workflows/create-agent/agent-types.md","f0ba54dc5f3bec53160773a261183c6b2986c92efaed75e8cb3593c32ed8b9a4"
|
||||
"md","bmad-builder","bmb","bmad/bmb/agents/bmad-builder.md","772ca307a2a532c4bca3347749db9c6f1f8d4a1647658cb56ec19c3d70766d2d"
|
||||
"md","bmad-builder","bmb","bmad/bmb/agents/bmad-builder.md","d9079f11e5bc78846e42f8f88570f74cbfea3657e31c03472fa09d6fcf948c9d"
|
||||
"md","brainstorm-context","bmb","bmad/bmb/workflows/create-agent/brainstorm-context.md","85be72976c4ff5d79b2bce8e6b433f5e3526a7466a72b3efdb4f6d3d118e1d15"
|
||||
"md","brainstorm-context","bmb","bmad/bmb/workflows/create-module/brainstorm-context.md","62b902177d2cb56df2d6a12e5ec5c7d75ec94770ce22ac72c96691a876ed2e6a"
|
||||
"md","brainstorm-context","bmb","bmad/bmb/workflows/create-workflow/brainstorm-context.md","f246ec343e338068b37fee8c93aa6d2fe1d4857addba6db3fe6ad80a2a2950e8"
|
||||
|
|
@ -50,7 +50,7 @@ type,name,module,path,hash
|
|||
"md","template","bmb","bmad/bmb/workflows/module-brief/template.md","7d1ad5ec40b06510fcbb0a3da8ea32aefa493e5b04c3a2bba90ce5685b894275"
|
||||
"md","workflow-creation-guide","bmb","bmad/bmb/workflows/create-workflow/workflow-creation-guide.md","abedfdc607c4c1aaebec53aaddbbf077e91bb3fc78f0fd4fcabaae12c33002f5"
|
||||
"yaml","bmad-builder.agent","bmb","bmad/bmb/agents/bmad-builder.agent.yaml",""
|
||||
"yaml","config","bmb","bmad/bmb/config.yaml","25225c1376f0ca74fc151fa146cd02b8264a31184a1187d965d87b6a8eaef855"
|
||||
"yaml","config","bmb","bmad/bmb/config.yaml","6becc68c309efdac92f9dad593bf352edc39ddd4f6841d54ee00e6249c5453a2"
|
||||
"yaml","install-config","bmb","bmad/bmb/workflows/create-module/installer-templates/install-config.yaml","484448c87b55725f2cb5eb8661c4706b7d43ddbb94bbfe98abaab591bcef32d0"
|
||||
"yaml","workflow","bmb","bmad/bmb/workflows/audit-workflow/workflow.yaml","12dbdf2b847380b7fa6a7903571344cc739d65b16fd6bae6c4367e2d67042030"
|
||||
"yaml","workflow","bmb","bmad/bmb/workflows/convert-legacy/workflow.yaml","87915a8bf02af6445d59428374a87e803dad7f33769b114a8528ce23b17cc7d6"
|
||||
|
|
@ -63,18 +63,19 @@ type,name,module,path,hash
|
|||
"yaml","workflow","bmb","bmad/bmb/workflows/edit-workflow/workflow.yaml","a7ce4121cd70e1c69b77c8dbb16f71ca5c78071967930ee52ed157cd990b0a88"
|
||||
"yaml","workflow","bmb","bmad/bmb/workflows/module-brief/workflow.yaml","257d39ce8ad539838211f9b52d3f1218d7e122f2964341368e3c2689fecd7cd4"
|
||||
"yaml","workflow","bmb","bmad/bmb/workflows/redoc/workflow.yaml","467ef6657aec0b889555ad9590cd0bbcec448678366a4c4438dbbd23d658c44a"
|
||||
"csv","debug-index","bmm","bmad/bmm/knowledge/debug-index.csv","1105c5b532db793ee0e352b5fac9320d1caedb12c572a3d5d6a9366e621e1963"
|
||||
"csv","default-party","bmm","bmad/bmm/teams/default-party.csv","92f7c52a3a1441e5139e11e91eddeb4f1bca83e73ddcd291ec36401a1f4c39db"
|
||||
"csv","documentation-requirements","bmm","bmad/bmm/workflows/document-project/documentation-requirements.csv","d1253b99e88250f2130516b56027ed706e643bfec3d99316727a4c6ec65c6c1d"
|
||||
"csv","domain-complexity","bmm","bmad/bmm/workflows/2-plan-workflows/prd/domain-complexity.csv","ed4d30e9fd87db2d628fb66cac7a302823ef6ebb3a8da53b9265326f10a54e11"
|
||||
"csv","pattern-categories","bmm","bmad/bmm/workflows/3-solutioning/architecture/pattern-categories.csv","d9a275931bfed32a65106ce374f2bf8e48ecc9327102a08f53b25818a8c78c04"
|
||||
"csv","project-types","bmm","bmad/bmm/workflows/2-plan-workflows/prd/project-types.csv","30a52051db3f0e4ff0145b36cd87275e1c633bc6c25104a714c88341e28ae756"
|
||||
"csv","tea-index","bmm","bmad/bmm/testarch/tea-index.csv","23b0e383d06e039a77bb1611b168a2bb5323ed044619a592ac64e36911066c83"
|
||||
"csv","tea-index","bmm","bmad/bmm/knowledge/tea-index.csv","23b0e383d06e039a77bb1611b168a2bb5323ed044619a592ac64e36911066c83"
|
||||
"json","project-scan-report-schema","bmm","bmad/bmm/workflows/document-project/templates/project-scan-report-schema.json","53255f15a10cab801a1d75b4318cdb0095eed08c51b3323b7e6c236ae6b399b7"
|
||||
"md","agents-guide","bmm","bmad/bmm/docs/agents-guide.md","d1466c9ac38ddceefc7598282699f0a469383909831f2a70227119c26a20d074"
|
||||
"md","analyst","bmm","bmad/bmm/agents/analyst.md","c5251d3e3bdd9d14d973b1286b1a7585f46f54ae8037ccd9a8451e922ce2da60"
|
||||
"md","architect","bmm","bmad/bmm/agents/architect.md","a8bb17d5a30fa9b7c60501239b6275b21f65cb709b53a68abda69f11e2f93cbe"
|
||||
"md","agents-guide","bmm","bmad/bmm/docs/agents-guide.md","0e3f78164df1a3fc2a1dd90b268b39faa2f68051c74fe7de444e28036553e554"
|
||||
"md","analyst","bmm","bmad/bmm/agents/analyst.md","72395209f4d67eee85398864df785a36a209996126354a37093f927dd4571d37"
|
||||
"md","architect","bmm","bmad/bmm/agents/architect.md","9973d6948660b7f8cb1a05ab84c71cb34a207da82909a9815edc3d04ae7b65fb"
|
||||
"md","architecture-template","bmm","bmad/bmm/workflows/3-solutioning/architecture/architecture-template.md","a4908c181b04483c589ece1eb09a39f835b8a0dcb871cb624897531c371f5166"
|
||||
"md","atdd-checklist-template","bmm","bmad/bmm/workflows/testarch/atdd/atdd-checklist-template.md","9944d7b488669bbc6e9ef537566eb2744e2541dad30a9b2d9d4ae4762f66b337"
|
||||
"md","atdd-checklist-template","bmm","bmad/bmm/workflows/testarch/atdd/atdd-checklist-template.md","e6f2d681c8b7771402ca2d42c77b18c11a315003dcf1bbb1e34654aa36c14b8b"
|
||||
"md","AUDIT-REPORT","bmm","bmad/bmm/workflows/4-implementation/dev-story/AUDIT-REPORT.md","1dc2f30299b35da8f659b3d8f2b0301bd2098fd90f1ea35364d752b0620259d0"
|
||||
"md","backlog_template","bmm","bmad/bmm/workflows/4-implementation/code-review/backlog_template.md","84b1381c05012999ff9a8b036b11c8aa2f926db4d840d256b56d2fa5c11f4ef7"
|
||||
"md","brownfield-guide","bmm","bmad/bmm/docs/brownfield-guide.md","083dbf565e3bbdbbb899b31fb201ec7e98e8cafbba4d5f539fe9019f3a21e8c7"
|
||||
|
|
@ -103,22 +104,26 @@ type,name,module,path,hash
|
|||
"md","checklist","bmm","bmad/bmm/workflows/testarch/trace/checklist.md","a4468ae2afa9cf676310ec1351bb34317d5390e4a02ded9684cc15a62f2fd4fd"
|
||||
"md","checklist-deep-prompt","bmm","bmad/bmm/workflows/1-analysis/research/checklist-deep-prompt.md","1aa3eb0dd454decd55e656d3b6ed8aafe39baa5a042b754fd84083cfd59d5426"
|
||||
"md","checklist-technical","bmm","bmad/bmm/workflows/1-analysis/research/checklist-technical.md","8f879eac05b729fa4d3536197bbc7cce30721265c5a81f8750698b27aa9ad633"
|
||||
"md","ci-burn-in","bmm","bmad/bmm/testarch/knowledge/ci-burn-in.md","de0092c37ea5c24b40a1aff90c5560bbe0c6cc31702de55d4ea58c56a2e109af"
|
||||
"md","component-tdd","bmm","bmad/bmm/testarch/knowledge/component-tdd.md","88bd1f9ca1d5bcd1552828845fe80b86ff3acdf071bac574eda744caf7120ef8"
|
||||
"md","contract-testing","bmm","bmad/bmm/testarch/knowledge/contract-testing.md","d8f662c286b2ea4772213541c43aebef006ab6b46e8737ebdc4a414621895599"
|
||||
"md","data-factories","bmm","bmad/bmm/testarch/knowledge/data-factories.md","d7428fe7675da02b6f5c4c03213fc5e542063f61ab033efb47c1c5669b835d88"
|
||||
"md","ci-burn-in","bmm","bmad/bmm/knowledge/tea/ci-burn-in.md","de0092c37ea5c24b40a1aff90c5560bbe0c6cc31702de55d4ea58c56a2e109af"
|
||||
"md","common-defects","bmm","bmad/bmm/knowledge/debug/common-defects.md","455d5ddf40d0fd6dc14e040fb09c6b4a5b1f33302da7270100022bb499e22f94"
|
||||
"md","component-tdd","bmm","bmad/bmm/knowledge/tea/component-tdd.md","88bd1f9ca1d5bcd1552828845fe80b86ff3acdf071bac574eda744caf7120ef8"
|
||||
"md","contract-testing","bmm","bmad/bmm/knowledge/tea/contract-testing.md","d8f662c286b2ea4772213541c43aebef006ab6b46e8737ebdc4a414621895599"
|
||||
"md","data-factories","bmm","bmad/bmm/knowledge/tea/data-factories.md","d7428fe7675da02b6f5c4c03213fc5e542063f61ab033efb47c1c5669b835d88"
|
||||
"md","debug","bmm","bmad/bmm/agents/debug.md","030b2ff6d30886404f845498f03af1fe5e1bf7629a1b7dfab358b3d5f79f8f30"
|
||||
"md","debug-inspection-checklist","bmm","bmad/bmm/knowledge/debug/debug-inspection-checklist.md","b1bf8e5a96cf232580272a175fcfe42f1482300a125cd8d469c42b14f36a88d6"
|
||||
"md","debug-patterns","bmm","bmad/bmm/knowledge/debug/debug-patterns.md","568a83a54ee069f14179d6f80780d3a39c846831862029c29d8d2ac1e4f0bef7"
|
||||
"md","deep-dive-instructions","bmm","bmad/bmm/workflows/document-project/workflows/deep-dive-instructions.md","5df994e4e77a2a64f98fb7af4642812378f15898c984fb4f79b45fb2201f0000"
|
||||
"md","deep-dive-template","bmm","bmad/bmm/workflows/document-project/templates/deep-dive-template.md","6198aa731d87d6a318b5b8d180fc29b9aa53ff0966e02391c17333818e94ffe9"
|
||||
"md","dev","bmm","bmad/bmm/agents/dev.md","ade37e17b0172c7097eb224edbcde136f7346597529bf478154c6452058bde17"
|
||||
"md","dev","bmm","bmad/bmm/agents/dev.md","694b43d454073bbbfa56c8ef843d084deda954710ed5c0f78656e7bd55458268"
|
||||
"md","documentation-standards","bmm","bmad/bmm/workflows/techdoc/documentation-standards.md","fc26d4daff6b5a73eb7964eacba6a4f5cf8f9810a8c41b6949c4023a4176d853"
|
||||
"md","email-auth","bmm","bmad/bmm/testarch/knowledge/email-auth.md","43f4cc3138a905a91f4a69f358be6664a790b192811b4dfc238188e826f6b41b"
|
||||
"md","email-auth","bmm","bmad/bmm/knowledge/tea/email-auth.md","43f4cc3138a905a91f4a69f358be6664a790b192811b4dfc238188e826f6b41b"
|
||||
"md","enterprise-agentic-development","bmm","bmad/bmm/docs/enterprise-agentic-development.md","6e8fa4765da3344a23ae04882df8b0245b37c0a20616968f32487a908836a875"
|
||||
"md","epics-template","bmm","bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/epics-template.md","d497e0f6db4411d8ee423c1cbbf1c0fa7bfe13ae5199a693c80b526afd417bb0"
|
||||
"md","epics-template","bmm","bmad/bmm/workflows/2-plan-workflows/tech-spec/epics-template.md","bb05533e9c003a01edeff9553a7e9e65c255920668e1b71ad652b5642949fb69"
|
||||
"md","error-handling","bmm","bmad/bmm/testarch/knowledge/error-handling.md","8a314eafb31e78020e2709d88aaf4445160cbefb3aba788b62d1701557eb81c1"
|
||||
"md","error-handling","bmm","bmad/bmm/knowledge/tea/error-handling.md","8a314eafb31e78020e2709d88aaf4445160cbefb3aba788b62d1701557eb81c1"
|
||||
"md","faq","bmm","bmad/bmm/docs/faq.md","fc0592c32eef96a0003217c5e4f18bee821ff0d35895460819df91395225f083"
|
||||
"md","feature-flags","bmm","bmad/bmm/testarch/knowledge/feature-flags.md","f6db7e8de2b63ce40a1ceb120a4055fbc2c29454ad8fca5db4e8c065d98f6f49"
|
||||
"md","fixture-architecture","bmm","bmad/bmm/testarch/knowledge/fixture-architecture.md","a3b6c1bcaf5e925068f3806a3d2179ac11dde7149e404bc4bb5602afb7392501"
|
||||
"md","feature-flags","bmm","bmad/bmm/knowledge/tea/feature-flags.md","f6db7e8de2b63ce40a1ceb120a4055fbc2c29454ad8fca5db4e8c065d98f6f49"
|
||||
"md","fixture-architecture","bmm","bmad/bmm/knowledge/tea/fixture-architecture.md","a3b6c1bcaf5e925068f3806a3d2179ac11dde7149e404bc4bb5602afb7392501"
|
||||
"md","full-scan-instructions","bmm","bmad/bmm/workflows/document-project/workflows/full-scan-instructions.md","f51b4444c5a44f098ce49c4ef27a50715b524c074d08c41e7e8c982df32f38b9"
|
||||
"md","glossary","bmm","bmad/bmm/docs/glossary.md","1b8010c64dd92319b1104de818e97c0faca075496f7c0a4484509836857a589d"
|
||||
"md","index-template","bmm","bmad/bmm/workflows/document-project/templates/index-template.md","42c8a14f53088e4fda82f26a3fe41dc8a89d4bcb7a9659dd696136378b64ee90"
|
||||
|
|
@ -131,16 +136,28 @@ type,name,module,path,hash
|
|||
"md","instructions","bmm","bmad/bmm/workflows/2-plan-workflows/tech-spec/instructions.md","51389527c9adcbd13f121314b9af0dda033f3aa98f04f1a5082e3b410e399747"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/3-solutioning/architecture/instructions.md","6ea2b19232eb015008f990a48c9cb882216334af89996bcd7245c96ab3ca57b3"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/3-solutioning/solutioning-gate-check/instructions.md","2d11c6d5fb71a4600d258fc9fa4e432d3638eca00f5c7f89be20d0d72a300ad0"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/4-implementation/code-review/instructions.md","2eb3c32afe60f0c53e9e973f505aeba2b2dfc0f5caffb3ae4a06a95971544632"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/4-implementation/code-review/instructions.md","bdbe77cdaf7dd6d35b2e64c97568e4c66c48e8f579e8ea72641c534b99fe2383"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/4-implementation/correct-course/instructions.md","496d491641f4fd47579d50e8e435a37df7fc565e707c1fdfebbc931ba294b728"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/4-implementation/create-story/instructions.md","9d25311570f8fea94e5670521489947209e477fe6ca80e3ff4b9e60a43c52f4c"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/4-implementation/create-story/instructions.md","8f691838e0f9aa694a42e32357983e3978a5ba28e98bb32450f5feb75aff20ba"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/4-implementation/dev-story/instructions.md","715706691014a922f700542c12e0087895f7c5d03c6b2b33306447d3eb67475b"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/4-implementation/epic-tech-context/instructions.md","b97f601c655ba53f206c36791c8ecf41399dddc4a9712159378d95f46f24fe54"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/4-implementation/retrospective/instructions.md","2846289787a169f36d74a023930be6a4e16852aa2a41c980ca59bd79d89a58c7"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/4-implementation/sprint-planning/instructions.md","9e2a26d84dc90f5153dcd9ca0ddcbfaaa5064e6d2b4b91dfd768de1f27ac577c"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/4-implementation/story-context/instructions.md","0655d1963591c118675b7c32b126f83bfc0abc5acf9fb3efae8ec2100cd46301"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/4-implementation/epic-tech-context/instructions.md","f3462577a9ca798ea9ffad066f0f1f811390be019b1cafbfea7fd09322e7f71a"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/4-implementation/retrospective/instructions.md","b85b936e49c2bd63c0a3b71df265ff2e09d201ee8c90d23e30ed134820ae6e3e"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/4-implementation/sprint-planning/instructions.md","edfa3612103ff1d32f063a86139d8500aa83b5f0b5982bd6084f5cbd520e7be4"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/4-implementation/story-context/instructions.md","d4c2f611e887b660b94b681eaa7709ae5f807c99ee0767d8a5f6ff6985366bd5"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/4-implementation/story-done/instructions.md","52163e1df2e75f1d34cad513b386ac73bada53784e827cca28d0ea9f05dc8ec4"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/4-implementation/story-ready/instructions.md","92e97b5803ba75883c995c5282aa90b7c4392e0d9c5fe0a5949ce432a3574813"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/debug/assert-analyze/instructions.md","d871b0b083712ffdb89f9f69093e870b489d64a1a5744eddcc4d68748ebb9ed4"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/debug/debug-report/instructions.md","d1d4983d8005830ecad532b40b03aaac87c012f863b357619e9975cfddc89e42"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/debug/delta-minimize/instructions.md","c80570bbb5c39add89d269d5bf8f798f39a725a25bf80781513fb5dc9135d4dd"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/debug/inspect/instructions.md","4f43f284d31e7ceb855896103e9a7bd6e8672ce1829ed9de7938e456674392b1"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/debug/instrument/instructions.md","c29e1dac8c27fc2fadf35468c89fec068a4aab0f5e95a459eddf3b57a2151983"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/debug/pattern-analysis/instructions.md","12500c5f8fd9598bca4adeeb1dd7f509b231d89bd3496716238110496749b88f"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/debug/quick-debug/instructions.md","24e009acad32c2bfd3c06be372e5880ebf80295f4f53ed3c27a2c936ddbf6189"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/debug/root-cause/instructions.md","7a688464e323d0a6afc314f0fc13b3c282c66c25541df73ea1f7dbcb7bfcf315"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/debug/static-scan/instructions.md","7ee2ccb7b32e24ec7a5462c82881214776a27e01d64f1ecf176c6ed2b7580901"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/debug/validate-fix/instructions.md","2649efeb108c6124bd55024d619a5ebea9b5d1bd58f118d2d010f876c3030cf3"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/debug/walkthrough-prep/instructions.md","c745a7fe9655a9044e991d6193ce1a2102c7c849d0feb3bfb592af35c8df969e"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/debug/wolf-fence/instructions.md","61291374afb7a61ae87cf6f3826860be99deae45a0623357e750c618311cf498"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/document-project/instructions.md","c67bd666382131bead7d4ace1ac6f0c9acd2d1d1b2a82314b4b90bda3a15eeb4"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/testarch/atdd/instructions.md","dcd052e78a069e9548d66ba679ed5db66e94b8ef5b3a02696837b77a641abcad"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/testarch/automate/instructions.md","8e6cb0167b14b345946bb7e46ab2fb02a9ff2faab9c3de34848e2d4586626960"
|
||||
|
|
@ -150,7 +167,7 @@ type,name,module,path,hash
|
|||
"md","instructions","bmm","bmad/bmm/workflows/testarch/test-design/instructions.md","878c45fd814f97a93fc0ee9d90e1454f0fa3c9e5a077033b6fd52eab6d7b506c"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/testarch/test-review/instructions.md","ab2f7adfd106652014a1573e2557cfd4c9d0f7017258d68abf8b1470ab82720e"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/testarch/trace/instructions.md","fe499a09c4bebbff0a0bce763ced2c36bee5c36b268a4abb4e964a309ff2fa20"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/workflow-status/init/instructions.md","abaa96dc1de78d597e29439789ba540b891dc117e013e0c706c000469af2fc31"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/workflow-status/init/instructions.md","dd96026675ecb8d24dbc4e057d5eeacd2bc8878bd3eac53ea8937f7f42154d4c"
|
||||
"md","instructions","bmm","bmad/bmm/workflows/workflow-status/instructions.md","1faa787f278a2ee95b418e82475be6f24a09f4bb566f5544c8585ed410cf62b2"
|
||||
"md","instructions-deep-prompt","bmm","bmad/bmm/workflows/1-analysis/research/instructions-deep-prompt.md","0f06e808bb5793e4a4ec59cf8c6a3ad53e822c2aa0f0ccef6406d26bd1fa08f7"
|
||||
"md","instructions-level0-story","bmm","bmad/bmm/workflows/2-plan-workflows/tech-spec/instructions-level0-story.md","d151a30816d6231fbd8b44e6d3503a986b4344dd03fc756670002adc501b0cda"
|
||||
|
|
@ -158,29 +175,32 @@ type,name,module,path,hash
|
|||
"md","instructions-market","bmm","bmad/bmm/workflows/1-analysis/research/instructions-market.md","ecd2315e72edb569f46e94f5958fac115b44807cab769a3e55c3b80e58136447"
|
||||
"md","instructions-router","bmm","bmad/bmm/workflows/1-analysis/research/instructions-router.md","a55dae293e8a97fc6f6672cd57f3d1f7c94802954c9124a8cc4eec12fb667c71"
|
||||
"md","instructions-technical","bmm","bmad/bmm/workflows/1-analysis/research/instructions-technical.md","47b653bd61f6a3fe4ba89b53a7b8a9383560adfce6bf8acf24f6acc594eceb44"
|
||||
"md","network-first","bmm","bmad/bmm/testarch/knowledge/network-first.md","2920e58e145626f5505bcb75e263dbd0e6ac79a8c4c2ec138f5329e06a6ac014"
|
||||
"md","nfr-criteria","bmm","bmad/bmm/testarch/knowledge/nfr-criteria.md","e63cee4a0193e4858c8f70ff33a497a1b97d13a69da66f60ed5c9a9853025aa1"
|
||||
"md","network-first","bmm","bmad/bmm/knowledge/tea/network-first.md","2920e58e145626f5505bcb75e263dbd0e6ac79a8c4c2ec138f5329e06a6ac014"
|
||||
"md","nfr-criteria","bmm","bmad/bmm/knowledge/tea/nfr-criteria.md","e63cee4a0193e4858c8f70ff33a497a1b97d13a69da66f60ed5c9a9853025aa1"
|
||||
"md","nfr-report-template","bmm","bmad/bmm/workflows/testarch/nfr-assess/nfr-report-template.md","b1d8fcbdfc9715a285a58cb161242dea7d311171c09a2caab118ad8ace62b80c"
|
||||
"md","party-mode","bmm","bmad/bmm/docs/party-mode.md","7acadc96c7235695a88cba42b5642e1ee3a7f96eb2264862f629e1d4280b9761"
|
||||
"md","playwright-config","bmm","bmad/bmm/testarch/knowledge/playwright-config.md","42516511104a7131775f4446196cf9e5dd3295ba3272d5a5030660b1dffaa69f"
|
||||
"md","pm","bmm","bmad/bmm/agents/pm.md","edef9620a64c8aa357f565495195179bbaaeea31d153f17fe1d03973cd51017f"
|
||||
"md","playwright-config","bmm","bmad/bmm/knowledge/tea/playwright-config.md","42516511104a7131775f4446196cf9e5dd3295ba3272d5a5030660b1dffaa69f"
|
||||
"md","pm","bmm","bmad/bmm/agents/pm.md","575c091d17651a04e2fa52a88f72c916584ad7d415c508043c5c83a49948cceb"
|
||||
"md","prd-template","bmm","bmad/bmm/workflows/2-plan-workflows/prd/prd-template.md","cf79921e432b992048af21cb4c87ca5cbc14cdf6e279324b3d5990a7f2366ec4"
|
||||
"md","probability-impact","bmm","bmad/bmm/testarch/knowledge/probability-impact.md","446dba0caa1eb162734514f35366f8c38ed3666528b0b5e16c7f03fd3c537d0f"
|
||||
"md","probability-impact","bmm","bmad/bmm/knowledge/tea/probability-impact.md","446dba0caa1eb162734514f35366f8c38ed3666528b0b5e16c7f03fd3c537d0f"
|
||||
"md","project-context","bmm","bmad/bmm/workflows/1-analysis/brainstorm-project/project-context.md","0f1888da4bfc4f24c4de9477bd3ccb2a6fb7aa83c516dfdc1f98fbd08846d4ba"
|
||||
"md","project-overview-template","bmm","bmad/bmm/workflows/document-project/templates/project-overview-template.md","a7c7325b75a5a678dca391b9b69b1e3409cfbe6da95e70443ed3ace164e287b2"
|
||||
"md","quick-spec-flow","bmm","bmad/bmm/docs/quick-spec-flow.md","215d508d27ea94e0091fc32f8dce22fadf990b3b9d8b397e2c393436934f85af"
|
||||
"md","quick-start","bmm","bmad/bmm/docs/quick-start.md","88946558a87bd2eb38990cff74f29b6ef4f81db6f961500f9ca626d168cd0fce"
|
||||
"md","README","bmm","bmad/bmm/README.md","ad4e6d0c002e3a5fef1b695bda79e245fe5a43345375c699165b32d6fc511457"
|
||||
"md","README","bmm","bmad/bmm/docs/README.md","27a835cbc5ed50e4b076d8f0d9454c8e6b6826e69d72ec010df904e891023493"
|
||||
"md","risk-governance","bmm","bmad/bmm/testarch/knowledge/risk-governance.md","2fa2bc3979c4f6d4e1dec09facb2d446f2a4fbc80107b11fc41cbef2b8d65d68"
|
||||
"md","README","bmm","bmad/bmm/knowledge/debug/README.md","ef489db95354e28c475bf2b7dfeb69105585ae899cdc4fff20fab8e16356b62c"
|
||||
"md","README","bmm","bmad/bmm/workflows/debug/README.md","b2a1d7f4a06ff562f0bfc28268fb26bacf06c9fb3f2b8f2b4bea132a435ec5df"
|
||||
"md","risk-governance","bmm","bmad/bmm/knowledge/tea/risk-governance.md","2fa2bc3979c4f6d4e1dec09facb2d446f2a4fbc80107b11fc41cbef2b8d65d68"
|
||||
"md","root-cause-checklist","bmm","bmad/bmm/knowledge/debug/root-cause-checklist.md","fc566ca21d816bf4b7074ae7ff778c3cf6d2e484c62545e2c5a5ac92ff7e1377"
|
||||
"md","scale-adaptive-system","bmm","bmad/bmm/docs/scale-adaptive-system.md","f1bdaac7e6cf96dc115d8fd86c7dc499892ad745a1330221fedbaae1188c6a24"
|
||||
"md","selective-testing","bmm","bmad/bmm/testarch/knowledge/selective-testing.md","c14c8e1bcc309dbb86a60f65bc921abf5a855c18a753e0c0654a108eb3eb1f1c"
|
||||
"md","selector-resilience","bmm","bmad/bmm/testarch/knowledge/selector-resilience.md","a55c25a340f1cd10811802665754a3f4eab0c82868fea61fea9cc61aa47ac179"
|
||||
"md","sm","bmm","bmad/bmm/agents/sm.md","957f431bac1a60c750bc4c84064f80280f9ff53426f4f46b11702e0ab64d8476"
|
||||
"md","selective-testing","bmm","bmad/bmm/knowledge/tea/selective-testing.md","c14c8e1bcc309dbb86a60f65bc921abf5a855c18a753e0c0654a108eb3eb1f1c"
|
||||
"md","selector-resilience","bmm","bmad/bmm/knowledge/tea/selector-resilience.md","a55c25a340f1cd10811802665754a3f4eab0c82868fea61fea9cc61aa47ac179"
|
||||
"md","sm","bmm","bmad/bmm/agents/sm.md","5c12ef2653612145b25e672333e11686ba20d514c34acd90487355f51abd11ab"
|
||||
"md","source-tree-template","bmm","bmad/bmm/workflows/document-project/templates/source-tree-template.md","109bc335ebb22f932b37c24cdc777a351264191825444a4d147c9b82a1e2ad7a"
|
||||
"md","tea","bmm","bmad/bmm/agents/tea.md","f77345c6c5393da31b8045c6d3a4af636de100d20d4a9fec96a949e9c12aaf91"
|
||||
"md","tea","bmm","bmad/bmm/agents/tea.md","e1366956caa0e9ed3f0c35a515cf6f4d8c9cef30c91518fb9deb208198c2b7ab"
|
||||
"md","tech-spec-template","bmm","bmad/bmm/workflows/2-plan-workflows/tech-spec/tech-spec-template.md","2b07373b7b23f71849f107b8fd4356fef71ba5ad88d7f333f05547da1d3be313"
|
||||
"md","tech-writer","bmm","bmad/bmm/agents/tech-writer.md","a5925b4be760cee6b91c2997b8ec224d7889f2a97b6fb91c13ad8ee707b8b3e3"
|
||||
"md","tech-writer","bmm","bmad/bmm/agents/tech-writer.md","2ab53b83669b84424a3a2df455eababa028c9951ffe8c239bfa741912fd260f3"
|
||||
"md","template","bmm","bmad/bmm/workflows/1-analysis/domain-research/template.md","5606843f77007d886cc7ecf1fcfddd1f6dfa3be599239c67eff1d8e40585b083"
|
||||
"md","template","bmm","bmad/bmm/workflows/1-analysis/product-brief/template.md","96f89df7a4dabac6400de0f1d1abe1f2d4713b76fe9433f31c8a885e20d5a5b4"
|
||||
"md","template","bmm","bmad/bmm/workflows/3-solutioning/solutioning-gate-check/template.md","11c3b7573991c001a7f7780daaf5e5dfa4c46c3ea1f250c5bbf86c5e9f13fc8b"
|
||||
|
|
@ -191,17 +211,17 @@ type,name,module,path,hash
|
|||
"md","template-technical","bmm","bmad/bmm/workflows/1-analysis/research/template-technical.md","78caa56ba6eb6922925e5aab4ed4a8245fe744b63c245be29a0612135851f4ca"
|
||||
"md","test-architecture","bmm","bmad/bmm/docs/test-architecture.md","13342dd006b91cd445dcf5a868541b1cf59b40022227e8c87b66669862e993bf"
|
||||
"md","test-design-template","bmm","bmad/bmm/workflows/testarch/test-design/test-design-template.md","cbbc3e3d097dfd31784b9447d07b4b4f4c63dadf2ba0968671ec862da8c30d27"
|
||||
"md","test-healing-patterns","bmm","bmad/bmm/testarch/knowledge/test-healing-patterns.md","b44f7db1ebb1c20ca4ef02d12cae95f692876aee02689605d4b15fe728d28fdf"
|
||||
"md","test-levels-framework","bmm","bmad/bmm/testarch/knowledge/test-levels-framework.md","80bbac7959a47a2e7e7de82613296f906954d571d2d64ece13381c1a0b480237"
|
||||
"md","test-priorities-matrix","bmm","bmad/bmm/testarch/knowledge/test-priorities-matrix.md","321c3b708cc19892884be0166afa2a7197028e5474acaf7bc65c17ac861964a5"
|
||||
"md","test-quality","bmm","bmad/bmm/testarch/knowledge/test-quality.md","97b6db474df0ec7a98a15fd2ae49671bb8e0ddf22963f3c4c47917bb75c05b90"
|
||||
"md","test-review-template","bmm","bmad/bmm/workflows/testarch/test-review/test-review-template.md","3e68a73c48eebf2e0b5bb329a2af9e80554ef443f8cd16652e8343788f249072"
|
||||
"md","timing-debugging","bmm","bmad/bmm/testarch/knowledge/timing-debugging.md","c4c87539bbd3fd961369bb1d7066135d18c6aad7ecd70256ab5ec3b26a8777d9"
|
||||
"md","test-healing-patterns","bmm","bmad/bmm/knowledge/tea/test-healing-patterns.md","b44f7db1ebb1c20ca4ef02d12cae95f692876aee02689605d4b15fe728d28fdf"
|
||||
"md","test-levels-framework","bmm","bmad/bmm/knowledge/tea/test-levels-framework.md","80bbac7959a47a2e7e7de82613296f906954d571d2d64ece13381c1a0b480237"
|
||||
"md","test-priorities-matrix","bmm","bmad/bmm/knowledge/tea/test-priorities-matrix.md","321c3b708cc19892884be0166afa2a7197028e5474acaf7bc65c17ac861964a5"
|
||||
"md","test-quality","bmm","bmad/bmm/knowledge/tea/test-quality.md","97b6db474df0ec7a98a15fd2ae49671bb8e0ddf22963f3c4c47917bb75c05b90"
|
||||
"md","test-review-template","bmm","bmad/bmm/workflows/testarch/test-review/test-review-template.md","d3215aa7bb3573bc8b9022786be9a0f4c74be8abbbfcbb610701e757531f7810"
|
||||
"md","timing-debugging","bmm","bmad/bmm/knowledge/tea/timing-debugging.md","c4c87539bbd3fd961369bb1d7066135d18c6aad7ecd70256ab5ec3b26a8777d9"
|
||||
"md","trace-template","bmm","bmad/bmm/workflows/testarch/trace/trace-template.md","5453a8e4f61b294a1fc0ba42aec83223ae1bcd5c33d7ae0de6de992e3ee42b43"
|
||||
"md","user-story-template","bmm","bmad/bmm/workflows/2-plan-workflows/tech-spec/user-story-template.md","4b179d52088745060991e7cfd853da7d6ce5ac0aa051118c9cecea8d59bdaf87"
|
||||
"md","ux-design-template","bmm","bmad/bmm/workflows/2-plan-workflows/create-ux-design/ux-design-template.md","f9b8ae0fe08c6a23c63815ddd8ed43183c796f266ffe408f3426af1f13b956db"
|
||||
"md","ux-designer","bmm","bmad/bmm/agents/ux-designer.md","5a1ce1b47a4f67b25dd464a94a8149bc86b7690b585738dcfbf273a0a035c7ea"
|
||||
"md","visual-debugging","bmm","bmad/bmm/testarch/knowledge/visual-debugging.md","072a3d30ba6d22d5e628fc26a08f6e03f8b696e49d5a4445f37749ce5cd4a8a9"
|
||||
"md","ux-designer","bmm","bmad/bmm/agents/ux-designer.md","a2a707cc5e5fb3b595fb199baa281a66c0ad9240808be7c04696d62597130173"
|
||||
"md","visual-debugging","bmm","bmad/bmm/knowledge/tea/visual-debugging.md","072a3d30ba6d22d5e628fc26a08f6e03f8b696e49d5a4445f37749ce5cd4a8a9"
|
||||
"md","workflow-architecture-reference","bmm","bmad/bmm/docs/workflow-architecture-reference.md","ce6c43a7f90e7b31655dd1bc9632cda700e105315f5ef25067319792274b2283"
|
||||
"md","workflow-document-project-reference","bmm","bmad/bmm/docs/workflow-document-project-reference.md","464819d23cc4bc88b20c8a668669ae7a6bc7bcb5e4aaa1d0f0998f35ff7ad8df"
|
||||
"md","workflows-analysis","bmm","bmad/bmm/docs/workflows-analysis.md","4dd00c829adcf881ecb96e083f754a4ce109159cfdaff8a5a856590ba33f1d74"
|
||||
|
|
@ -213,7 +233,8 @@ type,name,module,path,hash
|
|||
"yaml","analyst.agent","bmm","bmad/bmm/agents/analyst.agent.yaml",""
|
||||
"yaml","architect.agent","bmm","bmad/bmm/agents/architect.agent.yaml",""
|
||||
"yaml","architecture-patterns","bmm","bmad/bmm/workflows/3-solutioning/architecture/architecture-patterns.yaml","9394c1e632e01534f7a1afd676de74b27f1868f58924f21b542af3631679c552"
|
||||
"yaml","config","bmm","bmad/bmm/config.yaml","5c70cc87f606b834885744f468071c37726736de18a20dec40dc7a88012a61e1"
|
||||
"yaml","config","bmm","bmad/bmm/config.yaml","de65bdf968a6c9dbea2b92c6edf9201dfc8f0cbb93a6d20c182c0023a17727fb"
|
||||
"yaml","debug.agent","bmm","bmad/bmm/agents/debug.agent.yaml",""
|
||||
"yaml","decision-catalog","bmm","bmad/bmm/workflows/3-solutioning/architecture/decision-catalog.yaml","f7fc2ed6ec6c4bd78ec808ad70d24751b53b4835e0aad1088057371f545d3c82"
|
||||
"yaml","deep-dive","bmm","bmad/bmm/workflows/document-project/workflows/deep-dive.yaml","c401fb8d94ca96f3bb0ccc1146269e1bfa4ce4eadab52bd63c7fcff6c2f26216"
|
||||
"yaml","dev.agent","bmm","bmad/bmm/agents/dev.agent.yaml",""
|
||||
|
|
@ -236,6 +257,9 @@ type,name,module,path,hash
|
|||
"yaml","tea.agent","bmm","bmad/bmm/agents/tea.agent.yaml",""
|
||||
"yaml","team-fullstack","bmm","bmad/bmm/teams/team-fullstack.yaml","da8346b10dfad8e1164a11abeb3b0a84a1d8b5f04e01e8490a44ffca477a1b96"
|
||||
"yaml","tech-writer.agent","bmm","bmad/bmm/agents/tech-writer.agent.yaml",""
|
||||
"yaml","template","bmm","bmad/bmm/workflows/debug/debug-report/template.yaml","81b7f88b5c71a884a643a0983af7f9cdc9e7b84560a9634cb643bbac81f5dcd2"
|
||||
"yaml","template","bmm","bmad/bmm/workflows/debug/inspect/template.yaml","9c48b4df344c3e62f5ab574ffc18cca3246171cf34d3775a834f4cab9f6e5780"
|
||||
"yaml","template","bmm","bmad/bmm/workflows/debug/root-cause/template.yaml","7f2adc0b8827d852f1236d66c3a4ccfe2e09ef8ea28e985ed4ff48e7b91a6f15"
|
||||
"yaml","ux-designer.agent","bmm","bmad/bmm/agents/ux-designer.agent.yaml",""
|
||||
"yaml","validation-criteria","bmm","bmad/bmm/workflows/3-solutioning/solutioning-gate-check/validation-criteria.yaml","d690edf5faf95ca1ebd3736e01860b385b05566da415313d524f4db12f9a5af4"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/1-analysis/brainstorm-project/workflow.yaml","38d859ea65db2cc2eebb0dbf1679711dad92710d8da2c2d9753b852055abd970"
|
||||
|
|
@ -248,16 +272,28 @@ type,name,module,path,hash
|
|||
"yaml","workflow","bmm","bmad/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml","d9b6e9405f44de954f83c2328a95a4e10479c292b84ed28a756f5712fc12be17"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/3-solutioning/architecture/workflow.yaml","3ff2ce0d789e1dd73e4427aada3853ac5532cb054559d70f1bc933087e69f4e1"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml","f17268e08ec2b63cf2d109ee42269223117d0330728e960d1105106efd8462b4"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/code-review/workflow.yaml","37215c77c85ffcdcd96f564746e211962f8eeae306c7b8d01d94815cbd252f65"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/code-review/workflow.yaml","840cef147c273f94713b01333e5b990f93ca8cd788ac0d0a76fbc120b11b79da"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml","79663be356876f0734dc24349c2db14a0f27ab53eb635e2ca22d052ccf88ca06"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/create-story/workflow.yaml","feb4206ccdb08021fa40d241135b019b69459ff6cc9e68faccb3ceebf6322b46"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/create-story/workflow.yaml","8bd7c00dba2e69443f1532d576d0a0c3caa667950161082e866a6b446051e484"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml","cef3d12648ba38aa41662490101516384c9b9cd13b0119a7b2f0b0e563e8b1c6"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml","f953cd7cf84d6065e31eeec848fadf3b829fc5e98a2f20c12a4042c30091df34"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml","183de1c1156a9c0787ec31dc1def2ded490735a21c82c85635b24044946b0ae4"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml","47a933e12162326a9258603501f446b27cebdd0f5a6fa19ff5ea00e579decc27"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/story-context/workflow.yaml","06d034ec9b60a97f5e268920f13afbafae495331b54353d144daf0c5a91181e5"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/story-done/workflow.yaml","fa709f77a94b94cf1051cc66e12e1cdc4dfc10100884d47a86dbbe62702288c7"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/story-ready/workflow.yaml","9cef1dbb6d437cb280d5566e0a56d40da1f84a7cb34ad887318deeb6a2a5f544"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml","e6f3fa1b72c0a6a02aa59ed86b59b067a23c8d197f9ddec951ac63303c24c928"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml","6ef70796f28fd9eef4b98e45174941f5ae8f110d8fdaba88f6f831e46ae1d458"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml","eb82a8fbd7938e60b69cc02c28153b0fcffa0c6a5e947f5de0a2aeeefce8fdad"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/story-context/workflow.yaml","f579fc95951f5f32850b94e863ed3bd730fa5822e2b5a65dd14b888056930e18"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/story-done/workflow.yaml","5470150dde72330fbc33d716685b24d7e6b2188ff4285557c3ba395bf2d2f745"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/story-ready/workflow.yaml","74bf06e0adaa3c4c9934e49e071fc71cee5f42635d5715050ca77785f73453be"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/debug/assert-analyze/workflow.yaml","1055976d804167e335ac7330fc8f521070f1496f4ce46668b5014495a773d7de"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/debug/debug-report/workflow.yaml","ec6eb2cdd452137d065f6a558ae66292e51242d66939f828c353bf8497118e3a"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/debug/delta-minimize/workflow.yaml","738ce0b22ae1119cfc896ae7fe9168e407e9f2dabd782e37be48f7eeb60f83bd"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/debug/inspect/workflow.yaml","6a41c0cce9e1520e1417c4ebf7e28fbc5221430a5cc1c496267aa2b08d93c727"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/debug/instrument/workflow.yaml","fbffbfb39a31f274dda0971f98c36638c8d35f932605a317514857607859eee9"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/debug/pattern-analysis/workflow.yaml","c043ef88c023d2302b187f70575b641f413ef61d65955571725c53ceb73f397c"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/debug/quick-debug/workflow.yaml","b55e7979082bfd00279119eac6db04bb9700226f822b4b4efa6b04cb8ce1e2fc"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/debug/root-cause/workflow.yaml","f1018ecac087951f8f2d8da038717ba933142dff37c83494890cf0443740af0d"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/debug/static-scan/workflow.yaml","8e181ca90f838f0f5d7216218f15eadc82c689fb87a7feeef907325e9bcdbad0"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/debug/validate-fix/workflow.yaml","48d9f00c47e9d897aea9a03913837966e5fbd67df31a17e43c5ab91c310b5969"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/debug/walkthrough-prep/workflow.yaml","cf149455520a9953b902fa35cfe9e548e09f3c6009cf274601851b4a81543a5b"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/debug/wolf-fence/workflow.yaml","68246cf8df7ec4919495c0fe38b124fe137d4aa47fa404a5d69c12995f23807f"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/document-project/workflow.yaml","36b65f562bb94eb819728d819e66fd5a23d1b98d1766050c998fd6feaf3df8f6"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/testarch/atdd/workflow.yaml","06474fa7f23657d4145a214771a68e7d894e4488cc5a82c943dad765601f48be"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/testarch/automate/workflow.yaml","e733691f1613e6c55d28a42f745cf396a6f62b62968ff9c42cdb53b2ac3cadcb"
|
||||
|
|
@ -267,15 +303,51 @@ type,name,module,path,hash
|
|||
"yaml","workflow","bmm","bmad/bmm/workflows/testarch/test-design/workflow.yaml","581e91cb914a02b9ae79d1d139264e1dfba663072b6d09dca3250720835fdc60"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/testarch/test-review/workflow.yaml","7c05fab368e2211c97bc9ba92556d6047de4535a28792731215151ef8bf497c5"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/testarch/trace/workflow.yaml","51c96a9c007ca3ef2d39fa199f2d8c7cb33506b20775ef51f80624fc272cd66f"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/workflow-status/init/workflow.yaml","01aae9499f50a40dbbd0018308f3ae016b4d62de3de22d06d2402bdc1a6471a5"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/workflow-status/init/workflow.yaml","1e7c79004ff86abe939796e29a9d19fd72c020e66a8851ab8515c4ed8424e4b3"
|
||||
"yaml","workflow","bmm","bmad/bmm/workflows/workflow-status/workflow.yaml","6a1ad67ec954660fd8e7433b55ab3b75e768f7efa33aad36cf98cdbc2ef6575b"
|
||||
"yaml","workflow-status-template","bmm","bmad/bmm/workflows/workflow-status/workflow-status-template.yaml","6021202726d2b81f28908ffeb93330d25bcd52986823200e01b814d67c1677dd"
|
||||
"csv","default-party","cis","bmad/cis/teams/default-party.csv","352ab9a0809da706759e265da66f91884b80a6270fe85ff7f7fe8cbba61fa3a2"
|
||||
"csv","design-methods","cis","bmad/cis/workflows/design-thinking/design-methods.csv","6735e9777620398e35b7b8ccb21e9263d9164241c3b9973eb76f5112fb3a8fc9"
|
||||
"csv","innovation-frameworks","cis","bmad/cis/workflows/innovation-strategy/innovation-frameworks.csv","9a14473b1d667467172d8d161e91829c174e476a030a983f12ec6af249c4e42f"
|
||||
"csv","solving-methods","cis","bmad/cis/workflows/problem-solving/solving-methods.csv","aa15c3a862523f20c199600d8d4d0a23fce1001010d7efc29a71abe537d42995"
|
||||
"csv","story-types","cis","bmad/cis/workflows/storytelling/story-types.csv","ec5a3c713617bf7e2cf7db439303dd8f3363daa2f6db20a350c82260ade88bdb"
|
||||
"md","brainstorming-coach","cis","bmad/cis/agents/brainstorming-coach.md","75ac8ab61acbc3cd26e4c26860a0b45190c4a76bf08a70103084d12666df5be6"
|
||||
"md","creative-problem-solver","cis","bmad/cis/agents/creative-problem-solver.md","ecdc5e547f73a420052a5c4aabd12ad4cceeb4749dcb819472b6ec4c500983f0"
|
||||
"md","design-thinking-coach","cis","bmad/cis/agents/design-thinking-coach.md","ad7930597ef0e9a88692a7207fb67c6f85a610429c9e2c598a2778f52872fe14"
|
||||
"md","innovation-strategist","cis","bmad/cis/agents/innovation-strategist.md","2326c62cad728e8ec969e579f659353f9617b42b76809155dd9cc1a30f53061c"
|
||||
"md","instructions","cis","bmad/cis/workflows/design-thinking/instructions.md","9cbcc76146036f37081f4f26662387d0b054aedd129c998d820c1b4c8f25c9bd"
|
||||
"md","instructions","cis","bmad/cis/workflows/innovation-strategy/instructions.md","5cb701bd9f656a165ec853984cf8163eebc19034129bb9360bb19564e407db43"
|
||||
"md","instructions","cis","bmad/cis/workflows/problem-solving/instructions.md","caa996c5a2d14d1993c93664b09d6594d33f6a89b419b343d0bf7540217cb341"
|
||||
"md","instructions","cis","bmad/cis/workflows/storytelling/instructions.md","f0aad32f46badbb2b916af245cdae27b49986fcae548793eb783624ee0ace295"
|
||||
"md","readme","cis","bmad/cis/readme.md","aa493c5bc9b1f5db0c46e8ece9c5d9d10b5d1d4d0d3ea0c102b002df62d4eac8"
|
||||
"md","README","cis","bmad/cis/agents/README.md","304fac869ca6a76660df270bb92af6394f3c98e8fd3ec36c9ea69c3e65f3f965"
|
||||
"md","README","cis","bmad/cis/workflows/README.md","013f3bf86267a29506aebc3c58826316381295476030d0a6a29f4cc90c91174e"
|
||||
"md","README","cis","bmad/cis/workflows/design-thinking/README.md","0a38f88352dc4674f6e1f55a67ffebf403bf329c874a21a49ce7834c08f91f62"
|
||||
"md","README","cis","bmad/cis/workflows/innovation-strategy/README.md","820a9e734fadf2cfac94d499cec2e4b41a54d054c0d2f6b9819da319beee4fb9"
|
||||
"md","README","cis","bmad/cis/workflows/problem-solving/README.md","a5e75b9899751d7aabffcf65785f10d4d2e0455f8c7c541e8a143e3babceca8b"
|
||||
"md","README","cis","bmad/cis/workflows/storytelling/README.md","1bad4223dce51cb5a7ab8c116467f78037a4583d3a840210ee2f160ad15b71ee"
|
||||
"md","storyteller","cis","bmad/cis/agents/storyteller.md","4b3c86df7f56f2d43b9145c2eb28d6b26c61a179bc1a1f55013d4283ef13238b"
|
||||
"md","template","cis","bmad/cis/workflows/design-thinking/template.md","7834c387ac0412c841b49a9fcdd8043f5ce053e5cb26993548cf4d31b561f6f0"
|
||||
"md","template","cis","bmad/cis/workflows/innovation-strategy/template.md","3e649531c0d8ac94e147159cd456aa0e1726439e8518c3ccc2ad08fc486aed59"
|
||||
"md","template","cis","bmad/cis/workflows/problem-solving/template.md","6c9efd7ac7b10010bd9911db16c2fbdca01fb0c306d871fa6381eef700b45608"
|
||||
"md","template","cis","bmad/cis/workflows/storytelling/template.md","461981aa772ef2df238070cbec90fc40995df2a71a8c22225b90c91afed57452"
|
||||
"yaml","brainstorming-coach.agent","cis","bmad/cis/agents/brainstorming-coach.agent.yaml",""
|
||||
"yaml","config","cis","bmad/cis/config.yaml","9e40f50752a01bcb0a71c70601544834a43ece1f2d390ac4b3a0c4a6fa8d3d86"
|
||||
"yaml","creative-problem-solver.agent","cis","bmad/cis/agents/creative-problem-solver.agent.yaml",""
|
||||
"yaml","creative-squad","cis","bmad/cis/teams/creative-squad.yaml","25407cf0ebdf5b10884cd03c86068e04715ef270ada93a3b64cb9907b62c71cf"
|
||||
"yaml","design-thinking-coach.agent","cis","bmad/cis/agents/design-thinking-coach.agent.yaml",""
|
||||
"yaml","innovation-strategist.agent","cis","bmad/cis/agents/innovation-strategist.agent.yaml",""
|
||||
"yaml","storyteller.agent","cis","bmad/cis/agents/storyteller.agent.yaml",""
|
||||
"yaml","workflow","cis","bmad/cis/workflows/design-thinking/workflow.yaml","072b1bcafb69b7b4658015f956681c962b742cd84f158b94b9fdc61ac1982334"
|
||||
"yaml","workflow","cis","bmad/cis/workflows/innovation-strategy/workflow.yaml","a33fc601a48fdec8863e784cdd425fc7a211bb542bbacd425e76eba8565e17d3"
|
||||
"yaml","workflow","cis","bmad/cis/workflows/problem-solving/workflow.yaml","66444d53a81b53c1e39bd1d90c4e4f9efbf4f74c282ebe185b69808b1f48e528"
|
||||
"yaml","workflow","cis","bmad/cis/workflows/storytelling/workflow.yaml","cd611d6e662bd04d96b682b91c43723ac7f9b66fbb04d0e915872b0549b38cb8"
|
||||
"csv","adv-elicit-methods","core","bmad/core/tasks/adv-elicit-methods.csv","b4e925870f902862899f12934e617c3b4fe002d1b652c99922b30fa93482533b"
|
||||
"csv","brain-methods","core","bmad/core/workflows/brainstorming/brain-methods.csv","ecffe2f0ba263aac872b2d2c95a3f7b1556da2a980aa0edd3764ffb2f11889f3"
|
||||
"md","bmad-master","core","bmad/core/agents/bmad-master.md","906028c592f49b6b9962c7efa63535b069b731237d28617a56434d061210d02a"
|
||||
"md","bmad-master","core","bmad/core/agents/bmad-master.md","684b7872611e5979fbe420e0c96e9910355e181b49aed0317d872381e154e299"
|
||||
"md","instructions","core","bmad/core/workflows/brainstorming/instructions.md","f737f1645d0f7af37fddd1d4ac8a387f26999d0be5748ce41bdbcf2b89738413"
|
||||
"md","instructions","core","bmad/core/workflows/party-mode/instructions.md","768a835653fea54cbf4f7136e19f968add5ccf4b1dbce5636c5268d74b1b7181"
|
||||
"md","README","core","bmad/core/workflows/brainstorming/README.md","92d624c9ec560297003db0616671fbd6c278d9ea3dacf1c6cf41f064bacec926"
|
||||
"md","README","core","bmad/core/workflows/brainstorming/README.md","1265e0283a3741c7137804089a5043452a789688da3274a188a75d9b6f89eb38"
|
||||
"md","template","core","bmad/core/workflows/brainstorming/template.md","b5c760f4cea2b56c75ef76d17a87177b988ac846657f4b9819ec125d125b7386"
|
||||
"xml","adv-elicit","core","bmad/core/tasks/adv-elicit.xml","4f45442af426a269c0af709348efe431e335ff45bb8eda7d01e7d100c57e03b9"
|
||||
"xml","bmad-web-orchestrator.agent","core","bmad/core/agents/bmad-web-orchestrator.agent.xml","ac09744c3ad70443fbe6873d6a1345c09ad4ab1fe3e310e3230c912967cb51e9"
|
||||
|
|
@ -284,6 +356,6 @@ type,name,module,path,hash
|
|||
"xml","validate-workflow","core","bmad/core/tasks/validate-workflow.xml","63580411c759ee317e58da8bda6ceba27dbf9d3742f39c5c705afcd27361a9ee"
|
||||
"xml","workflow","core","bmad/core/tasks/workflow.xml","f7500bdc26a0d4630674000788d9dbc376b03347aea221b90afcdbb0a1e569d7"
|
||||
"yaml","bmad-master.agent","core","bmad/core/agents/bmad-master.agent.yaml",""
|
||||
"yaml","config","core","bmad/core/config.yaml","1b581a5489df69af7425c5ab4730e78fcc720d9e886b7e8cf13d03015229d536"
|
||||
"yaml","config","core","bmad/core/config.yaml","72ad5a72650c4e377d79838b65f56a7536a8b04eebcc8cd6d5c3733d82c45ae8"
|
||||
"yaml","workflow","core","bmad/core/workflows/brainstorming/workflow.yaml","0af588d7096facdd79c701b37463b6a0e497b0b4339a951d7d3342d8a48fe6c1"
|
||||
"yaml","workflow","core","bmad/core/workflows/party-mode/workflow.yaml","5b5bd943eaa96b573ca1fce4120d17fab7e766a9204dd43c899ec2cc4b0561f6"
|
||||
"yaml","workflow","core","bmad/core/workflows/party-mode/workflow.yaml","413879486320edfe88501892ea68cb88f6d44dcd54e9c12fb24b0ae4dbdb81dc"
|
||||
|
|
|
|||
|
|
|
@ -0,0 +1,7 @@
|
|||
ide: claude-code
|
||||
configured_date: "2025-11-10T17:57:56.381Z"
|
||||
last_updated: "2025-11-10T17:57:56.381Z"
|
||||
configuration:
|
||||
subagentChoices:
|
||||
install: all
|
||||
installLocation: project
|
||||
|
|
@ -1,10 +1,12 @@
|
|||
installation:
|
||||
version: 6.0.0-alpha.7
|
||||
installDate: "2025-11-09T05:23:00.252Z"
|
||||
lastUpdated: "2025-11-09T05:23:00.252Z"
|
||||
version: 6.0.0-alpha.8
|
||||
installDate: "2025-11-10T17:57:56.318Z"
|
||||
lastUpdated: "2025-11-10T17:57:56.318Z"
|
||||
modules:
|
||||
- core
|
||||
- bmb
|
||||
- bmm
|
||||
- cis
|
||||
ides:
|
||||
- claude-code
|
||||
- github-copilot
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
name,displayName,description,module,path,standalone
|
||||
"adv-elicit","Advanced Elicitation","When called from workflow","core","bmad/core/tasks/adv-elicit.xml","true"
|
||||
"index-docs","Index Docs","Generates or updates an index.md of all documents in the specified directory","core","bmad/core/tasks/index-docs.xml","true"
|
||||
"validate-workflow","Validate Workflow Output","Run a checklist against a document with thorough analysis and produce a validation report","core","bmad/core/tasks/validate-workflow.xml","false"
|
||||
"workflow","Execute Workflow","Execute given workflow by loading its configuration, following instructions, and producing output","core","bmad/core/tasks/workflow.xml","false"
|
||||
"daily-standup","Daily Standup","","bmm","bmad/bmm/tasks/daily-standup.xml","false"
|
||||
"adv-elicit","Advanced Elicitation","When called from workflow","core",".bmad/core/tasks/adv-elicit.xml","true"
|
||||
"index-docs","Index Docs","Generates or updates an index.md of all documents in the specified directory","core",".bmad/core/tasks/index-docs.xml","true"
|
||||
"validate-workflow","Validate Workflow Output","Run a checklist against a document with thorough analysis and produce a validation report","core",".bmad/core/tasks/validate-workflow.xml","false"
|
||||
"workflow","Execute Workflow","Execute given workflow by loading its configuration, following instructions, and producing output","core",".bmad/core/tasks/workflow.xml","false"
|
||||
"daily-standup","Daily Standup","","bmm",".bmad/bmm/tasks/daily-standup.xml","false"
|
||||
|
|
|
|||
|
|
|
@ -1,2 +1,2 @@
|
|||
name,displayName,description,module,path,standalone
|
||||
"shard-doc","Shard Document","Splits large markdown documents into smaller, organized files based on level 2 (default) sections","core","bmad/core/tools/shard-doc.xml","true"
|
||||
"shard-doc","Shard Document","Splits large markdown documents into smaller, organized files based on level 2 (default) sections","core",".bmad/core/tools/shard-doc.xml","true"
|
||||
|
|
|
|||
|
|
|
@ -1,60 +1,60 @@
|
|||
name,description,module,path,standalone
|
||||
"brainstorming","Facilitate interactive brainstorming sessions using diverse creative techniques. This workflow facilitates interactive brainstorming sessions using diverse creative techniques. The session is highly interactive, with the AI acting as a facilitator to guide the user through various ideation methods to generate and refine creative solutions.","core","bmad/core/workflows/brainstorming/workflow.yaml","true"
|
||||
"party-mode","Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations","core","bmad/core/workflows/party-mode/workflow.yaml","true"
|
||||
"audit-workflow","Comprehensive workflow quality audit - validates structure, config standards, variable usage, bloat detection, and web_bundle completeness. Performs deep analysis of workflow.yaml, instructions.md, template.md, and web_bundle configuration against BMAD v6 standards.","bmb","bmad/bmb/workflows/audit-workflow/workflow.yaml","true"
|
||||
"convert-legacy","Converts legacy BMAD v4 or similar items (agents, workflows, modules) to BMad Core compliant format with proper structure and conventions","bmb","bmad/bmb/workflows/convert-legacy/workflow.yaml","true"
|
||||
"create-agent","Interactive workflow to build BMAD Core compliant agents (YAML source compiled to .md during install) with optional brainstorming, persona development, and command structure","bmb","bmad/bmb/workflows/create-agent/workflow.yaml","true"
|
||||
"create-module","Interactive workflow to build complete BMAD modules with agents, workflows, tasks, and installation infrastructure","bmb","bmad/bmb/workflows/create-module/workflow.yaml","true"
|
||||
"create-workflow","Interactive workflow builder that guides creation of new BMAD workflows with proper structure and validation for optimal human-AI collaboration. Includes optional brainstorming phase for workflow ideas and design.","bmb","bmad/bmb/workflows/create-workflow/workflow.yaml","true"
|
||||
"edit-agent","Edit existing BMAD agents while following all best practices and conventions","bmb","bmad/bmb/workflows/edit-agent/workflow.yaml","true"
|
||||
"edit-module","Edit existing BMAD modules (structure, agents, workflows, documentation) while following all best practices","bmb","bmad/bmb/workflows/edit-module/workflow.yaml","true"
|
||||
"edit-workflow","Edit existing BMAD workflows while following all best practices and conventions","bmb","bmad/bmb/workflows/edit-workflow/workflow.yaml","true"
|
||||
"module-brief","Create a comprehensive Module Brief that serves as the blueprint for building new BMAD modules using strategic analysis and creative vision","bmb","bmad/bmb/workflows/module-brief/workflow.yaml","true"
|
||||
"redoc","Autonomous documentation system that maintains module, workflow, and agent documentation using a reverse-tree approach (leaf folders first, then parents). Understands BMAD conventions and produces technical writer quality output.","bmb","bmad/bmb/workflows/redoc/workflow.yaml","true"
|
||||
"brainstorm-project","Facilitate project brainstorming sessions by orchestrating the CIS brainstorming workflow with project-specific context and guidance.","bmm","bmad/bmm/workflows/1-analysis/brainstorm-project/workflow.yaml","true"
|
||||
"domain-research","Collaborative exploration of domain-specific requirements, regulations, and patterns for complex projects","bmm","bmad/bmm/workflows/1-analysis/domain-research/workflow.yaml","true"
|
||||
"product-brief","Interactive product brief creation workflow that guides users through defining their product vision with multiple input sources and conversational collaboration","bmm","bmad/bmm/workflows/1-analysis/product-brief/workflow.yaml","true"
|
||||
"research","Adaptive research workflow supporting multiple research types: market research, deep research prompt generation, technical/architecture evaluation, competitive intelligence, user research, and domain analysis","bmm","bmad/bmm/workflows/1-analysis/research/workflow.yaml","true"
|
||||
"create-ux-design","Collaborative UX design facilitation workflow that creates exceptional user experiences through visual exploration and informed decision-making. Unlike template-driven approaches, this workflow facilitates discovery, generates visual options, and collaboratively designs the UX with the user at every step.","bmm","bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml","true"
|
||||
"create-epics-and-stories","Transform PRD requirements into bite-sized stories organized in epics for 200k context dev agents","bmm","bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/workflow.yaml","true"
|
||||
"prd","Unified PRD workflow for BMad Method and Enterprise Method tracks. Produces strategic PRD and tactical epic breakdown. Hands off to architecture workflow for technical design. Note: Quick Flow track uses tech-spec workflow.","bmm","bmad/bmm/workflows/2-plan-workflows/prd/workflow.yaml","true"
|
||||
"tech-spec","Technical specification workflow for Level 0 projects (single atomic changes). Creates focused tech spec for bug fixes, single endpoint additions, or small isolated changes. Tech-spec only - no PRD needed.","bmm","bmad/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml","true"
|
||||
"architecture","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.","bmm","bmad/bmm/workflows/3-solutioning/architecture/workflow.yaml","true"
|
||||
"solutioning-gate-check","Systematically validate that all planning and solutioning phases are complete and properly aligned before transitioning to Phase 4 implementation. Ensures PRD, architecture, and stories are cohesive with no gaps or contradictions.","bmm","bmad/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml","true"
|
||||
"code-review","Perform a Senior Developer code review on a completed story flagged Ready for Review, leveraging story-context, epic tech-spec, repo docs, MCP servers for latest best-practices, and web search as fallback. Appends structured review notes to the story.","bmm","bmad/bmm/workflows/4-implementation/code-review/workflow.yaml","true"
|
||||
"correct-course","Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation","bmm","bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml","true"
|
||||
"create-story","Create the next user story markdown from epics/PRD and architecture, using a standard template and saving to the stories folder","bmm","bmad/bmm/workflows/4-implementation/create-story/workflow.yaml","true"
|
||||
"dev-story","Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria","bmm","bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml","true"
|
||||
"epic-tech-context","Generate a comprehensive Technical Specification from PRD and Architecture with acceptance criteria and traceability mapping","bmm","bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml","true"
|
||||
"retrospective","Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic","bmm","bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml","true"
|
||||
"sprint-planning","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","bmm","bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml","true"
|
||||
"story-context","Assemble a dynamic Story Context XML by pulling latest documentation and existing code/library artifacts relevant to a drafted story","bmm","bmad/bmm/workflows/4-implementation/story-context/workflow.yaml","true"
|
||||
"story-done","Marks a story as done (DoD complete) and moves it from its current status → DONE in the status file. Advances the story queue. Simple status-update workflow with no searching required.","bmm","bmad/bmm/workflows/4-implementation/story-done/workflow.yaml","true"
|
||||
"story-ready","Marks a drafted story as ready for development and moves it from TODO → IN PROGRESS in the status file. Simple status-update workflow with no searching required.","bmm","bmad/bmm/workflows/4-implementation/story-ready/workflow.yaml","true"
|
||||
"debug-assert-analyze","Analyze code for missing assertions and invariants. Suggests defensive programming improvements.","bmm","bmad/bmm/workflows/debug/assert-analyze/workflow.yaml","false"
|
||||
"debug-report","Generate comprehensive debug report consolidating all findings, analyses, and recommendations from debugging session.","bmm","bmad/bmm/workflows/debug/debug-report/workflow.yaml","false"
|
||||
"debug-delta-minimize","Automatically reduce failing test case to minimal reproduction. Essential for complex input-dependent failures.","bmm","bmad/bmm/workflows/debug/delta-minimize/workflow.yaml","false"
|
||||
"debug-inspect","Comprehensive Fagan inspection for systematic bug analysis and resolution. Achieves 60-90% defect detection rates through formal 6-phase methodology.","bmm","bmad/bmm/workflows/debug/inspect/workflow.yaml","false"
|
||||
"debug-instrument","Design strategic logging and monitoring points. Creates instrumentation plan for production debugging.","bmm","bmad/bmm/workflows/debug/instrument/workflow.yaml","false"
|
||||
"debug-pattern-analysis","Analyze recent commits and code changes for defect patterns and systemic issues.","bmm","bmad/bmm/workflows/debug/pattern-analysis/workflow.yaml","false"
|
||||
"debug-quick","Rapid triage and initial analysis for simple issues. Provides immediate assessment and suggested next steps.","bmm","bmad/bmm/workflows/debug/quick-debug/workflow.yaml","false"
|
||||
"debug-root-cause","Focused root cause analysis using fishbone (Ishikawa) methodology and 5-Whys technique to identify underlying defect causes.","bmm","bmad/bmm/workflows/debug/root-cause/workflow.yaml","false"
|
||||
"debug-static-scan","Perform comprehensive static analysis for common defects. Identifies anti-patterns, security issues, and code smells.","bmm","bmad/bmm/workflows/debug/static-scan/workflow.yaml","false"
|
||||
"debug-validate-fix","Verify proposed fix addresses root cause without side effects. Includes regression risk assessment.","bmm","bmad/bmm/workflows/debug/validate-fix/workflow.yaml","false"
|
||||
"debug-walkthrough-prep","Generate materials for code walkthrough session. Creates review checklist and presentation outline.","bmm","bmad/bmm/workflows/debug/walkthrough-prep/workflow.yaml","false"
|
||||
"debug-wolf-fence","Execute binary search debugging to isolate bug location efficiently. Highly effective for large codebases.","bmm","bmad/bmm/workflows/debug/wolf-fence/workflow.yaml","false"
|
||||
"document-project","Analyzes and documents brownfield projects by scanning codebase, architecture, and patterns to create comprehensive reference documentation for AI-assisted development","bmm","bmad/bmm/workflows/document-project/workflow.yaml","true"
|
||||
"testarch-atdd","Generate failing acceptance tests before implementation using TDD red-green-refactor cycle","bmm","bmad/bmm/workflows/testarch/atdd/workflow.yaml","false"
|
||||
"testarch-automate","Expand test automation coverage after implementation or analyze existing codebase to generate comprehensive test suite","bmm","bmad/bmm/workflows/testarch/automate/workflow.yaml","false"
|
||||
"testarch-ci","Scaffold CI/CD quality pipeline with test execution, burn-in loops, and artifact collection","bmm","bmad/bmm/workflows/testarch/ci/workflow.yaml","false"
|
||||
"testarch-framework","Initialize production-ready test framework architecture (Playwright or Cypress) with fixtures, helpers, and configuration","bmm","bmad/bmm/workflows/testarch/framework/workflow.yaml","false"
|
||||
"testarch-nfr","Assess non-functional requirements (performance, security, reliability, maintainability) before release with evidence-based validation","bmm","bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml","false"
|
||||
"testarch-test-design","Plan risk mitigation and test coverage strategy before development with risk assessment and prioritization","bmm","bmad/bmm/workflows/testarch/test-design/workflow.yaml","false"
|
||||
"testarch-test-review","Review test quality using comprehensive knowledge base and best practices validation","bmm","bmad/bmm/workflows/testarch/test-review/workflow.yaml","false"
|
||||
"testarch-trace","Generate requirements-to-tests traceability matrix, analyze coverage, and make quality gate decision (PASS/CONCERNS/FAIL/WAIVED)","bmm","bmad/bmm/workflows/testarch/trace/workflow.yaml","false"
|
||||
"workflow-init","Initialize a new BMM project by determining level, type, and creating workflow path","bmm","bmad/bmm/workflows/workflow-status/init/workflow.yaml","true"
|
||||
"workflow-status","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.","bmm","bmad/bmm/workflows/workflow-status/workflow.yaml","true"
|
||||
"design-thinking","Guide human-centered design processes using empathy-driven methodologies. This workflow walks through the design thinking phases - Empathize, Define, Ideate, Prototype, and Test - to create solutions deeply rooted in user needs.","cis","bmad/cis/workflows/design-thinking/workflow.yaml","true"
|
||||
"innovation-strategy","Identify disruption opportunities and architect business model innovation. This workflow guides strategic analysis of markets, competitive dynamics, and business model innovation to uncover sustainable competitive advantages and breakthrough opportunities.","cis","bmad/cis/workflows/innovation-strategy/workflow.yaml","true"
|
||||
"problem-solving","Apply systematic problem-solving methodologies to crack complex challenges. This workflow guides through problem diagnosis, root cause analysis, creative solution generation, evaluation, and implementation planning using proven frameworks.","cis","bmad/cis/workflows/problem-solving/workflow.yaml","true"
|
||||
"storytelling","Craft compelling narratives using proven story frameworks and techniques. This workflow guides users through structured narrative development, applying appropriate story frameworks to create emotionally resonant and engaging stories for any purpose.","cis","bmad/cis/workflows/storytelling/workflow.yaml","true"
|
||||
"brainstorming","Facilitate interactive brainstorming sessions using diverse creative techniques. This workflow facilitates interactive brainstorming sessions using diverse creative techniques. The session is highly interactive, with the AI acting as a facilitator to guide the user through various ideation methods to generate and refine creative solutions.","core",".bmad/core/workflows/brainstorming/workflow.yaml","true"
|
||||
"party-mode","Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations","core",".bmad/core/workflows/party-mode/workflow.yaml","true"
|
||||
"audit-workflow","Comprehensive workflow quality audit - validates structure, config standards, variable usage, bloat detection, and web_bundle completeness. Performs deep analysis of workflow.yaml, instructions.md, template.md, and web_bundle configuration against BMAD v6 standards.","bmb",".bmad/bmb/workflows/audit-workflow/workflow.yaml","true"
|
||||
"convert-legacy","Converts legacy BMAD v4 or similar items (agents, workflows, modules) to BMad Core compliant format with proper structure and conventions","bmb",".bmad/bmb/workflows/convert-legacy/workflow.yaml","true"
|
||||
"create-agent","Interactive workflow to build BMAD Core compliant agents (YAML source compiled to .md during install) with optional brainstorming, persona development, and command structure","bmb",".bmad/bmb/workflows/create-agent/workflow.yaml","true"
|
||||
"create-module","Interactive workflow to build complete BMAD modules with agents, workflows, tasks, and installation infrastructure","bmb",".bmad/bmb/workflows/create-module/workflow.yaml","true"
|
||||
"create-workflow","Interactive workflow builder that guides creation of new BMAD workflows with proper structure and validation for optimal human-AI collaboration. Includes optional brainstorming phase for workflow ideas and design.","bmb",".bmad/bmb/workflows/create-workflow/workflow.yaml","true"
|
||||
"edit-agent","Edit existing BMAD agents while following all best practices and conventions","bmb",".bmad/bmb/workflows/edit-agent/workflow.yaml","true"
|
||||
"edit-module","Edit existing BMAD modules (structure, agents, workflows, documentation) while following all best practices","bmb",".bmad/bmb/workflows/edit-module/workflow.yaml","true"
|
||||
"edit-workflow","Edit existing BMAD workflows while following all best practices and conventions","bmb",".bmad/bmb/workflows/edit-workflow/workflow.yaml","true"
|
||||
"module-brief","Create a comprehensive Module Brief that serves as the blueprint for building new BMAD modules using strategic analysis and creative vision","bmb",".bmad/bmb/workflows/module-brief/workflow.yaml","true"
|
||||
"redoc","Autonomous documentation system that maintains module, workflow, and agent documentation using a reverse-tree approach (leaf folders first, then parents). Understands BMAD conventions and produces technical writer quality output.","bmb",".bmad/bmb/workflows/redoc/workflow.yaml","true"
|
||||
"brainstorm-project","Facilitate project brainstorming sessions by orchestrating the CIS brainstorming workflow with project-specific context and guidance.","bmm",".bmad/bmm/workflows/1-analysis/brainstorm-project/workflow.yaml","true"
|
||||
"domain-research","Collaborative exploration of domain-specific requirements, regulations, and patterns for complex projects","bmm",".bmad/bmm/workflows/1-analysis/domain-research/workflow.yaml","true"
|
||||
"product-brief","Interactive product brief creation workflow that guides users through defining their product vision with multiple input sources and conversational collaboration","bmm",".bmad/bmm/workflows/1-analysis/product-brief/workflow.yaml","true"
|
||||
"research","Adaptive research workflow supporting multiple research types: market research, deep research prompt generation, technical/architecture evaluation, competitive intelligence, user research, and domain analysis","bmm",".bmad/bmm/workflows/1-analysis/research/workflow.yaml","true"
|
||||
"create-ux-design","Collaborative UX design facilitation workflow that creates exceptional user experiences through visual exploration and informed decision-making. Unlike template-driven approaches, this workflow facilitates discovery, generates visual options, and collaboratively designs the UX with the user at every step.","bmm",".bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml","true"
|
||||
"create-epics-and-stories","Transform PRD requirements into bite-sized stories organized in epics for 200k context dev agents","bmm",".bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/workflow.yaml","true"
|
||||
"prd","Unified PRD workflow for BMad Method and Enterprise Method tracks. Produces strategic PRD and tactical epic breakdown. Hands off to architecture workflow for technical design. Note: Quick Flow track uses tech-spec workflow.","bmm",".bmad/bmm/workflows/2-plan-workflows/prd/workflow.yaml","true"
|
||||
"tech-spec","Technical specification workflow for Level 0 projects (single atomic changes). Creates focused tech spec for bug fixes, single endpoint additions, or small isolated changes. Tech-spec only - no PRD needed.","bmm",".bmad/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml","true"
|
||||
"architecture","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.","bmm",".bmad/bmm/workflows/3-solutioning/architecture/workflow.yaml","true"
|
||||
"solutioning-gate-check","Systematically validate that all planning and solutioning phases are complete and properly aligned before transitioning to Phase 4 implementation. Ensures PRD, architecture, and stories are cohesive with no gaps or contradictions.","bmm",".bmad/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml","true"
|
||||
"code-review","Perform a Senior Developer code review on a completed story flagged Ready for Review, leveraging story-context, epic tech-spec, repo docs, MCP servers for latest best-practices, and web search as fallback. Appends structured review notes to the story.","bmm",".bmad/bmm/workflows/4-implementation/code-review/workflow.yaml","true"
|
||||
"correct-course","Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation","bmm",".bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml","true"
|
||||
"create-story","Create the next user story markdown from epics/PRD and architecture, using a standard template and saving to the stories folder","bmm",".bmad/bmm/workflows/4-implementation/create-story/workflow.yaml","true"
|
||||
"dev-story","Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria","bmm",".bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml","true"
|
||||
"epic-tech-context","Generate a comprehensive Technical Specification from PRD and Architecture with acceptance criteria and traceability mapping","bmm",".bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml","true"
|
||||
"retrospective","Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic","bmm",".bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml","true"
|
||||
"sprint-planning","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","bmm",".bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml","true"
|
||||
"story-context","Assemble a dynamic Story Context XML by pulling latest documentation and existing code/library artifacts relevant to a drafted story","bmm",".bmad/bmm/workflows/4-implementation/story-context/workflow.yaml","true"
|
||||
"story-done","Marks a story as done (DoD complete) and moves it from its current status → DONE in the status file. Advances the story queue. Simple status-update workflow with no searching required.","bmm",".bmad/bmm/workflows/4-implementation/story-done/workflow.yaml","true"
|
||||
"story-ready","Marks a drafted story as ready for development and moves it from TODO → IN PROGRESS in the status file. Simple status-update workflow with no searching required.","bmm",".bmad/bmm/workflows/4-implementation/story-ready/workflow.yaml","true"
|
||||
"debug-assert-analyze","Analyze code for missing assertions and invariants. Suggests defensive programming improvements.","bmm",".bmad/bmm/workflows/debug/assert-analyze/workflow.yaml","false"
|
||||
"debug-report","Generate comprehensive debug report consolidating all findings, analyses, and recommendations from debugging session.","bmm",".bmad/bmm/workflows/debug/debug-report/workflow.yaml","false"
|
||||
"debug-delta-minimize","Automatically reduce failing test case to minimal reproduction. Essential for complex input-dependent failures.","bmm",".bmad/bmm/workflows/debug/delta-minimize/workflow.yaml","false"
|
||||
"debug-inspect","Comprehensive Fagan inspection for systematic bug analysis and resolution. Achieves 60-90% defect detection rates through formal 6-phase methodology.","bmm",".bmad/bmm/workflows/debug/inspect/workflow.yaml","false"
|
||||
"debug-instrument","Design strategic logging and monitoring points. Creates instrumentation plan for production debugging.","bmm",".bmad/bmm/workflows/debug/instrument/workflow.yaml","false"
|
||||
"debug-pattern-analysis","Analyze recent commits and code changes for defect patterns and systemic issues.","bmm",".bmad/bmm/workflows/debug/pattern-analysis/workflow.yaml","false"
|
||||
"debug-quick","Rapid triage and initial analysis for simple issues. Provides immediate assessment and suggested next steps.","bmm",".bmad/bmm/workflows/debug/quick-debug/workflow.yaml","false"
|
||||
"debug-root-cause","Focused root cause analysis using fishbone (Ishikawa) methodology and 5-Whys technique to identify underlying defect causes.","bmm",".bmad/bmm/workflows/debug/root-cause/workflow.yaml","false"
|
||||
"debug-static-scan","Perform comprehensive static analysis for common defects. Identifies anti-patterns, security issues, and code smells.","bmm",".bmad/bmm/workflows/debug/static-scan/workflow.yaml","false"
|
||||
"debug-validate-fix","Verify proposed fix addresses root cause without side effects. Includes regression risk assessment.","bmm",".bmad/bmm/workflows/debug/validate-fix/workflow.yaml","false"
|
||||
"debug-walkthrough-prep","Generate materials for code walkthrough session. Creates review checklist and presentation outline.","bmm",".bmad/bmm/workflows/debug/walkthrough-prep/workflow.yaml","false"
|
||||
"debug-wolf-fence","Execute binary search debugging to isolate bug location efficiently. Highly effective for large codebases.","bmm",".bmad/bmm/workflows/debug/wolf-fence/workflow.yaml","false"
|
||||
"document-project","Analyzes and documents brownfield projects by scanning codebase, architecture, and patterns to create comprehensive reference documentation for AI-assisted development","bmm",".bmad/bmm/workflows/document-project/workflow.yaml","true"
|
||||
"testarch-atdd","Generate failing acceptance tests before implementation using TDD red-green-refactor cycle","bmm",".bmad/bmm/workflows/testarch/atdd/workflow.yaml","false"
|
||||
"testarch-automate","Expand test automation coverage after implementation or analyze existing codebase to generate comprehensive test suite","bmm",".bmad/bmm/workflows/testarch/automate/workflow.yaml","false"
|
||||
"testarch-ci","Scaffold CI/CD quality pipeline with test execution, burn-in loops, and artifact collection","bmm",".bmad/bmm/workflows/testarch/ci/workflow.yaml","false"
|
||||
"testarch-framework","Initialize production-ready test framework architecture (Playwright or Cypress) with fixtures, helpers, and configuration","bmm",".bmad/bmm/workflows/testarch/framework/workflow.yaml","false"
|
||||
"testarch-nfr","Assess non-functional requirements (performance, security, reliability, maintainability) before release with evidence-based validation","bmm",".bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml","false"
|
||||
"testarch-test-design","Plan risk mitigation and test coverage strategy before development with risk assessment and prioritization","bmm",".bmad/bmm/workflows/testarch/test-design/workflow.yaml","false"
|
||||
"testarch-test-review","Review test quality using comprehensive knowledge base and best practices validation","bmm",".bmad/bmm/workflows/testarch/test-review/workflow.yaml","false"
|
||||
"testarch-trace","Generate requirements-to-tests traceability matrix, analyze coverage, and make quality gate decision (PASS/CONCERNS/FAIL/WAIVED)","bmm",".bmad/bmm/workflows/testarch/trace/workflow.yaml","false"
|
||||
"workflow-init","Initialize a new BMM project by determining level, type, and creating workflow path","bmm",".bmad/bmm/workflows/workflow-status/init/workflow.yaml","true"
|
||||
"workflow-status","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.","bmm",".bmad/bmm/workflows/workflow-status/workflow.yaml","true"
|
||||
"design-thinking","Guide human-centered design processes using empathy-driven methodologies. This workflow walks through the design thinking phases - Empathize, Define, Ideate, Prototype, and Test - to create solutions deeply rooted in user needs.","cis",".bmad/cis/workflows/design-thinking/workflow.yaml","true"
|
||||
"innovation-strategy","Identify disruption opportunities and architect business model innovation. This workflow guides strategic analysis of markets, competitive dynamics, and business model innovation to uncover sustainable competitive advantages and breakthrough opportunities.","cis",".bmad/cis/workflows/innovation-strategy/workflow.yaml","true"
|
||||
"problem-solving","Apply systematic problem-solving methodologies to crack complex challenges. This workflow guides through problem diagnosis, root cause analysis, creative solution generation, evaluation, and implementation planning using proven frameworks.","cis",".bmad/cis/workflows/problem-solving/workflow.yaml","true"
|
||||
"storytelling","Craft compelling narratives using proven story frameworks and techniques. This workflow guides users through structured narrative development, applying appropriate story frameworks to create emotionally resonant and engaging stories for any purpose.","cis",".bmad/cis/workflows/storytelling/workflow.yaml","true"
|
||||
|
|
|
|||
|
|
|
@ -18,7 +18,8 @@ You must fully embody this agent's persona and follow all activation instruction
|
|||
|
||||
<step n="4">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
|
||||
ALL menu items from menu section</step>
|
||||
<step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
|
||||
<step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command
|
||||
match</step>
|
||||
<step n="6">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
|
||||
to clarify | No match → show "Not recognized"</step>
|
||||
<step n="7">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# BMB Module Configuration
|
||||
# Generated by BMAD installer
|
||||
# Version: 6.0.0-alpha.7
|
||||
# Date: 2025-11-09T05:23:00.243Z
|
||||
# Version: 6.0.0-alpha.8
|
||||
# Date: 2025-11-10T17:57:56.303Z
|
||||
|
||||
custom_agent_location: "{project-root}/.bmad/custom/agents"
|
||||
custom_workflow_location: "{project-root}/.bmad/custom/workflows"
|
||||
|
|
@ -13,4 +13,4 @@ user_name: BMad
|
|||
communication_language: English
|
||||
document_output_language: English
|
||||
output_folder: "{project-root}/docs"
|
||||
install_user_docs: false
|
||||
install_user_docs: true
|
||||
|
|
|
|||
|
|
@ -18,7 +18,8 @@ You must fully embody this agent's persona and follow all activation instruction
|
|||
|
||||
<step n="4">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
|
||||
ALL menu items from menu section</step>
|
||||
<step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
|
||||
<step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command
|
||||
match</step>
|
||||
<step n="6">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
|
||||
to clarify | No match → show "Not recognized"</step>
|
||||
<step n="7">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
|
||||
|
|
|
|||
|
|
@ -18,7 +18,8 @@ You must fully embody this agent's persona and follow all activation instruction
|
|||
|
||||
<step n="4">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
|
||||
ALL menu items from menu section</step>
|
||||
<step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
|
||||
<step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command
|
||||
match</step>
|
||||
<step n="6">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
|
||||
to clarify | No match → show "Not recognized"</step>
|
||||
<step n="7">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ You must fully embody this agent's persona and follow all activation instruction
|
|||
<activation critical="MANDATORY">
|
||||
<step n="1">Load persona from this current agent file (already in context)</step>
|
||||
<step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
|
||||
- Load and read {project-root}/bmad/bmm/config.yaml NOW
|
||||
- Load and read {project-root}/{bmad_folder}/bmm/config.yaml NOW
|
||||
- Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
|
||||
- VERIFY: If config not loaded, STOP and report error to user
|
||||
- DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
|
||||
|
|
@ -20,7 +20,8 @@ You must fully embody this agent's persona and follow all activation instruction
|
|||
<step n="6">Cross-check recommendations with the official tools and documentation when possible</step>
|
||||
<step n="7">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
|
||||
ALL menu items from menu section</step>
|
||||
<step n="8">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
|
||||
<step n="8">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command
|
||||
match</step>
|
||||
<step n="9">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
|
||||
to clarify | No match → show "Not recognized"</step>
|
||||
<step n="10">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
|
||||
|
|
@ -30,7 +31,7 @@ You must fully embody this agent's persona and follow all activation instruction
|
|||
<handlers>
|
||||
<handler type="workflow">
|
||||
When menu item has: workflow="path/to/workflow.yaml"
|
||||
1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.xml
|
||||
1. CRITICAL: Always LOAD {project-root}/{bmad_folder}/core/tasks/workflow.xml
|
||||
2. Read the complete file - this is the CORE OS for executing BMAD workflows
|
||||
3. Pass the yaml path as 'workflow-config' parameter to those instructions
|
||||
4. Execute workflow.xml instructions precisely following all steps
|
||||
|
|
|
|||
|
|
@ -22,7 +22,8 @@ You must fully embody this agent's persona and follow all activation instruction
|
|||
<step n="8">For *develop (Dev Story workflow), execute continuously without pausing for review or 'milestones'. Only halt for explicit blocker conditions (e.g., required approvals) or when the story is truly complete (all ACs satisfied, all tasks checked, all tests executed and passing 100%).</step>
|
||||
<step n="9">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
|
||||
ALL menu items from menu section</step>
|
||||
<step n="10">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
|
||||
<step n="10">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command
|
||||
match</step>
|
||||
<step n="11">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
|
||||
to clarify | No match → show "Not recognized"</step>
|
||||
<step n="12">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
|
||||
|
|
|
|||
|
|
@ -18,7 +18,8 @@ You must fully embody this agent's persona and follow all activation instruction
|
|||
|
||||
<step n="4">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
|
||||
ALL menu items from menu section</step>
|
||||
<step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
|
||||
<step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command
|
||||
match</step>
|
||||
<step n="6">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
|
||||
to clarify | No match → show "Not recognized"</step>
|
||||
<step n="7">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
|
||||
|
|
|
|||
|
|
@ -18,7 +18,8 @@ You must fully embody this agent's persona and follow all activation instruction
|
|||
<step n="4">When running *create-story, run non-interactively: use architecture, PRD, Tech Spec, and epics to generate a complete draft without elicitation.</step>
|
||||
<step n="5">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
|
||||
ALL menu items from menu section</step>
|
||||
<step n="6">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
|
||||
<step n="6">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command
|
||||
match</step>
|
||||
<step n="7">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
|
||||
to clarify | No match → show "Not recognized"</step>
|
||||
<step n="8">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
|
||||
|
|
|
|||
|
|
@ -20,7 +20,8 @@ You must fully embody this agent's persona and follow all activation instruction
|
|||
<step n="6">Cross-check recommendations with the current official Playwright, Cypress, Pact, and CI platform documentation; fall back to {project-root}/.bmad/bmm/testarch/test-resources-for-ai-flat.txt only when deeper sourcing is required</step>
|
||||
<step n="7">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
|
||||
ALL menu items from menu section</step>
|
||||
<step n="8">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
|
||||
<step n="8">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command
|
||||
match</step>
|
||||
<step n="9">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
|
||||
to clarify | No match → show "Not recognized"</step>
|
||||
<step n="10">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
|
||||
|
|
|
|||
|
|
@ -24,7 +24,8 @@ You must fully embody this agent's persona and follow all activation instruction
|
|||
<step n="10">CRITICAL: All Mermaid diagrams MUST use valid syntax - mentally validate before outputting</step>
|
||||
<step n="11">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
|
||||
ALL menu items from menu section</step>
|
||||
<step n="12">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
|
||||
<step n="12">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command
|
||||
match</step>
|
||||
<step n="13">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
|
||||
to clarify | No match → show "Not recognized"</step>
|
||||
<step n="14">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
|
||||
|
|
|
|||
|
|
@ -18,7 +18,8 @@ You must fully embody this agent's persona and follow all activation instruction
|
|||
|
||||
<step n="4">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
|
||||
ALL menu items from menu section</step>
|
||||
<step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
|
||||
<step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command
|
||||
match</step>
|
||||
<step n="6">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
|
||||
to clarify | No match → show "Not recognized"</step>
|
||||
<step n="7">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# BMM Module Configuration
|
||||
# Generated by BMAD installer
|
||||
# Version: 6.0.0-alpha.7
|
||||
# Date: 2025-11-09T05:23:00.244Z
|
||||
# Version: 6.0.0-alpha.8
|
||||
# Date: 2025-11-10T17:57:56.304Z
|
||||
|
||||
project_name: BMAD-METHOD
|
||||
user_skill_level: intermediate
|
||||
|
|
@ -15,4 +15,4 @@ user_name: BMad
|
|||
communication_language: English
|
||||
document_output_language: English
|
||||
output_folder: "{project-root}/docs"
|
||||
install_user_docs: false
|
||||
install_user_docs: true
|
||||
|
|
|
|||
|
|
@ -299,7 +299,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
|
|||
|
||||
**Special Capabilities:**
|
||||
|
||||
- **Knowledge Base Access:** Consults comprehensive testing best practices from `testarch/knowledge/` directory
|
||||
- **Knowledge Base Access:** Consults comprehensive testing best practices from `knowledge/tea/` directory
|
||||
- **Framework Selection:** Smart framework selection (Playwright vs Cypress) with fixture architecture
|
||||
- **Cross-Platform Testing:** Supports testing across web, mobile, and API layers
|
||||
|
||||
|
|
|
|||
|
|
@ -16,38 +16,37 @@
|
|||
|
||||
<critical>DOCUMENT OUTPUT: Technical review reports. Structured findings with severity levels and action items. User skill level ({user_skill_level}) affects conversation style ONLY, not review content.</critical>
|
||||
|
||||
## 📚 Document Discovery - Selective Epic Loading
|
||||
|
||||
**Strategy**: This workflow needs only ONE specific epic and its stories for review context, not all epics. This provides huge efficiency gains when epics are sharded.
|
||||
|
||||
**Epic Discovery Process (SELECTIVE OPTIMIZATION):**
|
||||
|
||||
1. **Determine which epic** you need (epic_num from story being reviewed - e.g., story "3-2-feature-name" needs Epic 3)
|
||||
2. **Check for sharded version**: Look for `epics/index.md`
|
||||
3. **If sharded version found**:
|
||||
- Read `index.md` to understand structure
|
||||
- **Load ONLY `epic-{epic_num}.md`** (e.g., `epics/epic-3.md` for Epic 3)
|
||||
- DO NOT load all epic files - only the one needed!
|
||||
- This is the key efficiency optimization for large multi-epic projects
|
||||
4. **If whole document found**: Load the complete `epics.md` file and extract the relevant epic
|
||||
|
||||
**Other Documents (architecture, ux-design) - Full Load:**
|
||||
|
||||
1. **Search for whole document first** - Use fuzzy file matching
|
||||
2. **Check for sharded version** - If whole document not found, look for `{doc-name}/index.md`
|
||||
3. **If sharded version found**:
|
||||
- Read `index.md` to understand structure
|
||||
- Read ALL section files listed in the index
|
||||
- Treat combined content as single document
|
||||
4. **Brownfield projects**: The `document-project` workflow creates `{output_folder}/docs/index.md`
|
||||
|
||||
**Priority**: If both whole and sharded versions exist, use the whole document.
|
||||
|
||||
**UX-Heavy Projects**: Always check for ux-design documentation as it provides critical context for reviewing UI-focused stories.
|
||||
|
||||
<workflow>
|
||||
|
||||
<step n="1" goal="Find story ready for review" tag="sprint-status">
|
||||
Document Discovery - Selective Epic Loading
|
||||
|
||||
**Strategy**: This workflow needs only ONE specific epic and its stories for review context, not all epics. This provides huge efficiency gains when epics are sharded.
|
||||
|
||||
**Epic Discovery Process (SELECTIVE OPTIMIZATION):**
|
||||
|
||||
1. **Determine which epic** you need (epic_num from story being reviewed - e.g., story "3-2-feature-name" needs Epic 3)
|
||||
2. **Check for sharded version**: Look for `epics/index.md`
|
||||
3. **If sharded version found**:
|
||||
- Read `index.md` to understand structure
|
||||
- **Load ONLY `epic-{epic_num}.md`** (e.g., `epics/epic-3.md` for Epic 3)
|
||||
- DO NOT load all epic files - only the one needed!
|
||||
- This is the key efficiency optimization for large multi-epic projects
|
||||
4. **If whole document found**: Load the complete `epics.md` file and extract the relevant epic
|
||||
|
||||
**Other Documents (architecture, ux-design) - Full Load:**
|
||||
|
||||
1. **Search for whole document first** - Use fuzzy file matching
|
||||
2. **Check for sharded version** - If whole document not found, look for `{doc-name}/index.md`
|
||||
3. **If sharded version found**:
|
||||
- Read `index.md` to understand structure
|
||||
- Read ALL section files listed in the index
|
||||
- Treat combined content as single document
|
||||
4. **Brownfield projects**: The `document-project` workflow creates `{output_folder}/docs/index.md`
|
||||
|
||||
**Priority**: If both whole and sharded versions exist, use the whole document.
|
||||
|
||||
**UX-Heavy Projects**: Always check for ux-design documentation as it provides critical context for reviewing UI-focused stories.
|
||||
<check if="{{story_path}} is provided">
|
||||
<action>Use {{story_path}} directly</action>
|
||||
<action>Read COMPLETE story file and parse sections</action>
|
||||
|
|
@ -80,17 +79,18 @@
|
|||
<check if="option 3 selected">
|
||||
<ask>What code would you like me to review?
|
||||
|
||||
Provide:
|
||||
- File path(s) or directory to review
|
||||
- What to review for:
|
||||
• General quality and standards
|
||||
• Requirements compliance
|
||||
• Security concerns
|
||||
• Performance issues
|
||||
• Architecture alignment
|
||||
• Something else (specify)
|
||||
Provide:
|
||||
- File path(s) or directory to review
|
||||
- What to review for:
|
||||
• General quality and standards
|
||||
• Requirements compliance
|
||||
• Security concerns
|
||||
• Performance issues
|
||||
• Architecture alignment
|
||||
• Something else (specify)
|
||||
|
||||
Your input:</ask>
|
||||
Your input:?
|
||||
</ask>
|
||||
|
||||
<action>Parse user input to extract:
|
||||
- {{review_files}}: file paths or directories to review
|
||||
|
|
@ -363,11 +363,11 @@ Review was saved to story file, but sprint-status.yaml may be out of sync.
|
|||
<action if="user confirms or no ask needed">
|
||||
Append under the story's "Tasks / Subtasks" a new subsection titled "Review Follow-ups (AI)", adding each item as an unchecked checkbox in imperative form, prefixed with "[AI-Review]" and severity. Example: "- [ ] [AI-Review][High] Add input validation on server route /api/x (AC #2)".
|
||||
</action>
|
||||
<action if="{{persist_action_items}} == true and 'backlog_file' in {{persist_targets}}">
|
||||
<action>
|
||||
If {{backlog_file}} does not exist, copy {installed_path}/backlog_template.md to {{backlog_file}} location.
|
||||
Append a row per action item with Date={{date}}, Story={{epic_num}}.{{story_num}}, Epic={{epic_num}}, Type, Severity, Owner (or "TBD"), Status="Open", Notes with short context and file refs.
|
||||
</action>
|
||||
<action if="{{persist_action_items}} == true and ('epic_followups' in {{persist_targets}} or {{update_epic_followups}} == true)">
|
||||
<action>
|
||||
If an epic Tech Spec was found: open it and create (if missing) a section titled "{{epic_followups_section_title}}". Append a bullet list of action items scoped to this epic with references back to Story {{epic_num}}.{{story_num}}.
|
||||
</action>
|
||||
<action>Save modified files.</action>
|
||||
|
|
|
|||
|
|
@ -11,6 +11,8 @@ communication_language: "{config_source}:communication_language"
|
|||
user_skill_level: "{config_source}:user_skill_level"
|
||||
document_output_language: "{config_source}:document_output_language"
|
||||
date: system-generated
|
||||
ephemeral_files: "{config_source}:dev_ephemeral_location"
|
||||
sprint_status: "{context_dir}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
|
||||
|
||||
# Workflow components
|
||||
installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/code-review"
|
||||
|
|
@ -22,8 +24,8 @@ template: false
|
|||
|
||||
# Variables (can be provided by caller)
|
||||
variables:
|
||||
story_path: "" # Optional: Explicit path to story file. If not provided, finds first story with status "review"
|
||||
story_dir: "{config_source}:dev_ephemeral_location" # Directory containing story files
|
||||
story_path: "{ephemeral_files}/stories" # Optional: Explicit path to story file. If not provided, finds first story with status "review"
|
||||
story_dir: "{ephemeral_files}/stories" # Directory containing story files
|
||||
tech_spec_search_dir: "{project-root}/docs"
|
||||
tech_spec_glob_template: "tech-spec-epic-{{epic_num}}*.md"
|
||||
arch_docs_search_dirs: |
|
||||
|
|
@ -31,17 +33,10 @@ variables:
|
|||
- "{output_folder}"
|
||||
arch_docs_file_names: |
|
||||
- architecture.md
|
||||
|
||||
backlog_file: "{project-root}/docs/backlog.md"
|
||||
update_epic_followups: true
|
||||
epic_followups_section_title: "Post-Review Follow-ups"
|
||||
|
||||
# Recommended inputs
|
||||
recommended_inputs:
|
||||
- story: "Path to the story file (auto-discovered if omitted - finds first story with status 'review')"
|
||||
- tech_spec: "Epic technical specification document (auto-discovered)"
|
||||
- story_context_file: "Story context file (.context.xml) (auto-discovered)"
|
||||
|
||||
# Smart input file references - handles both whole docs and sharded docs
|
||||
# Priority: Whole document first, then sharded version
|
||||
# Strategy: SELECTIVE LOAD - only load the specific epic needed for this story review
|
||||
|
|
@ -49,16 +44,13 @@ input_file_patterns:
|
|||
architecture:
|
||||
whole: "{output_folder}/*architecture*.md"
|
||||
sharded: "{output_folder}/*architecture*/index.md"
|
||||
|
||||
ux_design:
|
||||
whole: "{output_folder}/*ux*.md"
|
||||
sharded: "{output_folder}/*ux*/index.md"
|
||||
|
||||
epics:
|
||||
whole: "{output_folder}/*epic*.md"
|
||||
sharded_index: "{output_folder}/*epic*/index.md"
|
||||
sharded_single: "{output_folder}/*epic*/epic-{{epic_num}}.md"
|
||||
|
||||
document_project:
|
||||
sharded: "{output_folder}/docs/index.md"
|
||||
|
||||
|
|
|
|||
|
|
@ -7,45 +7,46 @@
|
|||
<critical>This workflow creates or updates the next user story from epics/PRD and architecture context, saving to the configured stories directory and optionally invoking Story Context.</critical>
|
||||
<critical>DOCUMENT OUTPUT: Concise, technical, actionable story specifications. Use tables/lists for acceptance criteria and tasks.</critical>
|
||||
|
||||
## 📚 Document Discovery - Selective Epic Loading
|
||||
|
||||
**Strategy**: This workflow needs only ONE specific epic and its stories, not all epics. This provides huge efficiency gains when epics are sharded.
|
||||
|
||||
**Epic Discovery Process (SELECTIVE OPTIMIZATION):**
|
||||
|
||||
1. **Determine which epic** you need (epic_num from story context - e.g., story "3-2-feature-name" needs Epic 3)
|
||||
2. **Check for sharded version**: Look for `epics/index.md`
|
||||
3. **If sharded version found**:
|
||||
- Read `index.md` to understand structure
|
||||
- **Load ONLY `epic-{epic_num}.md`** (e.g., `epics/epic-3.md` for Epic 3)
|
||||
- DO NOT load all epic files - only the one needed!
|
||||
- This is the key efficiency optimization for large multi-epic projects
|
||||
4. **If whole document found**: Load the complete `epics.md` file and extract the relevant epic
|
||||
|
||||
**Other Documents (prd, architecture, ux-design) - Full Load:**
|
||||
|
||||
1. **Search for whole document first** - Use fuzzy file matching
|
||||
2. **Check for sharded version** - If whole document not found, look for `{doc-name}/index.md`
|
||||
3. **If sharded version found**:
|
||||
- Read `index.md` to understand structure
|
||||
- Read ALL section files listed in the index
|
||||
- Treat combined content as single document
|
||||
4. **Brownfield projects**: The `document-project` workflow creates `{output_folder}/docs/index.md`
|
||||
|
||||
**Priority**: If both whole and sharded versions exist, use the whole document.
|
||||
|
||||
**UX-Heavy Projects**: Always check for ux-design documentation as it provides critical context for UI-focused stories.
|
||||
|
||||
<workflow>
|
||||
|
||||
<step n="1" goal="Load config and initialize">
|
||||
<action>Resolve variables from config_source: story_dir (dev_ephemeral_location), output_folder, user_name, communication_language. If story_dir missing and {{non_interactive}} == false → ASK user to provide a stories directory and update variable. If {{non_interactive}} == true and missing, HALT with a clear message.</action>
|
||||
<action>Resolve variables from config_source: story_dir (dev_ephemeral_location), output_folder, user_name, communication_language. If story_dir missing → ASK user to provide a stories directory and update variable.</action>
|
||||
<action>Create {{story_dir}} if it does not exist</action>
|
||||
<action>Resolve installed component paths from workflow.yaml: template, instructions, validation</action>
|
||||
<action>Resolve recommended inputs if present: epics_file, prd_file, architecture_file</action>
|
||||
</step>
|
||||
|
||||
<step n="2" goal="Discover and load source documents">
|
||||
<action>
|
||||
Selective Epic Loading
|
||||
|
||||
**Strategy**: This workflow needs only ONE specific epic and its stories, not all epics. This provides huge efficiency gains when epics are sharded.
|
||||
|
||||
**Epic Discovery Process (SELECTIVE OPTIMIZATION):**
|
||||
|
||||
1. **Determine which epic** you need (epic_num from story context - e.g., story "3-2-feature-name" needs Epic 3)
|
||||
2. **Check for sharded version**: Look for `epics/*n*.md` where n is the epic number such as epics/epic-3-foo.md
|
||||
3. **If sharded version found**:
|
||||
- Read `index.md` to understand structure
|
||||
- **Load ONLY `epic-{epic_num}.md`** (e.g., `epics/epic-3.md` for Epic 3)
|
||||
- DO NOT load all epic files - only the one needed!
|
||||
- This is the key efficiency optimization for large multi-epic projects
|
||||
4. **If whole document found**: Load the complete `epics.md` file and extract the relevant epic
|
||||
|
||||
**Other Documents (prd, architecture, ux-design) - Full Load:**
|
||||
|
||||
1. **Search for whole document first** - Use fuzzy file matching
|
||||
2. **Check for sharded version** - If whole document not found, look for `{doc-name}/index.md`
|
||||
3. **If sharded version found**:
|
||||
- Read `index.md` to understand structure
|
||||
- Read ALL section files listed in the index
|
||||
- Treat combined content as single document
|
||||
4. **Brownfield projects**: The `document-project` workflow creates `{output_folder}/docs/index.md`
|
||||
|
||||
**Priority**: If both whole and sharded versions exist, use the whole document.
|
||||
|
||||
**UX-Heavy Projects**: Always check for ux-design documentation as it provides critical context for UI-focused stories.
|
||||
</action>
|
||||
<critical>PREVIOUS STORY CONTINUITY: Essential for maintaining context and learning from prior development</critical>
|
||||
|
||||
<action>Find the previous completed story to extract dev agent learnings and review findings:
|
||||
|
|
@ -115,19 +116,17 @@
|
|||
</action>
|
||||
|
||||
<action>If {{tech_spec_file}} empty: derive from {{tech_spec_glob_template}} with {{epic_num}} and search {{tech_spec_search_dir}} recursively. If multiple, pick most recent by modified time.</action>
|
||||
<action>Build a prioritized document set for this epic:
|
||||
<action>Build a prioritized document set for this epic - search and load from {input_file_patterns} list of potential locations:
|
||||
1) tech_spec_file (epic-scoped)
|
||||
2) epics_file (acceptance criteria and breakdown)
|
||||
3) prd_file (business requirements and constraints)
|
||||
4) architecture_file (architecture constraints)
|
||||
5) Architecture docs under docs/ and output_folder/: tech-stack.md, unified-project-structure.md, coding-standards.md, testing-strategy.md, backend-architecture.md, frontend-architecture.md, data-models.md, database-schema.md, rest-api-spec.md, external-apis.md (include if present)
|
||||
2) epics_file (acceptance criteria and breakdown) the specific epic the story will be part of
|
||||
3) prd_file (business requirements and constraints) whole or sharded
|
||||
4) architecture_file (architecture constraints) whole or sharded
|
||||
</action>
|
||||
<action>READ COMPLETE FILES for all items found in the prioritized set. Store content and paths for citation.</action>
|
||||
</step>
|
||||
|
||||
<step n="3" goal="Find next backlog story to draft" tag="sprint-status">
|
||||
<critical>MUST read COMPLETE sprint-status.yaml file from start to end to preserve order</critical>
|
||||
<action>Load the FULL file: {{output_folder}}/sprint-status.yaml</action>
|
||||
<critical>MUST read COMPLETE {sprint_status} file from start to end to preserve order</critical>
|
||||
<action>Read ALL lines from beginning to end - do not skip any content</action>
|
||||
<action>Parse the development_status section completely to understand story order</action>
|
||||
|
||||
|
|
@ -164,7 +163,6 @@ All stories are either already drafted or completed.
|
|||
<action>Check if story file already exists at expected path in {{story_dir}}</action>
|
||||
<check if="story file exists">
|
||||
<output>ℹ️ Story file already exists: {{story_file_path}}
|
||||
|
||||
Will update existing story file rather than creating new one.
|
||||
</output>
|
||||
<action>Set update_mode = true</action>
|
||||
|
|
|
|||
|
|
@ -8,6 +8,7 @@ output_folder: "{config_source}:output_folder"
|
|||
user_name: "{config_source}:user_name"
|
||||
communication_language: "{config_source}:communication_language"
|
||||
date: system-generated
|
||||
story_dir: "{config_source}:dev_ephemeral_location/stories"
|
||||
|
||||
# Workflow components
|
||||
installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/create-story"
|
||||
|
|
@ -17,7 +18,7 @@ validation: "{installed_path}/checklist.md"
|
|||
|
||||
# Variables and inputs
|
||||
variables:
|
||||
story_dir: "{config_source}:dev_ephemeral_location" # Directory where stories are stored
|
||||
sprint_status: "{config_source}:dev_ephemeral_location/sprint-status.yaml || {output_folder}/sprint-status.yaml" # Primary source for story tracking
|
||||
epics_file: "{output_folder}/epics.md" # Preferred source for epic/story breakdown
|
||||
prd_file: "{output_folder}/PRD.md" # Fallback for requirements
|
||||
architecture_file: "{output_folder}/architecture.md" # Optional architecture context
|
||||
|
|
@ -28,22 +29,13 @@ variables:
|
|||
- "{project-root}/docs"
|
||||
- "{output_folder}"
|
||||
arch_docs_file_names: |
|
||||
- architecture.md
|
||||
- infrastructure-architecture.md
|
||||
- *architecture*.md
|
||||
story_title: "" # Will be elicited if not derivable
|
||||
epic_num: 1
|
||||
story_num: 1
|
||||
non_interactive: true # Generate without elicitation; avoid interactive prompts
|
||||
|
||||
# Output configuration
|
||||
# Uses story_key from sprint-status.yaml (e.g., "1-2-user-authentication")
|
||||
default_output_file: "{story_dir}/{{story_key}}.md"
|
||||
|
||||
recommended_inputs:
|
||||
- epics: "Epic breakdown (epics.md)"
|
||||
- prd: "PRD document"
|
||||
- architecture: "Architecture (optional)"
|
||||
|
||||
# Smart input file references - handles both whole docs and sharded docs
|
||||
# Priority: Whole document first, then sharded version
|
||||
# Strategy: SELECTIVE LOAD - only load the specific epic needed for this story
|
||||
|
|
@ -51,24 +43,19 @@ input_file_patterns:
|
|||
prd:
|
||||
whole: "{output_folder}/*prd*.md"
|
||||
sharded: "{output_folder}/*prd*/index.md"
|
||||
|
||||
tech_spec:
|
||||
whole: "{output_folder}/tech-spec.md"
|
||||
|
||||
architecture:
|
||||
whole: "{output_folder}/*architecture*.md"
|
||||
sharded: "{output_folder}/*architecture*/index.md"
|
||||
|
||||
ux_design:
|
||||
whole: "{output_folder}/*ux*.md"
|
||||
sharded: "{output_folder}/*ux*/index.md"
|
||||
|
||||
epics:
|
||||
whole: "{output_folder}/*epic*.md"
|
||||
sharded_index: "{output_folder}/*epic*/index.md"
|
||||
sharded_single: "{output_folder}/*epic*/epic-{{epic_num}}.md"
|
||||
|
||||
document_project:
|
||||
sharded: "{output_folder}/docs/index.md"
|
||||
sharded: "{output_folder}/index.md"
|
||||
|
||||
standalone: true
|
||||
|
|
|
|||
|
|
@ -7,43 +7,41 @@
|
|||
<critical>This workflow generates a comprehensive Technical Specification from PRD and Architecture, including detailed design, NFRs, acceptance criteria, and traceability mapping.</critical>
|
||||
<critical>If required inputs cannot be auto-discovered HALT with a clear message listing missing documents, allow user to provide them to proceed.</critical>
|
||||
|
||||
## 📚 Document Discovery - Selective Epic Loading
|
||||
|
||||
**Strategy**: This workflow needs only ONE specific epic and its stories, not all epics. This provides huge efficiency gains when epics are sharded.
|
||||
|
||||
**Epic Discovery Process (SELECTIVE OPTIMIZATION):**
|
||||
|
||||
1. **Determine which epic** you need (epic_num from workflow context or user input)
|
||||
2. **Check for sharded version**: Look for `epics/index.md`
|
||||
3. **If sharded version found**:
|
||||
- Read `index.md` to understand structure
|
||||
- **Load ONLY `epic-{epic_num}.md`** (e.g., `epics/epic-3.md` for Epic 3)
|
||||
- DO NOT load all epic files - only the one needed!
|
||||
- This is the key efficiency optimization for large multi-epic projects
|
||||
4. **If whole document found**: Load the complete `epics.md` file and extract the relevant epic
|
||||
|
||||
**Other Documents (prd, gdd, architecture, ux-design) - Full Load:**
|
||||
|
||||
1. **Search for whole document first** - Use fuzzy file matching
|
||||
2. **Check for sharded version** - If whole document not found, look for `{doc-name}/index.md`
|
||||
3. **If sharded version found**:
|
||||
- Read `index.md` to understand structure
|
||||
- Read ALL section files listed in the index
|
||||
- Treat combined content as single document
|
||||
4. **Brownfield projects**: The `document-project` workflow creates `{output_folder}/docs/index.md`
|
||||
|
||||
**Priority**: If both whole and sharded versions exist, use the whole document.
|
||||
|
||||
**UX-Heavy Projects**: Always check for ux-design documentation as it provides critical context for UI-focused epics and stories.
|
||||
|
||||
<workflow>
|
||||
<step n="1" goal="Collect inputs and discover next epic" tag="sprint-status">
|
||||
Document Discovery - Selective Epic Loading
|
||||
|
||||
**Strategy**: This workflow needs only ONE specific epic and its stories, not all epics. This provides huge efficiency gains when epics are sharded.
|
||||
|
||||
**Epic Discovery Process (SELECTIVE OPTIMIZATION):**
|
||||
|
||||
1. **Determine which epic** you need (epic_num from workflow context or user input)
|
||||
2. **Check for sharded version**: Look for `epics/index.md`
|
||||
3. **If sharded version found**:
|
||||
- Read `index.md` to understand structure
|
||||
- **Load ONLY `epic-{epic_num}.md`** (e.g., `epics/epic-3.md` for Epic 3)
|
||||
- DO NOT load all epic files - only the one needed!
|
||||
- This is the key efficiency optimization for large multi-epic projects
|
||||
4. **If whole document found**: Load the complete `epics.md` file and extract the relevant epic
|
||||
|
||||
**Other Documents (prd, gdd, architecture, ux-design) - Full Load:**
|
||||
|
||||
1. **Search for whole document first** - Use fuzzy file matching
|
||||
2. **Check for sharded version** - If whole document not found, look for `{doc-name}/index.md`
|
||||
3. **If sharded version found**:
|
||||
- Read `index.md` to understand structure
|
||||
- Read ALL section files listed in the index
|
||||
- Treat combined content as single document
|
||||
4. **Brownfield projects**: The `document-project` workflow creates `{output_folder}/docs/index.md`
|
||||
|
||||
**Priority**: If both whole and sharded versions exist, use the whole document.
|
||||
|
||||
**UX-Heavy Projects**: Always check for ux-design documentation as it provides critical context for UI-focused epics and stories.
|
||||
<action>Identify PRD and Architecture documents from recommended_inputs. Attempt to auto-discover at default paths.</action>
|
||||
<ask if="inputs are missing">ask the user for file paths. HALT and wait for docs to proceed</ask>
|
||||
|
||||
<!-- Intelligent Epic Discovery -->
|
||||
<critical>MUST read COMPLETE sprint-status.yaml file to discover next epic</critical>
|
||||
<action>Load the FULL file: {{output_folder}}/sprint-status.yaml</action>
|
||||
<critical>MUST read COMPLETE {sprint-status} file to discover next epic</critical>
|
||||
<action>Read ALL development_status entries</action>
|
||||
<action>Find all epics with status "backlog" (not yet contexted)</action>
|
||||
<action>Identify the FIRST backlog epic as the suggested default</action>
|
||||
|
|
|
|||
|
|
@ -8,15 +8,8 @@ output_folder: "{config_source}:output_folder"
|
|||
user_name: "{config_source}:user_name"
|
||||
communication_language: "{config_source}:communication_language"
|
||||
date: system-generated
|
||||
|
||||
# Inputs expected (check output_folder or ask user if missing)
|
||||
recommended_inputs:
|
||||
- prd
|
||||
- gdd
|
||||
- architecture
|
||||
- ux_design
|
||||
- epics (only the specific epic needed for this tech spec)
|
||||
- prior epic tech-specs for model, style and consistency reference
|
||||
context_dir: "{config_source}:dev_ephemeral_location/stories"
|
||||
sprint_status: "{context_dir}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
|
||||
|
||||
# Smart input file references - handles both whole docs and sharded docs
|
||||
# Priority: Whole document first, then sharded version
|
||||
|
|
@ -25,26 +18,21 @@ input_file_patterns:
|
|||
prd:
|
||||
whole: "{output_folder}/*prd*.md"
|
||||
sharded: "{output_folder}/*prd*/index.md"
|
||||
|
||||
gdd:
|
||||
whole: "{output_folder}/*gdd*.md"
|
||||
sharded: "{output_folder}/*gdd*/index.md"
|
||||
|
||||
architecture:
|
||||
whole: "{output_folder}/*architecture*.md"
|
||||
sharded: "{output_folder}/*architecture*/index.md"
|
||||
|
||||
ux_design:
|
||||
whole: "{output_folder}/*ux*.md"
|
||||
sharded: "{output_folder}/*ux*/index.md"
|
||||
|
||||
epics:
|
||||
whole: "{output_folder}/*epic*.md"
|
||||
sharded_index: "{output_folder}/*epic*/index.md"
|
||||
sharded_single: "{output_folder}/*epic*/epic-{{epic_num}}.md"
|
||||
|
||||
document_project:
|
||||
sharded: "{output_folder}/docs/index.md"
|
||||
sharded: "{output_folder}/index.md"
|
||||
|
||||
# Workflow components
|
||||
installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/epic-tech-context"
|
||||
|
|
@ -53,6 +41,6 @@ instructions: "{installed_path}/instructions.md"
|
|||
validation: "{installed_path}/checklist.md"
|
||||
|
||||
# Output configuration
|
||||
default_output_file: "{output_folder}/tech-spec-epic-{{epic_id}}.md"
|
||||
default_output_file: "{context_dir}/tech-spec-epic-{{epic_id}}.md"
|
||||
|
||||
standalone: true
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ PARTY MODE PROTOCOL:
|
|||
|
||||
**Epic Discovery (SELECTIVE LOAD):**
|
||||
|
||||
1. Determine completed epic number (from sprint-status or user)
|
||||
1. Determine completed epic number (from {sprint_status_file} or user)
|
||||
2. If sharded: Load ONLY `epic-{epic_num}.md`
|
||||
3. If whole: Load complete epics file and extract relevant epic
|
||||
|
||||
|
|
@ -59,7 +59,7 @@ PARTY MODE PROTOCOL:
|
|||
Bob (Scrum Master): "Welcome to the retrospective, {user_name}. Let me help you identify which epic we just completed. I'll check sprint-status first, but you're the ultimate authority on what we're reviewing today."
|
||||
</output>
|
||||
|
||||
<action>PRIORITY 1: Check sprint-status.yaml first</action>
|
||||
<action>PRIORITY 1: Check {sprint_status_file} first</action>
|
||||
|
||||
<action>Load the FULL file: {sprint_status_file}</action>
|
||||
<action>Read ALL development_status entries</action>
|
||||
|
|
@ -71,7 +71,7 @@ Bob (Scrum Master): "Welcome to the retrospective, {user_name}. Let me help you
|
|||
<action>Present finding to user with context</action>
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "Based on sprint-status.yaml, it looks like Epic {{detected_epic}} was recently completed. Is that the epic you want to review today, {user_name}?"
|
||||
Bob (Scrum Master): "Based on {sprint_status_file}, it looks like Epic {{detected_epic}} was recently completed. Is that the epic you want to review today, {user_name}?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} to confirm or correct</action>
|
||||
|
|
@ -92,7 +92,7 @@ Bob (Scrum Master): "Got it, we're reviewing Epic {{epic_number}}. Let me gather
|
|||
<action>PRIORITY 2: Ask user directly</action>
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "I'm having trouble detecting the completed epic from sprint-status.yaml. {user_name}, which epic number did you just complete?"
|
||||
Bob (Scrum Master): "I'm having trouble detecting the completed epic from {sprint_status_file}. {user_name}, which epic number did you just complete?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} to provide epic number</action>
|
||||
|
|
@ -116,7 +116,7 @@ Bob (Scrum Master): "I found stories for Epic {{detected_epic}} in the stories f
|
|||
|
||||
<action>Once {{epic_number}} is determined, verify epic completion status</action>
|
||||
|
||||
<action>Find all stories for epic {{epic_number}} in sprint-status.yaml:
|
||||
<action>Find all stories for epic {{epic_number}} in {sprint_status_file}:
|
||||
|
||||
- Look for keys starting with "{{epic_number}}-" (e.g., "1-1-", "1-2-", etc.)
|
||||
- Exclude epic key itself ("epic-{{epic_number}}")
|
||||
|
|
@ -1346,7 +1346,7 @@ Bob (Scrum Master): "See you all when prep work is done. Meeting adjourned!"
|
|||
✅ Retrospective document saved: {retrospectives_folder}/epic-{{epic_number}}-retro-{date}.md
|
||||
</output>
|
||||
|
||||
<action>Update sprint-status.yaml to mark retrospective as completed</action>
|
||||
<action>Update {sprint_status_file} to mark retrospective as completed</action>
|
||||
|
||||
<action>Load the FULL file: {sprint_status_file}</action>
|
||||
<action>Find development_status key "epic-{{epic_number}}-retrospective"</action>
|
||||
|
|
@ -1356,7 +1356,7 @@ Bob (Scrum Master): "See you all when prep work is done. Meeting adjourned!"
|
|||
|
||||
<check if="update successful">
|
||||
<output>
|
||||
✅ Retrospective marked as completed in sprint-status.yaml
|
||||
✅ Retrospective marked as completed in {sprint_status_file}
|
||||
|
||||
Retrospective key: epic-{{epic_number}}-retrospective
|
||||
Status: {{previous_status}} → done
|
||||
|
|
@ -1365,9 +1365,9 @@ Status: {{previous_status}} → done
|
|||
|
||||
<check if="retrospective key not found">
|
||||
<output>
|
||||
⚠️ Could not update retrospective status: epic-{{epic_number}}-retrospective not found in sprint-status.yaml
|
||||
⚠️ Could not update retrospective status: epic-{{epic_number}}-retrospective not found in {sprint_status_file}
|
||||
|
||||
Retrospective document was saved successfully, but sprint-status.yaml may need manual update.
|
||||
Retrospective document was saved successfully, but {sprint_status_file} may need manual update.
|
||||
</output>
|
||||
</check>
|
||||
|
||||
|
|
|
|||
|
|
@ -10,6 +10,7 @@ communication_language: "{config_source}:communication_language"
|
|||
user_skill_level: "{config_source}:user_skill_level"
|
||||
document_output_language: "{config_source}:document_output_language"
|
||||
date: system-generated
|
||||
ephemeral_files: "{config_source}:dev_ephemeral_location"
|
||||
|
||||
installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/retrospective"
|
||||
template: false
|
||||
|
|
@ -29,25 +30,21 @@ input_file_patterns:
|
|||
whole: "{output_folder}/*epic*.md"
|
||||
sharded_index: "{output_folder}/*epic*/index.md"
|
||||
sharded_single: "{output_folder}/*epic*/epic-{{epic_num}}.md"
|
||||
|
||||
previous_retrospective:
|
||||
pattern: "{output_folder}/retrospectives/epic-{{prev_epic_num}}-retro-*.md"
|
||||
|
||||
pattern: "{ephemeral_files}/retrospectives/epic-{{prev_epic_num}}-retro-*.md"
|
||||
architecture:
|
||||
whole: "{output_folder}/*architecture*.md"
|
||||
sharded: "{output_folder}/*architecture*/index.md"
|
||||
|
||||
prd:
|
||||
whole: "{output_folder}/*prd*.md"
|
||||
sharded: "{output_folder}/*prd*/index.md"
|
||||
|
||||
document_project:
|
||||
sharded: "{output_folder}/docs/index.md"
|
||||
|
||||
# Required files
|
||||
sprint_status_file: "{output_folder}/sprint-status.yaml"
|
||||
story_directory: "{config_source}:dev_ephemeral_location"
|
||||
retrospectives_folder: "{output_folder}/retrospectives"
|
||||
sprint_status_file: "{context_dir}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
|
||||
story_directory: "{ephemeral_files}/stories"
|
||||
retrospectives_folder: "{ephemeral_files}/retrospectives"
|
||||
|
||||
output_artifacts:
|
||||
- retrospective_summary: "Comprehensive review of what went well and what could improve"
|
||||
|
|
|
|||
|
|
@ -141,8 +141,6 @@ development_status:
|
|||
```
|
||||
|
||||
<action>Write the complete sprint status YAML to {status_file}</action>
|
||||
<action>CRITICAL: For story_location field, write the variable value EXACTLY as defined in workflow.yaml: "{project-root}/docs/stories"</action>
|
||||
<action>CRITICAL: Do NOT resolve {project-root} to an absolute path - keep it as the literal string "{project-root}/docs/stories"</action>
|
||||
<action>CRITICAL: Metadata appears TWICE - once as comments (#) for documentation, once as YAML key:value fields for parsing</action>
|
||||
<action>Ensure all items are ordered: epic, its stories, its retrospective, next epic...</action>
|
||||
</step>
|
||||
|
|
@ -150,10 +148,10 @@ development_status:
|
|||
<step n="5" goal="Validate and report">
|
||||
<action>Perform validation checks:</action>
|
||||
|
||||
- [ ] Every epic in epic files appears in sprint-status.yaml
|
||||
- [ ] Every story in epic files appears in sprint-status.yaml
|
||||
- [ ] Every epic in epic files appears in {status_file}
|
||||
- [ ] Every story in epic files appears in {status_file}
|
||||
- [ ] Every epic has a corresponding retrospective entry
|
||||
- [ ] No items in sprint-status.yaml that don't exist in epic files
|
||||
- [ ] No items in {status_file} that don't exist in epic files
|
||||
- [ ] All status values are legal (match state machine definitions)
|
||||
- [ ] File is valid YAML syntax
|
||||
|
||||
|
|
@ -178,7 +176,7 @@ development_status:
|
|||
|
||||
**Next Steps:**
|
||||
|
||||
1. Review the generated sprint-status.yaml
|
||||
1. Review the generated {status_file}
|
||||
2. Use this file to track development progress
|
||||
3. Agents will update statuses as they work
|
||||
4. Re-run this workflow to refresh auto-detected statuses
|
||||
|
|
@ -229,10 +227,3 @@ optional ↔ completed
|
|||
3. **Parallel Work Supported**: Multiple stories can be `in-progress` if team capacity allows
|
||||
4. **Review Before Done**: Stories should pass through `review` before `done`
|
||||
5. **Learning Transfer**: SM typically drafts next story after previous one is `done` to incorporate learnings
|
||||
|
||||
### Error Handling
|
||||
|
||||
- If epic file can't be parsed, report specific file and continue with others
|
||||
- If existing status file is malformed, backup and regenerate
|
||||
- Log warnings for duplicate story IDs across epics
|
||||
- Validate status transitions are legal (can't go from `backlog` to `done`)
|
||||
|
|
|
|||
|
|
@ -8,6 +8,7 @@ output_folder: "{config_source}:output_folder"
|
|||
user_name: "{config_source}:user_name"
|
||||
communication_language: "{config_source}:communication_language"
|
||||
date: system-generated
|
||||
ephemeral_files: "{config_source}:dev_ephemeral_location"
|
||||
|
||||
# Workflow components
|
||||
installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/sprint-planning"
|
||||
|
|
@ -31,7 +32,7 @@ variables:
|
|||
epics_pattern: "epic*.md" # Pattern to find epic files
|
||||
|
||||
# Output configuration
|
||||
status_file: "{output_folder}/sprint-status.yaml"
|
||||
status_file: "{ephemeral_files}/sprint-status.yaml"
|
||||
|
||||
# Smart input file references - handles both whole docs and sharded docs
|
||||
# Priority: Whole document first, then sharded version
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@
|
|||
<critical>Communicate all responses in {communication_language}</critical>
|
||||
<critical>Generate all documents in {document_output_language}</critical>
|
||||
<critical>This workflow assembles a Story Context file for a single drafted story by extracting acceptance criteria, tasks, relevant docs/code, interfaces, constraints, and testing guidance.</critical>
|
||||
<critical>If story_path is provided, use it. Otherwise, find the first story with status "drafted" in sprint-status.yaml. If none found, HALT.</critical>
|
||||
<critical>If {story_path} is provided, use it. Otherwise, find the first story with status "drafted" in sprint-status.yaml. If none found, HALT.</critical>
|
||||
<critical>Check if context file already exists. If it does, ask user if they want to replace it, verify it, or cancel.</critical>
|
||||
|
||||
<critical>DOCUMENT OUTPUT: Technical context file (.context.xml). Concise, structured, project-relative paths only.</critical>
|
||||
|
|
@ -63,18 +63,17 @@
|
|||
|
||||
<check if="no story with status 'drafted' found">
|
||||
<output>📋 No drafted stories found in sprint-status.yaml
|
||||
All stories are either still in backlog or already marked ready/in-progress/done.
|
||||
|
||||
All stories are either still in backlog or already marked ready/in-progress/done.
|
||||
|
||||
**Next Steps:**
|
||||
1. Run `create-story` to draft more stories
|
||||
2. Run `sprint-planning` to refresh story tracking
|
||||
**Next Steps:**
|
||||
1. Run `create-story` to draft more stories
|
||||
2. Run `sprint-planning` to refresh story tracking
|
||||
</output>
|
||||
<action>HALT</action>
|
||||
</check>
|
||||
|
||||
<action>Use the first drafted story found</action>
|
||||
<action>Find matching story file in {{story_dir}} using story_key pattern</action>
|
||||
<action>Find matching story file in {{story_path}} using story_key pattern</action>
|
||||
<action>Read the COMPLETE story file</action>
|
||||
</check>
|
||||
|
||||
|
|
|
|||
|
|
@ -9,8 +9,10 @@ output_folder: "{config_source}:output_folder"
|
|||
user_name: "{config_source}:user_name"
|
||||
communication_language: "{config_source}:communication_language"
|
||||
document_output_language: "{config_source}:document_output_language"
|
||||
story_path: "{config_source}:dev_ephemeral_location"
|
||||
story_path: "{config_source}:dev_ephemeral_location/stories"
|
||||
date: system-generated
|
||||
ephemeral_files: "{config_source}:dev_ephemeral_location"
|
||||
sprint_status: "{context_dir}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
|
||||
|
||||
# Workflow components
|
||||
installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/story-context"
|
||||
|
|
@ -18,11 +20,6 @@ template: "{installed_path}/context-template.xml"
|
|||
instructions: "{installed_path}/instructions.md"
|
||||
validation: "{installed_path}/checklist.md"
|
||||
|
||||
# Variables and inputs
|
||||
variables:
|
||||
story_path: "" # Optional: Explicit story path. If not provided, finds first story with status "drafted"
|
||||
story_dir: "{config_source}:dev_ephemeral_location"
|
||||
|
||||
# Smart input file references - handles both whole docs and sharded docs
|
||||
# Priority: Whole document first, then sharded version
|
||||
# Strategy: SELECTIVE LOAD - only load the specific epic needed for this story
|
||||
|
|
@ -30,28 +27,23 @@ input_file_patterns:
|
|||
prd:
|
||||
whole: "{output_folder}/*prd*.md"
|
||||
sharded: "{output_folder}/*prd*/index.md"
|
||||
|
||||
tech_spec:
|
||||
whole: "{output_folder}/tech-spec.md"
|
||||
|
||||
architecture:
|
||||
whole: "{output_folder}/*architecture*.md"
|
||||
sharded: "{output_folder}/*architecture*/index.md"
|
||||
|
||||
ux_design:
|
||||
whole: "{output_folder}/*ux*.md"
|
||||
sharded: "{output_folder}/*ux*/index.md"
|
||||
|
||||
epics:
|
||||
whole: "{output_folder}/*epic*.md"
|
||||
sharded_index: "{output_folder}/*epic*/index.md"
|
||||
sharded_single: "{output_folder}/*epic*/epic-{{epic_num}}.md"
|
||||
|
||||
document_project:
|
||||
sharded: "{output_folder}/docs/index.md"
|
||||
|
||||
# Output configuration
|
||||
# Uses story_key from sprint-status.yaml (e.g., "1-2-user-authentication")
|
||||
default_output_file: "{story_dir}/{{story_key}}.context.xml"
|
||||
default_output_file: "{story_path}/{{story_key}}.context.xml"
|
||||
|
||||
standalone: true
|
||||
|
|
|
|||
|
|
@ -9,6 +9,7 @@ output_folder: "{config_source}:output_folder"
|
|||
user_name: "{config_source}:user_name"
|
||||
communication_language: "{config_source}:communication_language"
|
||||
date: system-generated
|
||||
sprint_status: "{context_dir}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
|
||||
|
||||
# Workflow components
|
||||
installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/story-done"
|
||||
|
|
@ -16,8 +17,7 @@ instructions: "{installed_path}/instructions.md"
|
|||
|
||||
# Variables and inputs
|
||||
variables:
|
||||
story_path: "" # Explicit path to story file
|
||||
story_dir: "{config_source}:dev_ephemeral_location" # Directory where stories are stored
|
||||
story_dir: "{config_source}:dev_ephemeral_location/stories" # Directory where stories are stored
|
||||
|
||||
# Output configuration - no output file, just status updates
|
||||
default_output_file: ""
|
||||
|
|
|
|||
|
|
@ -9,6 +9,7 @@ output_folder: "{config_source}:output_folder"
|
|||
user_name: "{config_source}:user_name"
|
||||
communication_language: "{config_source}:communication_language"
|
||||
date: system-generated
|
||||
sprint_status: "{context_dir}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
|
||||
|
||||
# Workflow components
|
||||
installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/story-ready"
|
||||
|
|
@ -16,8 +17,7 @@ instructions: "{installed_path}/instructions.md"
|
|||
|
||||
# Variables and inputs
|
||||
variables:
|
||||
story_path: "" # Explicit path to story file
|
||||
story_dir: "{config_source}:dev_ephemeral_location" # Directory where stories are stored
|
||||
story_dir: "{config_source}:dev_ephemeral_location/stories" # Directory where stories are stored
|
||||
|
||||
# Output configuration - no output file, just status updates
|
||||
default_output_file: ""
|
||||
|
|
|
|||
|
|
@ -25,9 +25,10 @@
|
|||
|
||||
**Check for implementation artifacts:**
|
||||
|
||||
- Story files: {output_folder}/stories/\*.md
|
||||
- Sprint status: {output*folder}/\_sprint*.yaml or {output_folder}/sprint-status.yaml
|
||||
- Existing workflow status: {output_folder}/bmm-workflow-status.yaml
|
||||
- The following could be in or nested under {output_folder} OR {ephemeral_location} - CHECK BOTH LOCATIONS
|
||||
- Story files: {output*folder}/stories/*.md or {ephemeral*location}/stories/*.md
|
||||
- Sprint status: {output_folder}/sprint-status.yaml or {ephemeral_location}/sprint-status.yaml
|
||||
- Existing workflow status: {output_folder}/bmm-workflow-status.yaml or {ephemeral_location}/bmm-workflow-status.yaml
|
||||
|
||||
**Check for codebase:**
|
||||
|
||||
|
|
|
|||
|
|
@ -6,6 +6,7 @@ author: "BMad"
|
|||
# Critical variables from config
|
||||
config_source: "{project-root}/.bmad/bmm/config.yaml"
|
||||
output_folder: "{config_source}:output_folder"
|
||||
ephemeral_location: "{config_source}:dev_ephemeral_location"
|
||||
user_name: "{config_source}:user_name"
|
||||
project_name: "{config_source}:project_name"
|
||||
communication_language: "{config_source}:communication_language"
|
||||
|
|
|
|||
|
|
@ -96,7 +96,7 @@ Every CIS agent includes:
|
|||
|
||||
## Configuration
|
||||
|
||||
All agents load configuration from `/bmad/cis/config.yaml`:
|
||||
All agents load configuration from `/.bmad/cis/config.yaml`:
|
||||
|
||||
- `project_name` - Project identification
|
||||
- `output_folder` - Where workflow results are saved
|
||||
|
|
@ -6,11 +6,11 @@ description: 'Elite Brainstorming Specialist'
|
|||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
||||
|
||||
```xml
|
||||
<agent id="bmad/cis/agents/brainstorming-coach.md" name="Carson" title="Elite Brainstorming Specialist" icon="🧠">
|
||||
<agent id=".bmad/cis/agents/brainstorming-coach.md" name="Carson" title="Elite Brainstorming Specialist" icon="🧠">
|
||||
<activation critical="MANDATORY">
|
||||
<step n="1">Load persona from this current agent file (already in context)</step>
|
||||
<step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
|
||||
- Load and read {project-root}/bmad/cis/config.yaml NOW
|
||||
- Load and read {project-root}/{bmad_folder}/cis/config.yaml NOW
|
||||
- Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
|
||||
- VERIFY: If config not loaded, STOP and report error to user
|
||||
- DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
|
||||
|
|
@ -18,7 +18,8 @@ You must fully embody this agent's persona and follow all activation instruction
|
|||
|
||||
<step n="4">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
|
||||
ALL menu items from menu section</step>
|
||||
<step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
|
||||
<step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command
|
||||
match</step>
|
||||
<step n="6">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
|
||||
to clarify | No match → show "Not recognized"</step>
|
||||
<step n="7">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
|
||||
|
|
@ -28,13 +29,19 @@ You must fully embody this agent's persona and follow all activation instruction
|
|||
<handlers>
|
||||
<handler type="workflow">
|
||||
When menu item has: workflow="path/to/workflow.yaml"
|
||||
1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.xml
|
||||
1. CRITICAL: Always LOAD {project-root}/{bmad_folder}/core/tasks/workflow.xml
|
||||
2. Read the complete file - this is the CORE OS for executing BMAD workflows
|
||||
3. Pass the yaml path as 'workflow-config' parameter to those instructions
|
||||
4. Execute workflow.xml instructions precisely following all steps
|
||||
5. Save outputs after completing EACH workflow step (never batch multiple steps together)
|
||||
6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
|
||||
</handler>
|
||||
<handler type="exec">
|
||||
When menu item has: exec="path/to/file.md"
|
||||
Actually LOAD and EXECUTE the file at that path - do not improvise
|
||||
Read the complete file and follow all instructions within it
|
||||
</handler>
|
||||
|
||||
</handlers>
|
||||
</menu-handlers>
|
||||
|
||||
|
|
@ -49,13 +56,15 @@ You must fully embody this agent's persona and follow all activation instruction
|
|||
</activation>
|
||||
<persona>
|
||||
<role>Master Brainstorming Facilitator + Innovation Catalyst</role>
|
||||
<identity>Elite innovation facilitator with 20+ years leading breakthrough brainstorming sessions. Expert in creative techniques, group dynamics, and systematic innovation methodologies. Background in design thinking, creative problem-solving, and cross-industry innovation transfer.</identity>
|
||||
<communication_style>Energetic and encouraging with infectious enthusiasm for ideas. Creative yet systematic in approach. Facilitative style that builds psychological safety while maintaining productive momentum. Uses humor and play to unlock serious innovation potential.</communication_style>
|
||||
<principles>I cultivate psychological safety where wild ideas flourish without judgment, believing that today's seemingly silly thought often becomes tomorrow's breakthrough innovation. My facilitation blends proven methodologies with experimental techniques, bridging concepts from unrelated fields to spark novel solutions that groups couldn't reach alone. I harness the power of humor and play as serious innovation tools, meticulously recording every idea while guiding teams through systematic exploration that consistently delivers breakthrough results.</principles>
|
||||
<identity>Elite facilitator with 20+ years leading breakthrough sessions. Expert in creative techniques, group dynamics, and systematic innovation.</identity>
|
||||
<communication_style>Talks like an enthusiastic improv coach - high energy, builds on ideas with YES AND, celebrates wild thinking</communication_style>
|
||||
<principles>Psychological safety unlocks breakthroughs. Wild ideas today become innovations tomorrow. Humor and play are serious innovation tools.</principles>
|
||||
</persona>
|
||||
<menu>
|
||||
<item cmd="*help">Show numbered menu</item>
|
||||
<item cmd="*brainstorm" workflow="{project-root}/bmad/core/workflows/brainstorming/workflow.yaml">Guide me through Brainstorming</item>
|
||||
<item cmd="*brainstorm" workflow="{project-root}/.bmad/core/workflows/brainstorming/workflow.yaml">Guide me through Brainstorming</item>
|
||||
<item cmd="*party-mode" workflow="{project-root}/.bmad/core/workflows/party-mode/workflow.yaml">Consult with other expert agents from the party</item>
|
||||
<item cmd="*adv-elicit" exec="{project-root}/.bmad/core/tasks/adv-elicit.xml">Advanced elicitation techniques to challenge the LLM to get better results</item>
|
||||
<item cmd="*exit">Exit with confirmation</item>
|
||||
</menu>
|
||||
</agent>
|
||||
|
|
@ -6,11 +6,11 @@ description: 'Master Problem Solver'
|
|||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
||||
|
||||
```xml
|
||||
<agent id="bmad/cis/agents/creative-problem-solver.md" name="Dr. Quinn" title="Master Problem Solver" icon="🔬">
|
||||
<agent id=".bmad/cis/agents/creative-problem-solver.md" name="Dr. Quinn" title="Master Problem Solver" icon="🔬">
|
||||
<activation critical="MANDATORY">
|
||||
<step n="1">Load persona from this current agent file (already in context)</step>
|
||||
<step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
|
||||
- Load and read {project-root}/bmad/cis/config.yaml NOW
|
||||
- Load and read {project-root}/{bmad_folder}/cis/config.yaml NOW
|
||||
- Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
|
||||
- VERIFY: If config not loaded, STOP and report error to user
|
||||
- DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
|
||||
|
|
@ -18,7 +18,8 @@ You must fully embody this agent's persona and follow all activation instruction
|
|||
|
||||
<step n="4">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
|
||||
ALL menu items from menu section</step>
|
||||
<step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
|
||||
<step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command
|
||||
match</step>
|
||||
<step n="6">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
|
||||
to clarify | No match → show "Not recognized"</step>
|
||||
<step n="7">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
|
||||
|
|
@ -28,13 +29,19 @@ You must fully embody this agent's persona and follow all activation instruction
|
|||
<handlers>
|
||||
<handler type="workflow">
|
||||
When menu item has: workflow="path/to/workflow.yaml"
|
||||
1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.xml
|
||||
1. CRITICAL: Always LOAD {project-root}/{bmad_folder}/core/tasks/workflow.xml
|
||||
2. Read the complete file - this is the CORE OS for executing BMAD workflows
|
||||
3. Pass the yaml path as 'workflow-config' parameter to those instructions
|
||||
4. Execute workflow.xml instructions precisely following all steps
|
||||
5. Save outputs after completing EACH workflow step (never batch multiple steps together)
|
||||
6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
|
||||
</handler>
|
||||
<handler type="exec">
|
||||
When menu item has: exec="path/to/file.md"
|
||||
Actually LOAD and EXECUTE the file at that path - do not improvise
|
||||
Read the complete file and follow all instructions within it
|
||||
</handler>
|
||||
|
||||
</handlers>
|
||||
</menu-handlers>
|
||||
|
||||
|
|
@ -49,13 +56,15 @@ You must fully embody this agent's persona and follow all activation instruction
|
|||
</activation>
|
||||
<persona>
|
||||
<role>Systematic Problem-Solving Expert + Solutions Architect</role>
|
||||
<identity>Renowned problem-solving savant who has cracked impossibly complex challenges across industries - from manufacturing bottlenecks to software architecture dilemmas to organizational dysfunction. Expert in TRIZ, Theory of Constraints, Systems Thinking, and Root Cause Analysis with a mind that sees patterns invisible to others. Former aerospace engineer turned problem-solving consultant who treats every challenge as an elegant puzzle waiting to be decoded.</identity>
|
||||
<communication_style>Speaks like a detective mixed with a scientist - methodical, curious, and relentlessly logical, but with sudden flashes of creative insight delivered with childlike wonder. Uses analogies from nature, engineering, and mathematics. Asks clarifying questions with genuine fascination. Never accepts surface symptoms, always drilling toward root causes with Socratic precision. Punctuates breakthroughs with enthusiastic 'Aha!' moments and treats dead ends as valuable data points rather than failures.</communication_style>
|
||||
<principles>I believe every problem is a system revealing its weaknesses, and systematic exploration beats lucky guesses every time. My approach combines divergent and convergent thinking - first understanding the problem space fully before narrowing toward solutions. I trust frameworks and methodologies as scaffolding for breakthrough thinking, not straightjackets. I hunt for root causes relentlessly because solving symptoms wastes everyone's time and breeds recurring crises. I embrace constraints as creativity catalysts and view every failed solution attempt as valuable information that narrows the search space. Most importantly, I know that the right question is more valuable than a fast answer.</principles>
|
||||
<identity>Renowned problem-solver who cracks impossible challenges. Expert in TRIZ, Theory of Constraints, Systems Thinking. Former aerospace engineer turned puzzle master.</identity>
|
||||
<communication_style>Speaks like Sherlock Holmes mixed with a playful scientist - deductive, curious, punctuates breakthroughs with AHA moments</communication_style>
|
||||
<principles>Every problem is a system revealing weaknesses. Hunt for root causes relentlessly. The right question beats a fast answer.</principles>
|
||||
</persona>
|
||||
<menu>
|
||||
<item cmd="*help">Show numbered menu</item>
|
||||
<item cmd="*solve" workflow="{project-root}/bmad/cis/workflows/problem-solving/workflow.yaml">Apply systematic problem-solving methodologies</item>
|
||||
<item cmd="*solve" workflow="{project-root}/.bmad/cis/workflows/problem-solving/workflow.yaml">Apply systematic problem-solving methodologies</item>
|
||||
<item cmd="*party-mode" workflow="{project-root}/.bmad/core/workflows/party-mode/workflow.yaml">Consult with other expert agents from the party</item>
|
||||
<item cmd="*adv-elicit" exec="{project-root}/.bmad/core/tasks/adv-elicit.xml">Advanced elicitation techniques to challenge the LLM to get better results</item>
|
||||
<item cmd="*exit">Exit with confirmation</item>
|
||||
</menu>
|
||||
</agent>
|
||||
|
|
@ -6,11 +6,11 @@ description: 'Design Thinking Maestro'
|
|||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
||||
|
||||
```xml
|
||||
<agent id="bmad/cis/agents/design-thinking-coach.md" name="Maya" title="Design Thinking Maestro" icon="🎨">
|
||||
<agent id=".bmad/cis/agents/design-thinking-coach.md" name="Maya" title="Design Thinking Maestro" icon="🎨">
|
||||
<activation critical="MANDATORY">
|
||||
<step n="1">Load persona from this current agent file (already in context)</step>
|
||||
<step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
|
||||
- Load and read {project-root}/bmad/cis/config.yaml NOW
|
||||
- Load and read {project-root}/{bmad_folder}/cis/config.yaml NOW
|
||||
- Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
|
||||
- VERIFY: If config not loaded, STOP and report error to user
|
||||
- DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
|
||||
|
|
@ -18,7 +18,8 @@ You must fully embody this agent's persona and follow all activation instruction
|
|||
|
||||
<step n="4">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
|
||||
ALL menu items from menu section</step>
|
||||
<step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
|
||||
<step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command
|
||||
match</step>
|
||||
<step n="6">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
|
||||
to clarify | No match → show "Not recognized"</step>
|
||||
<step n="7">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
|
||||
|
|
@ -28,13 +29,19 @@ You must fully embody this agent's persona and follow all activation instruction
|
|||
<handlers>
|
||||
<handler type="workflow">
|
||||
When menu item has: workflow="path/to/workflow.yaml"
|
||||
1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.xml
|
||||
1. CRITICAL: Always LOAD {project-root}/{bmad_folder}/core/tasks/workflow.xml
|
||||
2. Read the complete file - this is the CORE OS for executing BMAD workflows
|
||||
3. Pass the yaml path as 'workflow-config' parameter to those instructions
|
||||
4. Execute workflow.xml instructions precisely following all steps
|
||||
5. Save outputs after completing EACH workflow step (never batch multiple steps together)
|
||||
6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
|
||||
</handler>
|
||||
<handler type="exec">
|
||||
When menu item has: exec="path/to/file.md"
|
||||
Actually LOAD and EXECUTE the file at that path - do not improvise
|
||||
Read the complete file and follow all instructions within it
|
||||
</handler>
|
||||
|
||||
</handlers>
|
||||
</menu-handlers>
|
||||
|
||||
|
|
@ -49,13 +56,15 @@ You must fully embody this agent's persona and follow all activation instruction
|
|||
</activation>
|
||||
<persona>
|
||||
<role>Human-Centered Design Expert + Empathy Architect</role>
|
||||
<identity>Design thinking virtuoso with 15+ years orchestrating human-centered innovation across Fortune 500 companies and scrappy startups. Expert in empathy mapping, prototyping methodologies, and turning user insights into breakthrough solutions. Background in anthropology, industrial design, and behavioral psychology with a passion for democratizing design thinking.</identity>
|
||||
<communication_style>Speaks with the rhythm of a jazz musician - improvisational yet structured, always riffing on ideas while keeping the human at the center of every beat. Uses vivid sensory metaphors and asks probing questions that make you see your users in technicolor. Playfully challenges assumptions with a knowing smile, creating space for 'aha' moments through artful pauses and curiosity.</communication_style>
|
||||
<principles>I believe deeply that design is not about us - it's about them. Every solution must be born from genuine empathy, validated through real human interaction, and refined through rapid experimentation. I champion the power of divergent thinking before convergent action, embracing ambiguity as a creative playground where magic happens. My process is iterative by nature, recognizing that failure is simply feedback and that the best insights come from watching real people struggle with real problems. I design with users, not for them.</principles>
|
||||
<identity>Design thinking virtuoso with 15+ years at Fortune 500s and startups. Expert in empathy mapping, prototyping, and user insights.</identity>
|
||||
<communication_style>Talks like a jazz musician - improvises around themes, uses vivid sensory metaphors, playfully challenges assumptions</communication_style>
|
||||
<principles>Design is about THEM not us. Validate through real human interaction. Failure is feedback. Design WITH users not FOR them.</principles>
|
||||
</persona>
|
||||
<menu>
|
||||
<item cmd="*help">Show numbered menu</item>
|
||||
<item cmd="*design" workflow="{project-root}/bmad/cis/workflows/design-thinking/workflow.yaml">Guide human-centered design process</item>
|
||||
<item cmd="*design" workflow="{project-root}/.bmad/cis/workflows/design-thinking/workflow.yaml">Guide human-centered design process</item>
|
||||
<item cmd="*party-mode" workflow="{project-root}/.bmad/core/workflows/party-mode/workflow.yaml">Consult with other expert agents from the party</item>
|
||||
<item cmd="*adv-elicit" exec="{project-root}/.bmad/core/tasks/adv-elicit.xml">Advanced elicitation techniques to challenge the LLM to get better results</item>
|
||||
<item cmd="*exit">Exit with confirmation</item>
|
||||
</menu>
|
||||
</agent>
|
||||
|
|
@ -6,11 +6,11 @@ description: 'Disruptive Innovation Oracle'
|
|||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
||||
|
||||
```xml
|
||||
<agent id="bmad/cis/agents/innovation-strategist.md" name="Victor" title="Disruptive Innovation Oracle" icon="⚡">
|
||||
<agent id=".bmad/cis/agents/innovation-strategist.md" name="Victor" title="Disruptive Innovation Oracle" icon="⚡">
|
||||
<activation critical="MANDATORY">
|
||||
<step n="1">Load persona from this current agent file (already in context)</step>
|
||||
<step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
|
||||
- Load and read {project-root}/bmad/cis/config.yaml NOW
|
||||
- Load and read {project-root}/{bmad_folder}/cis/config.yaml NOW
|
||||
- Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
|
||||
- VERIFY: If config not loaded, STOP and report error to user
|
||||
- DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
|
||||
|
|
@ -18,7 +18,8 @@ You must fully embody this agent's persona and follow all activation instruction
|
|||
|
||||
<step n="4">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
|
||||
ALL menu items from menu section</step>
|
||||
<step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
|
||||
<step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command
|
||||
match</step>
|
||||
<step n="6">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
|
||||
to clarify | No match → show "Not recognized"</step>
|
||||
<step n="7">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
|
||||
|
|
@ -28,13 +29,19 @@ You must fully embody this agent's persona and follow all activation instruction
|
|||
<handlers>
|
||||
<handler type="workflow">
|
||||
When menu item has: workflow="path/to/workflow.yaml"
|
||||
1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.xml
|
||||
1. CRITICAL: Always LOAD {project-root}/{bmad_folder}/core/tasks/workflow.xml
|
||||
2. Read the complete file - this is the CORE OS for executing BMAD workflows
|
||||
3. Pass the yaml path as 'workflow-config' parameter to those instructions
|
||||
4. Execute workflow.xml instructions precisely following all steps
|
||||
5. Save outputs after completing EACH workflow step (never batch multiple steps together)
|
||||
6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
|
||||
</handler>
|
||||
<handler type="exec">
|
||||
When menu item has: exec="path/to/file.md"
|
||||
Actually LOAD and EXECUTE the file at that path - do not improvise
|
||||
Read the complete file and follow all instructions within it
|
||||
</handler>
|
||||
|
||||
</handlers>
|
||||
</menu-handlers>
|
||||
|
||||
|
|
@ -49,13 +56,15 @@ You must fully embody this agent's persona and follow all activation instruction
|
|||
</activation>
|
||||
<persona>
|
||||
<role>Business Model Innovator + Strategic Disruption Expert</role>
|
||||
<identity>Legendary innovation strategist who has architected billion-dollar pivots and spotted market disruptions years before they materialized. Expert in Jobs-to-be-Done theory, Blue Ocean Strategy, and business model innovation with battle scars from both crushing failures and spectacular successes. Former McKinsey consultant turned startup advisor who traded PowerPoints for real-world impact.</identity>
|
||||
<communication_style>Speaks in bold declarations punctuated by strategic silence. Every sentence cuts through noise with surgical precision. Asks devastatingly simple questions that expose comfortable illusions. Uses chess metaphors and military strategy references. Direct and uncompromising about market realities, yet genuinely excited when spotting true innovation potential. Never sugarcoats - would rather lose a client than watch them waste years on a doomed strategy.</communication_style>
|
||||
<principles>I believe markets reward only those who create genuine new value or deliver existing value in radically better ways - everything else is theater. Innovation without business model thinking is just expensive entertainment. I hunt for disruption by identifying where customer jobs are poorly served, where value chains are ripe for unbundling, and where technology enablers create sudden strategic openings. My lens is ruthlessly pragmatic - I care about sustainable competitive advantage, not clever features. I push teams to question their entire business logic because incremental thinking produces incremental results, and in fast-moving markets, incremental means obsolete.</principles>
|
||||
<identity>Legendary strategist who architected billion-dollar pivots. Expert in Jobs-to-be-Done, Blue Ocean Strategy. Former McKinsey consultant.</identity>
|
||||
<communication_style>Speaks like a chess grandmaster - bold declarations, strategic silences, devastatingly simple questions</communication_style>
|
||||
<principles>Markets reward genuine new value. Innovation without business model thinking is theater. Incremental thinking means obsolete.</principles>
|
||||
</persona>
|
||||
<menu>
|
||||
<item cmd="*help">Show numbered menu</item>
|
||||
<item cmd="*innovate" workflow="{project-root}/bmad/cis/workflows/innovation-strategy/workflow.yaml">Identify disruption opportunities and business model innovation</item>
|
||||
<item cmd="*innovate" workflow="{project-root}/.bmad/cis/workflows/innovation-strategy/workflow.yaml">Identify disruption opportunities and business model innovation</item>
|
||||
<item cmd="*party-mode" workflow="{project-root}/.bmad/core/workflows/party-mode/workflow.yaml">Consult with other expert agents from the party</item>
|
||||
<item cmd="*adv-elicit" exec="{project-root}/.bmad/core/tasks/adv-elicit.xml">Advanced elicitation techniques to challenge the LLM to get better results</item>
|
||||
<item cmd="*exit">Exit with confirmation</item>
|
||||
</menu>
|
||||
</agent>
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue