chore: update documentation to reflect recent architectural changes and improve clarity
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: 'bmad-master'
|
||||
mode: all
|
||||
description: 'bmad-master agent'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: 'agent-builder'
|
||||
mode: all
|
||||
description: 'agent-builder agent'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: 'module-builder'
|
||||
mode: all
|
||||
description: 'module-builder agent'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: 'workflow-builder'
|
||||
mode: all
|
||||
description: 'workflow-builder agent'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: 'analyst'
|
||||
mode: all
|
||||
description: 'analyst agent'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: 'architect'
|
||||
mode: all
|
||||
description: 'architect agent'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: 'dev'
|
||||
mode: all
|
||||
description: 'dev agent'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: 'pm'
|
||||
mode: all
|
||||
description: 'pm agent'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: 'qa'
|
||||
mode: all
|
||||
description: 'qa agent'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: 'quick-flow-solo-dev'
|
||||
mode: all
|
||||
description: 'quick-flow-solo-dev agent'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: 'sm'
|
||||
mode: all
|
||||
description: 'sm agent'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: 'tech-writer'
|
||||
mode: all
|
||||
description: 'tech-writer agent'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: 'ux-designer'
|
||||
mode: all
|
||||
description: 'ux-designer agent'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: 'brainstorming-coach'
|
||||
mode: all
|
||||
description: 'brainstorming-coach agent'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: 'creative-problem-solver'
|
||||
mode: all
|
||||
description: 'creative-problem-solver agent'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: 'design-thinking-coach'
|
||||
mode: all
|
||||
description: 'design-thinking-coach agent'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: 'innovation-strategist'
|
||||
mode: all
|
||||
description: 'innovation-strategist agent'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: 'presentation-master'
|
||||
mode: all
|
||||
description: 'presentation-master agent'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: 'storyteller'
|
||||
mode: all
|
||||
description: 'storyteller agent'
|
||||
---
|
||||
|
||||
@@ -1,17 +0,0 @@
|
||||
---
|
||||
name: 'qa-automate'
|
||||
description: 'Generate tests quickly for existing features using standard test patterns'
|
||||
---
|
||||
|
||||
Execute the BMAD 'qa-automate' workflow.
|
||||
|
||||
CRITICAL: You must load and follow the workflow definition exactly.
|
||||
|
||||
WORKFLOW INSTRUCTIONS:
|
||||
|
||||
1. LOAD the workflow file from {project-root}/_bmad/bmm/workflows/qa/automate/workflow.yaml
|
||||
2. READ its entire contents
|
||||
3. FOLLOW every step precisely as specified
|
||||
4. DO NOT skip or modify any steps
|
||||
|
||||
WORKFLOW FILE: {project-root}/_bmad/bmm/workflows/qa/automate/workflow.yaml
|
||||
@@ -1,5 +1,4 @@
|
||||
---
|
||||
name: 'create-agent'
|
||||
description: 'Create a new BMAD agent with best practices and compliance'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,4 @@
|
||||
---
|
||||
name: 'create-module-brief'
|
||||
description: 'Create product brief for BMAD module development'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,4 @@
|
||||
---
|
||||
name: 'create-module'
|
||||
description: 'Create a complete BMAD module with agents, workflows, and infrastructure'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,4 @@
|
||||
---
|
||||
name: 'create-workflow'
|
||||
description: 'Create a new BMAD workflow with proper structure and best practices'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,4 @@
|
||||
---
|
||||
name: 'edit-agent'
|
||||
description: 'Edit existing BMAD agents while maintaining compliance'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,4 @@
|
||||
---
|
||||
name: 'edit-module'
|
||||
description: 'Edit existing BMAD modules while maintaining coherence'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,4 @@
|
||||
---
|
||||
name: 'edit-workflow'
|
||||
description: 'Edit existing BMAD workflows while maintaining integrity'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,4 @@
|
||||
---
|
||||
name: 'rework-workflow'
|
||||
description: 'Rework a Workflow to a V6 Compliant Version'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,4 @@
|
||||
---
|
||||
name: 'validate-agent'
|
||||
description: 'Validate existing BMAD agents and offer to improve deficiencies'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,4 @@
|
||||
---
|
||||
name: 'validate-max-parallel-workflow'
|
||||
description: 'Run validation checks in MAX-PARALLEL mode against a workflow requires a tool that supports Parallel Sub-Processes'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,4 @@
|
||||
---
|
||||
name: 'validate-module'
|
||||
description: 'Run compliance check on BMAD modules against best practices'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,4 @@
|
||||
---
|
||||
name: 'validate-workflow'
|
||||
description: 'Run validation check on BMAD workflows against best practices'
|
||||
---
|
||||
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'check-implementation-readiness'
|
||||
description: 'Critical validation workflow that assesses PRD, Architecture, and Epics & Stories for completeness and alignment before implementation. Uses adversarial review approach to find gaps and issues.'
|
||||
description: 'Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".'
|
||||
---
|
||||
|
||||
Execute the BMAD 'check-implementation-readiness' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'code-review'
|
||||
description: 'Perform an ADVERSARIAL Senior Developer code review that finds 3-10 specific problems in every story. Challenges everything: code quality, test coverage, architecture compliance, security, performance. NEVER accepts `looks good` - must find minimum issues and can auto-fix with user approval.'
|
||||
description: 'Perform adversarial code review finding specific issues. Use when the user says "run code review" or "review this code"'
|
||||
---
|
||||
|
||||
Execute the BMAD 'code-review' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'correct-course'
|
||||
description: 'Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation'
|
||||
description: 'Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"'
|
||||
---
|
||||
|
||||
Execute the BMAD 'correct-course' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'create-architecture'
|
||||
description: 'Collaborative architectural decision facilitation for AI-agent consistency. Replaces template-driven architecture with intelligent, adaptive conversation that produces a decision-focused architecture document optimized for preventing agent conflicts.'
|
||||
description: 'Create architecture solution design decisions for AI agent consistency. Use when the user says "lets create architecture" or "create technical architecture" or "create a solution design"'
|
||||
---
|
||||
|
||||
Execute the BMAD 'create-architecture' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'create-epics-and-stories'
|
||||
description: 'Transform PRD requirements and Architecture decisions into comprehensive stories organized by user value. This workflow requires completed PRD + Architecture documents (UX recommended if UI exists) and breaks down requirements into implementation-ready epics and user stories that incorporate all available technical and design context. Creates detailed, actionable stories with complete acceptance criteria for development teams.'
|
||||
description: 'Break requirements into epics and user stories. Use when the user says "create the epics and stories list"'
|
||||
---
|
||||
|
||||
Execute the BMAD 'create-epics-and-stories' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'create-prd'
|
||||
description: 'Create a comprehensive PRD (Product Requirements Document) through structured workflow facilitation'
|
||||
description: 'Create a PRD from scratch. Use when the user says "lets create a product requirements document" or "I want to create a new PRD"'
|
||||
---
|
||||
|
||||
Execute the BMAD 'create-prd' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'create-product-brief'
|
||||
description: 'Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.'
|
||||
description: 'Create product brief through collaborative discovery. Use when the user says "lets create a product brief" or "help me create a project brief"'
|
||||
---
|
||||
|
||||
Execute the BMAD 'create-product-brief' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'create-story'
|
||||
description: 'Create the next user story from epics+stories with enhanced context analysis and direct ready-for-dev marking'
|
||||
description: 'Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]"'
|
||||
---
|
||||
|
||||
Execute the BMAD 'create-story' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'create-ux-design'
|
||||
description: 'Work with a peer UX Design expert to plan your applications UX patterns, look and feel.'
|
||||
description: 'Plan UX patterns and design specifications. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"'
|
||||
---
|
||||
|
||||
Execute the BMAD 'create-ux-design' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'dev-story'
|
||||
description: 'Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria'
|
||||
description: 'Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"'
|
||||
---
|
||||
|
||||
Execute the BMAD 'dev-story' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'document-project'
|
||||
description: 'Analyzes and documents brownfield projects by scanning codebase, architecture, and patterns to create comprehensive reference documentation for AI-assisted development'
|
||||
description: 'Document brownfield projects for AI context. Use when the user says "document this project" or "generate project docs"'
|
||||
---
|
||||
|
||||
Execute the BMAD 'document-project' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'domain-research'
|
||||
description: 'Conduct domain research covering industry analysis, regulations, technology trends, and ecosystem dynamics using current web data and verified sources.'
|
||||
description: 'Conduct domain and industry research. Use when the user says "lets create a research report on [domain or industry]"'
|
||||
---
|
||||
|
||||
Execute the BMAD 'domain-research' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'edit-prd'
|
||||
description: 'Edit and improve an existing PRD - enhance clarity, completeness, and quality'
|
||||
description: 'Edit an existing PRD. Use when the user says "edit this PRD".'
|
||||
---
|
||||
|
||||
Execute the BMAD 'edit-prd' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'generate-project-context'
|
||||
description: 'Creates a concise project-context.md file with critical rules and patterns that AI agents must follow when implementing code. Optimized for LLM context efficiency.'
|
||||
description: 'Create project-context.md with AI rules. Use when the user says "generate project context" or "create project context"'
|
||||
---
|
||||
|
||||
Execute the BMAD 'generate-project-context' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'market-research'
|
||||
description: 'Conduct market research covering market size, growth, competition, and customer insights using current web data and verified sources.'
|
||||
description: 'Conduct market research on competition and customers. Use when the user says "create a market research report about [business idea]".'
|
||||
---
|
||||
|
||||
Execute the BMAD 'market-research' workflow.
|
||||
16
.opencode/commands/bmad-bmm-qa-generate-e2e-tests.md
Normal file
16
.opencode/commands/bmad-bmm-qa-generate-e2e-tests.md
Normal file
@@ -0,0 +1,16 @@
|
||||
---
|
||||
description: 'Generate end to end automated tests for existing features. Use when the user says "create qa automated tests for [feature]"'
|
||||
---
|
||||
|
||||
Execute the BMAD 'qa-generate-e2e-tests' workflow.
|
||||
|
||||
CRITICAL: You must load and follow the workflow definition exactly.
|
||||
|
||||
WORKFLOW INSTRUCTIONS:
|
||||
|
||||
1. LOAD the workflow file from {project-root}/_bmad/bmm/workflows/qa-generate-e2e-tests/workflow.yaml
|
||||
2. READ its entire contents
|
||||
3. FOLLOW every step precisely as specified
|
||||
4. DO NOT skip or modify any steps
|
||||
|
||||
WORKFLOW FILE: {project-root}/_bmad/bmm/workflows/qa-generate-e2e-tests/workflow.yaml
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'quick-dev'
|
||||
description: 'Flexible development - execute tech-specs OR direct instructions with optional planning.'
|
||||
description: 'Implement a Quick Tech Spec for small changes or features. Use when the user provides a quick tech spec and says "implement this quick spec" or "proceed with implementation of [quick tech spec]"'
|
||||
---
|
||||
|
||||
Execute the BMAD 'quick-dev' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'quick-spec'
|
||||
description: 'Conversational spec engineering - ask questions, investigate code, produce implementation-ready tech-spec.'
|
||||
description: 'Very quick process to create implementation-ready quick specs for small changes or features. Use when the user says "create a quick spec" or "generate a quick tech spec"'
|
||||
---
|
||||
|
||||
Execute the BMAD 'quick-spec' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'retrospective'
|
||||
description: 'Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic'
|
||||
description: 'Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"'
|
||||
---
|
||||
|
||||
Execute the BMAD 'retrospective' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'sprint-planning'
|
||||
description: 'Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle'
|
||||
description: 'Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"'
|
||||
---
|
||||
|
||||
Execute the BMAD 'sprint-planning' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'sprint-status'
|
||||
description: 'Summarize sprint-status.yaml, surface risks, and route to the right implementation workflow.'
|
||||
description: 'Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status"'
|
||||
---
|
||||
|
||||
Execute the BMAD 'sprint-status' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'technical-research'
|
||||
description: 'Conduct technical research covering technology evaluation, architecture decisions, and implementation approaches using current web data and verified sources.'
|
||||
description: 'Conduct technical research on technologies and architecture. Use when the user says "create a technical research report on [topic]".'
|
||||
---
|
||||
|
||||
Execute the BMAD 'technical-research' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'validate-prd'
|
||||
description: 'Validate an existing PRD against BMAD standards - comprehensive review for completeness, clarity, and quality'
|
||||
description: 'Validate a PRD against standards. Use when the user says "validate this PRD" or "run PRD validation"'
|
||||
---
|
||||
|
||||
Execute the BMAD 'validate-prd' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'brainstorming'
|
||||
description: 'Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods'
|
||||
description: 'Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods. Use when the user says help me brainstorm or help me ideate.'
|
||||
---
|
||||
|
||||
Execute the BMAD 'brainstorming' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'design-thinking'
|
||||
description: '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.'
|
||||
description: 'Guide human-centered design processes using empathy-driven methodologies. Use when the user says "lets run design thinking" or "I want to apply design thinking"'
|
||||
---
|
||||
|
||||
Execute the BMAD 'design-thinking' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'innovation-strategy'
|
||||
description: '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.'
|
||||
description: 'Identify disruption opportunities and architect business model innovation. Use when the user says "lets create an innovation strategy" or "I want to find disruption opportunities"'
|
||||
---
|
||||
|
||||
Execute the BMAD 'innovation-strategy' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'problem-solving'
|
||||
description: '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.'
|
||||
description: 'Apply systematic problem-solving methodologies to complex challenges. Use when the user says "guide me through structured problem solving" or "I want to crack this challenge with guided problem solving techniques"'
|
||||
---
|
||||
|
||||
Execute the BMAD 'problem-solving' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'storytelling'
|
||||
description: '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.'
|
||||
description: 'Craft compelling narratives using story frameworks. Use when the user says "help me with storytelling" or "I want to create a narrative through storytelling"'
|
||||
---
|
||||
|
||||
Execute the BMAD 'storytelling' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'editorial-review-prose'
|
||||
description: 'Clinical copy-editor that reviews text for communication issues'
|
||||
description: 'Clinical copy-editor that reviews text for communication issues. Use when user says review for prose or improve the prose'
|
||||
---
|
||||
|
||||
Execute the BMAD 'editorial-review-prose' task.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'editorial-review-structure'
|
||||
description: 'Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension'
|
||||
description: 'Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension. Use when user requests structural review or editorial review of structure'
|
||||
---
|
||||
|
||||
Execute the BMAD 'editorial-review-structure' task.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'help'
|
||||
description: 'Get unstuck by showing what workflow steps come next or answering questions about what to do'
|
||||
description: 'Analyzes what is done and the users query and offers advice on what to do next. Use if user says what should I do next or what do I do now'
|
||||
---
|
||||
|
||||
Execute the BMAD 'help' task.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'index-docs'
|
||||
description: 'Generates or updates an index.md of all documents in the specified directory'
|
||||
description: 'Generates or updates an index.md to reference all docs in the folder. Use if user requests to create or update an index of all files in a specific folder'
|
||||
---
|
||||
|
||||
Execute the BMAD 'index-docs' task.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'party-mode'
|
||||
description: 'Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations'
|
||||
description: 'Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations. Use when user requests party mode.'
|
||||
---
|
||||
|
||||
Execute the BMAD 'party-mode' workflow.
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'review-adversarial-general'
|
||||
description: 'Cynically review content and produce findings'
|
||||
description: 'Perform a Cynical Review and produce a findings report. Use when the user requests a critical review of something'
|
||||
---
|
||||
|
||||
Execute the BMAD 'review-adversarial-general' task.
|
||||
13
.opencode/commands/bmad-review-edge-case-hunter.md
Normal file
13
.opencode/commands/bmad-review-edge-case-hunter.md
Normal file
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven.'
|
||||
---
|
||||
|
||||
Execute the BMAD 'review-edge-case-hunter' task.
|
||||
|
||||
TASK INSTRUCTIONS:
|
||||
|
||||
1. LOAD the task file from {project-root}/_bmad/core/tasks/review-edge-case-hunter.xml
|
||||
2. READ its entire contents
|
||||
3. FOLLOW every instruction precisely as specified
|
||||
|
||||
TASK FILE: {project-root}/_bmad/core/tasks/review-edge-case-hunter.xml
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: 'shard-doc'
|
||||
description: 'Splits large markdown documents into smaller, organized files based on level 2 (default) sections'
|
||||
description: 'Splits large markdown documents into smaller, organized files based on level 2 (default) sections. Use if the user says perform shard document'
|
||||
---
|
||||
|
||||
Execute the BMAD 'shard-doc' task.
|
||||
Reference in New Issue
Block a user