From 981e5a49c2abdf5366d3a68f6c3b5f6aedd8aa7a Mon Sep 17 00:00:00 2001 From: Chad Woolley Date: Sun, 1 Feb 2026 08:05:49 -0800 Subject: [PATCH 1/9] docs: Add exact slash commands to getting-started guide (#1505) The getting-started tutorial referenced agents and workflows by name (e.g., "Load the PM agent", "Run the prd workflow") without providing the actual commands to type. This adds the exact slash commands inline alongside the existing prose so new users know precisely what to run. --- docs/tutorials/getting-started.md | 76 ++++++++++++++++--------------- 1 file changed, 40 insertions(+), 36 deletions(-) diff --git a/docs/tutorials/getting-started.md b/docs/tutorials/getting-started.md index 38d25a2d..54a9b240 100644 --- a/docs/tutorials/getting-started.md +++ b/docs/tutorials/getting-started.md @@ -65,7 +65,11 @@ The installer creates two folders: - `_bmad/` — agents, workflows, tasks, and configuration - `_bmad-output/` — empty for now, but this is where your artifacts will be saved -Open your AI IDE in the project folder. Run the `help` workflow (`/bmad-help` on most platforms) to see what to do next — it detects what you've completed and recommends the next step. +Open your AI IDE in the project folder. Run the `help` workflow (`/bmad-help`) to see what to do next — it detects what you've completed and recommends the next step. + +:::note[How to Load Agents and Run Workflows] +Each workflow has a **slash command** you run in your IDE (e.g., `/bmad-bmm-create-prd`). Running a workflow command automatically loads the appropriate agent — you don't need to load agents separately. You can also load an agent directly for general conversation (e.g., `/bmad-agent-bmm-pm` for the PM agent). +::: :::caution[Fresh Chats] Always start a fresh chat for each workflow. This prevents context limitations from causing issues. @@ -78,29 +82,29 @@ Work through phases 1-3. **Use fresh chats for each workflow.** ### Phase 1: Analysis (Optional) All workflows in this phase are optional: -- **brainstorming** — Guided ideation -- **research** — Market and technical research -- **create-product-brief** — Recommended foundation document +- **brainstorming** (`/bmad-brainstorming`) — Guided ideation +- **research** (`/bmad-bmm-research`) — Market and technical research +- **create-product-brief** (`/bmad-bmm-create-product-brief`) — Recommended foundation document ### Phase 2: Planning (Required) **For BMad Method and Enterprise tracks:** -1. Load the **PM agent** in a new chat -2. Run the `prd` workflow +1. Load the **PM agent** (`/bmad-agent-bmm-pm`) in a new chat +2. Run the `prd` workflow (`/bmad-bmm-create-prd`) 3. Output: `PRD.md` **For Quick Flow track:** -- Use the `quick-spec` workflow instead of PRD, then skip to implementation +- Use the `quick-spec` workflow (`/bmad-bmm-quick-spec`) instead of PRD, then skip to implementation :::note[UX Design (Optional)] -If your project has a user interface, load the **UX-Designer agent** and run the UX design workflow after creating your PRD. +If your project has a user interface, load the **UX-Designer agent** (`/bmad-agent-bmm-ux-designer`) and run the UX design workflow (`/bmad-bmm-create-ux-design`) after creating your PRD. ::: ### Phase 3: Solutioning (BMad Method/Enterprise) **Create Architecture** -1. Load the **Architect agent** in a new chat -2. Run `create-architecture` +1. Load the **Architect agent** (`/bmad-agent-bmm-architect`) in a new chat +2. Run `create-architecture` (`/bmad-bmm-create-architecture`) 3. Output: Architecture document with technical decisions **Create Epics and Stories** @@ -109,13 +113,13 @@ If your project has a user interface, load the **UX-Designer agent** and run the Epics and stories are now created *after* architecture. This produces better quality stories because architecture decisions (database, API patterns, tech stack) directly affect how work should be broken down. ::: -1. Load the **PM agent** in a new chat -2. Run `create-epics-and-stories` +1. Load the **PM agent** (`/bmad-agent-bmm-pm`) in a new chat +2. Run `create-epics-and-stories` (`/bmad-bmm-create-epics-and-stories`) 3. The workflow uses both PRD and Architecture to create technically-informed stories **Implementation Readiness Check** *(Highly Recommended)* -1. Load the **Architect agent** in a new chat -2. Run `check-implementation-readiness` +1. Load the **Architect agent** (`/bmad-agent-bmm-architect`) in a new chat +2. Run `check-implementation-readiness` (`/bmad-bmm-check-implementation-readiness`) 3. Validates cohesion across all planning documents ## Step 2: Build Your Project @@ -124,19 +128,19 @@ Once planning is complete, move to implementation. **Each workflow should run in ### Initialize Sprint Planning -Load the **SM agent** and run `sprint-planning`. This creates `sprint-status.yaml` to track all epics and stories. +Load the **SM agent** (`/bmad-agent-bmm-sm`) and run `sprint-planning` (`/bmad-bmm-sprint-planning`). This creates `sprint-status.yaml` to track all epics and stories. ### The Build Cycle For each story, repeat this cycle with fresh chats: -| Step | Agent | Workflow | Purpose | -| ---- | ----- | -------------- | ---------------------------------- | -| 1 | SM | `create-story` | Create story file from epic | -| 2 | DEV | `dev-story` | Implement the story | -| 3 | DEV | `code-review` | Quality validation *(recommended)* | +| Step | Agent | Workflow | Command | Purpose | +| ---- | ----- | -------------- | -------------------------- | ---------------------------------- | +| 1 | SM | `create-story` | `/bmad-bmm-create-story` | Create story file from epic | +| 2 | DEV | `dev-story` | `/bmad-bmm-dev-story` | Implement the story | +| 3 | DEV | `code-review` | `/bmad-bmm-code-review` | Quality validation *(recommended)* | -After completing all stories in an epic, load the **SM agent** and run `retrospective`. +After completing all stories in an epic, load the **SM agent** (`/bmad-agent-bmm-sm`) and run `retrospective` (`/bmad-bmm-retrospective`). ## What You've Accomplished @@ -162,17 +166,17 @@ your-project/ ## Quick Reference -| Workflow | Agent | Purpose | -| -------------------------------- | --------- | ------------------------------------ | -| `help` | Any | Get guidance on what to do next | -| `prd` | PM | Create Product Requirements Document | -| `create-architecture` | Architect | Create architecture document | -| `create-epics-and-stories` | PM | Break down PRD into epics | -| `check-implementation-readiness` | Architect | Validate planning cohesion | -| `sprint-planning` | SM | Initialize sprint tracking | -| `create-story` | SM | Create a story file | -| `dev-story` | DEV | Implement a story | -| `code-review` | DEV | Review implemented code | +| Workflow | Command | Agent | Purpose | +| -------------------------------- | ------------------------------------------ | --------- | ------------------------------------ | +| `help` | `/bmad-help` | Any | Get guidance on what to do next | +| `prd` | `/bmad-bmm-create-prd` | PM | Create Product Requirements Document | +| `create-architecture` | `/bmad-bmm-create-architecture` | Architect | Create architecture document | +| `create-epics-and-stories` | `/bmad-bmm-create-epics-and-stories` | PM | Break down PRD into epics | +| `check-implementation-readiness` | `/bmad-bmm-check-implementation-readiness` | Architect | Validate planning cohesion | +| `sprint-planning` | `/bmad-bmm-sprint-planning` | SM | Initialize sprint tracking | +| `create-story` | `/bmad-bmm-create-story` | SM | Create a story file | +| `dev-story` | `/bmad-bmm-dev-story` | DEV | Implement a story | +| `code-review` | `/bmad-bmm-code-review` | DEV | Review implemented code | ## Common Questions @@ -180,10 +184,10 @@ your-project/ Only for BMad Method and Enterprise tracks. Quick Flow skips from tech-spec to implementation. **Can I change my plan later?** -Yes. The SM agent has a `correct-course` workflow for handling scope changes. +Yes. The SM agent has a `correct-course` workflow (`/bmad-bmm-correct-course`) for handling scope changes. **What if I want to brainstorm first?** -Load the Analyst agent and run `brainstorming` before starting your PRD. +Load the Analyst agent (`/bmad-agent-bmm-analyst`) and run `brainstorming` (`/bmad-brainstorming`) before starting your PRD. **Do I need to follow a strict order?** Not strictly. Once you learn the flow, you can run workflows directly using the Quick Reference above. @@ -192,14 +196,14 @@ Not strictly. Once you learn the flow, you can run workflows directly using the - **During workflows** — Agents guide you with questions and explanations - **Community** — [Discord](https://discord.gg/gk8jAdXWmj) (#bmad-method-help, #report-bugs-and-issues) -- **Stuck?** — Run `help` to see what to do next +- **Stuck?** — Run `help` (`/bmad-help`) to see what to do next ## Key Takeaways :::tip[Remember These] - **Always use fresh chats** — Start a new chat for each workflow - **Track matters** — Quick Flow uses quick-spec; Method/Enterprise need PRD and architecture -- **Use `help` when stuck** — It detects your progress and suggests next steps +- **Use `help` (`/bmad-help`) when stuck** — It detects your progress and suggests next steps ::: Ready to start? Install BMad and let the agents guide you through your first project. From ef7abb7ca581e53367243b53b1f0c78ce5e08a04 Mon Sep 17 00:00:00 2001 From: Alex Verkhovsky Date: Sun, 1 Feb 2026 09:14:50 -0700 Subject: [PATCH 2/9] fix: complete sharding of market research customer analysis steps (#1486) Connect orphaned detailed customer analysis chain (steps 02-behavior, 03-pain-points, 04-decisions) by updating step-01-init to load step-02-customer-behavior instead of the condensed step-02-customer-insights. Remove the now-superseded monolithic file. Fixes #1399 Co-authored-by: Brian --- .../research/market-steps/step-01-init.md | 2 +- .../market-steps/step-02-customer-insights.md | 200 ------------------ 2 files changed, 1 insertion(+), 201 deletions(-) delete mode 100644 src/bmm/workflows/1-analysis/research/market-steps/step-02-customer-insights.md diff --git a/src/bmm/workflows/1-analysis/research/market-steps/step-01-init.md b/src/bmm/workflows/1-analysis/research/market-steps/step-01-init.md index a3772a9b..5ab85939 100644 --- a/src/bmm/workflows/1-analysis/research/market-steps/step-01-init.md +++ b/src/bmm/workflows/1-analysis/research/market-steps/step-01-init.md @@ -138,7 +138,7 @@ Show initial scope document and present continue option: - Update frontmatter: `stepsCompleted: [1]` - Add confirmation note to document: "Scope confirmed by user on {{date}}" -- Load: `./step-02-customer-insights.md` +- Load: `./step-02-customer-behavior.md` #### If 'Modify': diff --git a/src/bmm/workflows/1-analysis/research/market-steps/step-02-customer-insights.md b/src/bmm/workflows/1-analysis/research/market-steps/step-02-customer-insights.md deleted file mode 100644 index c6d7ea32..00000000 --- a/src/bmm/workflows/1-analysis/research/market-steps/step-02-customer-insights.md +++ /dev/null @@ -1,200 +0,0 @@ -# Market Research Step 2: Customer Insights - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A CUSTOMER INSIGHTS ANALYST, not content generator -- 💬 FOCUS on customer behavior and needs analysis -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] continue option after customer insights content generation -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from step-01 are available -- Focus on customer behavior and needs analysis -- Web search capabilities with source verification are enabled -- May need to search for current customer behavior trends - -## YOUR TASK: - -Conduct comprehensive customer insights analysis with emphasis on behavior patterns and needs. - -## CUSTOMER INSIGHTS SEQUENCE: - -### 1. Begin Customer Insights Analysis - -**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer areas simultaneously and thoroughly - -Start with customer research approach: -"Now I'll conduct **customer insights analysis** to understand customer behavior and needs. - -**Customer Insights Focus:** - -- Customer behavior patterns and preferences -- Pain points and challenges -- Decision-making processes -- Customer journey mapping -- Customer satisfaction drivers -- Demographic and psychographic profiles - -**Let me search for current customer insights using parallel web searches for comprehensive coverage.**" - -### 2. Parallel Customer Research Execution - -**Execute multiple web searches simultaneously:** - -Search the web: "[product/service/market] customer behavior patterns" -Search the web: "[product/service/market] customer pain points challenges" -Search the web: "[product/service/market] customer decision process" - -**Analysis approach:** - -- Look for customer behavior studies and surveys -- Search for customer experience and interaction patterns -- Research customer satisfaction methodologies -- Note generational and cultural customer variations -- Research customer pain points and frustrations -- Analyze decision-making processes and criteria - -### 3. Analyze and Aggregate Results - -**Collect and analyze findings from all parallel searches:** - -"After executing comprehensive parallel web searches, let me analyze and aggregate the customer insights: - -**Research Coverage:** - -- Customer behavior patterns and preferences -- Pain points and challenges -- Decision-making processes and journey mapping - -**Cross-Customer Analysis:** -[Identify patterns connecting behavior, pain points, and decisions] - -**Quality Assessment:** -[Overall confidence levels and research gaps identified]" - -### 4. Generate Customer Insights Content - -Prepare customer analysis with web search citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Customer Insights - -### Customer Behavior Patterns - -[Customer behavior analysis with source citations] -_Source: [URL]_ - -### Pain Points and Challenges - -[Pain points analysis with source citations] -_Source: [URL]_ - -### Decision-Making Processes - -[Decision-making analysis with source citations] -_Source: [URL]_ - -### Customer Journey Mapping - -[Customer journey analysis with source citations] -_Source: [URL]_ - -### Customer Satisfaction Drivers - -[Satisfaction drivers analysis with source citations] -_Source: [URL]_ - -### Demographic Profiles - -[Demographic profiles analysis with source citations] -_Source: [URL]_ - -### Psychographic Profiles - -[Psychographic profiles analysis with source citations] -_Source: [URL]_ -``` - -### 5. Present Analysis and Continue Option - -Show the generated customer insights and present continue option: -"I've completed the **customer insights analysis** for customer behavior and needs. - -**Key Customer Findings:** - -- Customer behavior patterns clearly identified -- Pain points and challenges thoroughly documented -- Decision-making processes mapped -- Customer journey insights captured -- Satisfaction and profile data analyzed - -**Ready to proceed to competitive analysis?** -[C] Continue - Save this to the document and proceed to competitive analysis - -### 6. Handle Continue Selection - -#### If 'C' (Continue): - -- Append the final content to the research document -- Update frontmatter: `stepsCompleted: [1, 2]` -- Load: `./step-05-competitive-analysis.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the research document using the structure from step 4. - -## SUCCESS METRICS: - -✅ Customer behavior patterns identified with current citations -✅ Pain points and challenges clearly documented -✅ Decision-making processes thoroughly analyzed -✅ Customer journey insights captured and mapped -✅ Customer satisfaction drivers identified -✅ [C] continue option presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Relying solely on training data without web verification for current facts - -❌ Missing critical customer behavior patterns -❌ Not identifying key pain points and challenges -❌ Incomplete customer journey mapping -❌ Not presenting [C] continue option after content generation -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## CUSTOMER RESEARCH PROTOCOLS: - -- Search for customer behavior studies and surveys -- Use market research firm and industry association sources -- Research customer experience and interaction patterns -- Note generational and cultural customer variations -- Research customer satisfaction methodologies - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `./step-05-competitive-analysis.md` to focus on competitive landscape analysis. - -Remember: Always emphasize current customer data and rigorous source verification! From 04e3dc8f75c7150077629a6cf748921dbb366b47 Mon Sep 17 00:00:00 2001 From: Michael Pursifull Date: Sun, 1 Feb 2026 10:15:35 -0600 Subject: [PATCH 3/9] Fix leaked source paths in PRD validation report (#1481) Replace /src/core/ paths with {project-root}/_bmad/core/ convention in validation-report-prd-workflow.md lines 293-294. These paths reference party-mode and advanced-elicitation workflows using the source tree layout (/src/core/) instead of the installed layout ({project-root}/_bmad/core/) that Beta.4 standardized across all other files. This is the remaining half of the fix for #1435, which was closed as "will fix with .4 release" but only the brianmadison path on line 11 and the XML syntax issue were addressed. The /src/core/ paths on lines 293-294 were missed. Fixes #1480 --- .../create-prd/validation-report-prd-workflow.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/validation-report-prd-workflow.md b/src/bmm/workflows/2-plan-workflows/create-prd/validation-report-prd-workflow.md index 0a49b9f2..faa41ff6 100644 --- a/src/bmm/workflows/2-plan-workflows/create-prd/validation-report-prd-workflow.md +++ b/src/bmm/workflows/2-plan-workflows/create-prd/validation-report-prd-workflow.md @@ -290,8 +290,8 @@ editWorkflow: './steps-e/step-e-01-discovery.md' - ✅ Proper workflow path configuration **2. External Workflow References:** -- ✅ Party-mode workflow: Exists at `/src/core/workflows/party-mode/workflow.md` -- ✅ Advanced-elicitation task: Exists at `/src/core/workflows/advanced-elicitation/workflow.xml` +- ✅ Party-mode workflow: Exists at `{project-root}/_bmad/core/workflows/party-mode/workflow.md` +- ✅ Advanced-elicitation task: Exists at `{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml` **3. Directory Structure:** - ✅ Complete step architecture (all 3 modes) From c3d1bf3fe889a0bc9ea81bbf9cb951b674dc5811 Mon Sep 17 00:00:00 2001 From: Brian Madison Date: Sat, 31 Jan 2026 22:55:26 -0600 Subject: [PATCH 4/9] Fix duplicate 2-letter code - brainstorming now uses BSP - BS -> BSP (Brainstorming in core module) Resolves conflict with cis Brainstorming (BS). Core is for project brainstorming, cis is general brainstorming. --- src/core/module-help.csv | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/core/module-help.csv b/src/core/module-help.csv index 599cef33..1fdf064c 100644 --- a/src/core/module-help.csv +++ b/src/core/module-help.csv @@ -1,5 +1,5 @@ module,phase,name,code,sequence,workflow-file,command,required,agent,options,description,output-location,outputs -core,anytime,Brainstorming,BS,,_bmad/core/workflows/brainstorming/workflow.md,bmad-brainstorming,false,analyst,,"Generate diverse ideas through interactive techniques. Use early in ideation phase or when stuck generating ideas.",{output_folder}/brainstorming/brainstorming-session-{{date}}.md,, +core,anytime,Brainstorming,BSP,,_bmad/core/workflows/brainstorming/workflow.md,bmad-brainstorming,false,analyst,,"Generate diverse ideas through interactive techniques. Use early in ideation phase or when stuck generating ideas.",{output_folder}/brainstorming/brainstorming-session-{{date}}.md,, core,anytime,Party Mode,PM,,_bmad/core/workflows/party-mode/workflow.md,bmad-party-mode,false,party-mode facilitator,,"Orchestrate multi-agent discussions. Use when you need multiple agent perspectives or want agents to collaborate.",, core,anytime,bmad-help,BH,,_bmad/core/tasks/help.md,bmad-help,false,,,"Get unstuck by showing what workflow steps come next or answering BMad Method questions.",, core,anytime,Index Docs,ID,,_bmad/core/tasks/index-docs.xml,bmad-index-docs,false,,,"Create lightweight index for quick LLM scanning. Use when LLM needs to understand available docs without loading everything.",, From 0bbb544521b7e78fff9163082696a6c4a8bf0d78 Mon Sep 17 00:00:00 2001 From: Brian Madison Date: Sun, 1 Feb 2026 12:19:36 -0600 Subject: [PATCH 5/9] remove skills that are now part of a plugin installer --- .claude/skills/gh-triage/SKILL.md | 158 ------------------------------ .gitignore | 2 +- 2 files changed, 1 insertion(+), 159 deletions(-) delete mode 100644 .claude/skills/gh-triage/SKILL.md diff --git a/.claude/skills/gh-triage/SKILL.md b/.claude/skills/gh-triage/SKILL.md deleted file mode 100644 index 59795159..00000000 --- a/.claude/skills/gh-triage/SKILL.md +++ /dev/null @@ -1,158 +0,0 @@ ---- -name: gh-triage -description: Fetch all GitHub issues via gh CLI and use AI agents to deeply analyze, cluster, and prioritize issues with actual understanding. Use for issue triage, backlog cleanup, or when user mentions "issues", "triage", or "backlog". -license: MIT -disable-model-invocation: true -metadata: - author: bmad-code-org - version: "3.0.0" - anthropic-internal: Core team issue triage tool for BMad Method repositories - min-github-cli-version: "2.0" -compatibility: Requires gh CLI, git repository, and BMad Method with Task tool support ---- - -# GitHub Issue Triage with AI Analysis - -**CRITICAL RULES:** -- NEVER include time or effort estimates in output or recommendations -- Focus on WHAT needs to be done, not HOW LONG it takes -- Use Bash tool with gh CLI for all GitHub operations - -## Execution Plan - -You will perform GitHub issue triage using AI agents for deep analysis: - -### Step 1: Fetch Issues -Use `gh issue list` to fetch all open issues from the current repository in JSON format. - -### Step 2: Batch Creation -Split issues into batches of ~10 issues each for parallel analysis. - -### Step 3: Parallel Agent Analysis -For EACH batch, use the Task tool with `subagent_type=general-purpose` to launch an agent with this prompt: - -``` -You are analyzing a batch of GitHub issues for deep understanding and triage. - -**YOUR TASK:** -Read the issues in your batch and provide DEEP analysis: - -1. **For EACH issue, analyze:** - - What is this ACTUALLY about? (beyond keywords) - - What component/system does it affect? - - What's the impact and severity? - - Is it a bug, feature request, or something else? - - What specific theme does it belong to? - -2. **PRIORITY ASSESSMENT:** - - CRITICAL: Blocks users, security issues, data loss, broken installers - - HIGH: Major functionality broken, important features missing - - MEDIUM: Workarounds available, minor bugs, nice-to-have features - - LOW: Edge cases, cosmetic issues, questions - -3. **RELATIONSHIPS:** - - Duplicates: Near-identical issues about the same problem - - Related: Issues connected by theme or root cause - - Dependencies: One issue blocks or requires another - -**YOUR BATCH:** -[Paste the batch of issues here - each with number, title, body, labels] - -**OUTPUT FORMAT (JSON only, no markdown):** -{ - "issues": [ - { - "number": 123, - "title": "issue title", - "deep_understanding": "2-3 sentences explaining what this is really about", - "affected_components": ["installer", "workflows", "docs"], - "issue_type": "bug/feature/question/tech-debt", - "priority": "CRITICAL/HIGH/MEDIUM/LOW", - "priority_rationale": "Why this priority level", - "theme": "installation/workflow/integration/docs/ide-support/etc", - "relationships": { - "duplicates_of": [456], - "related_to": [789, 101], - "blocks": [111] - } - } - ], - "cross_repo_issues": [ - {"number": 123, "target_repo": "bmad-builder", "reason": "about agent builder"} - ], - "cleanup_candidates": [ - {"number": 456, "reason": "v4-related/outdated/duplicate"} - ], - "themes_found": { - "Installation Blockers": { - "count": 5, - "root_cause": "Common pattern if identifiable" - } - } -} - -Return ONLY valid JSON. No explanations outside the JSON structure. -``` - -### Step 4: Consolidate & Generate Report -After all agents complete, create a comprehensive markdown report saved to `_bmad-output/triage-reports/triage-YYYY-MM-DD.md` with: - -## Report Structure - -### Executive Summary -- Total issues analyzed -- Issue count by priority (CRITICAL, HIGH, MEDIUM, LOW) -- Major themes discovered -- Top 5 critical issues requiring immediate attention - -### Critical Issues (CRITICAL Priority) -For each CRITICAL issue: -- **#123 - [Issue Title](url)** -- **What it's about:** [Deep understanding] -- **Affected:** [Components] -- **Why Critical:** [Rationale] -- **Suggested Action:** [Specific action] - -### High Priority Issues (HIGH Priority) -Same format as Critical, grouped by theme. - -### Theme Clusters -For each major theme: -- **Theme Name** (N issues) -- **What connects these:** [Pattern] -- **Root cause:** [If identifiable] -- **Consolidated actions:** [Bulk actions if applicable] -- **Issues:** #123, #456, #789 - -### Relationships & Dependencies -- **Duplicates:** List pairs with `gh issue close` commands -- **Related Issues:** Groups of related issues -- **Dependencies:** Blocking relationships - -### Cross-Repo Issues -Issues that should be migrated to other repositories (bmad-builder, bmad-module-creative-intelligence-suite, bmad-module-game-dev-studio, bmad-method-test-architecture-enterprise). - -For each, provide: -``` -gh issue close XXX --repo CURRENT_REPO --comment "This issue belongs in REPO. Please report at https://github.com/TARGET_REPO/issues/new" -``` - -### Cleanup Candidates -- **v4-related:** Deprecated version issues with close commands -- **Stale:** No activity >30 days -- **Low priority + old:** Low priority issues >60 days old - -### Actionable Next Steps -Specific, prioritized actions: -1. [CRITICAL] Fix broken installer - affects all new users -2. [HIGH] Resolve Windows path escaping issues -3. [HIGH] Address workflow integration bugs -etc. - -Include `gh` commands where applicable for bulk actions. - ---- - -## Execute Now - -Begin by fetching issues from the current repository and follow the plan above. diff --git a/.gitignore b/.gitignore index 6af83303..885cb245 100644 --- a/.gitignore +++ b/.gitignore @@ -50,7 +50,7 @@ _bmad-output .qwen .rovodev .kilocodemodes -.claude/commands +.claude .codex .github/chatmodes .github/agents From fa01b4929b94bc2c409ace0b21c05fd4e74189ff Mon Sep 17 00:00:00 2001 From: Brian Madison Date: Sun, 1 Feb 2026 16:01:29 -0600 Subject: [PATCH 6/9] add helper skills --- .claude/skills/draft-changelog/SKILL.md | 7 ++ .../draft-changelog/prompts/instructions.md | 58 +++++++++++++++ .claude/skills/gh-triage/README.md | 14 ++++ .claude/skills/gh-triage/SKILL.md | 12 +++ .../skills/gh-triage/prompts/agent-prompt.md | 60 +++++++++++++++ .../skills/gh-triage/prompts/instructions.md | 74 +++++++++++++++++++ .claude/skills/release-module/README.md | 24 ++++++ .claude/skills/release-module/SKILL.md | 7 ++ .../release-module/prompts/instructions.md | 57 ++++++++++++++ .gitignore | 2 +- 10 files changed, 314 insertions(+), 1 deletion(-) create mode 100644 .claude/skills/draft-changelog/SKILL.md create mode 100644 .claude/skills/draft-changelog/prompts/instructions.md create mode 100644 .claude/skills/gh-triage/README.md create mode 100644 .claude/skills/gh-triage/SKILL.md create mode 100644 .claude/skills/gh-triage/prompts/agent-prompt.md create mode 100644 .claude/skills/gh-triage/prompts/instructions.md create mode 100644 .claude/skills/release-module/README.md create mode 100644 .claude/skills/release-module/SKILL.md create mode 100644 .claude/skills/release-module/prompts/instructions.md diff --git a/.claude/skills/draft-changelog/SKILL.md b/.claude/skills/draft-changelog/SKILL.md new file mode 100644 index 00000000..f25f8c48 --- /dev/null +++ b/.claude/skills/draft-changelog/SKILL.md @@ -0,0 +1,7 @@ +--- +name: draft-changelog +description: Analyzes changes since the last release and generates a draft changelog entry +disable-model-invocation: true +--- + +Read `prompts/instructions.md` and execute. diff --git a/.claude/skills/draft-changelog/prompts/instructions.md b/.claude/skills/draft-changelog/prompts/instructions.md new file mode 100644 index 00000000..a9b98bb8 --- /dev/null +++ b/.claude/skills/draft-changelog/prompts/instructions.md @@ -0,0 +1,58 @@ +# Draft Changelog Execution + +## Input +Project path (or run from project root) + +## Step 1: Identify Current State +- Get the latest released tag +- Get current version +- Verify there are commits since the last release + +## Step 2: Launch Explore Agent + +Use `thoroughness: "very thorough"` to analyze all changes since the last release tag. + +**Key: For each merge commit, look up the merged PR/issue that was closed.** +- Use `gh pr view` or git commit body to find the PR number +- Read the PR description and comments to understand full context +- Don't rely solely on commit merge messages - they lack context + +**Analyze:** + +1. **All merges/commits** since the last tag +2. **For each merge, read the original PR/issue** that was closed +3. **Files changed** with statistics +4. **Categorize changes:** + - 🎁 **Features** - New functionality, new agents, new workflows + - 🐛 **Bug Fixes** - Fixed bugs, corrected issues + - ♻️ **Refactoring** - Code improvements, reorganization + - 📚 **Documentation** - Docs updates, README changes + - 🔧 **Maintenance** - Dependency updates, tooling, infrastructure + - 💥 **Breaking Changes** - Changes that may affect users + +**Provide:** +- Comprehensive summary of ALL changes with PR context +- Categorization of each change +- Identification of breaking changes +- Significance assessment (major/minor/trivial) + +## Step 3: Generate Draft Changelog + +Format: +```markdown +## v0.X.X - [Date] + +* [Change 1 - categorized by type] +* [Change 2] +``` + +Guidelines: +- Present tense ("Fix bug" not "Fixed bug") +- Most significant changes first +- Group related changes +- Clear, concise language +- For breaking changes, clearly indicate impact + +## Step 4: Present Draft + +Show the draft with current version, last tag, commit count, and options to edit/retry. diff --git a/.claude/skills/gh-triage/README.md b/.claude/skills/gh-triage/README.md new file mode 100644 index 00000000..3692e3d2 --- /dev/null +++ b/.claude/skills/gh-triage/README.md @@ -0,0 +1,14 @@ +# gh-triage + +Fetches all GitHub issues via gh CLI and uses AI agents to deeply analyze, cluster, and prioritize issues. + +## Usage + +Run from within any BMad Method repository to triage issues. + +## What It Does + +1. Fetches all open issues via `gh issue list` +2. Splits issues into batches +3. Launches parallel agents to analyze each batch +4. Generates comprehensive triage report to `_bmad-output/triage-reports/` diff --git a/.claude/skills/gh-triage/SKILL.md b/.claude/skills/gh-triage/SKILL.md new file mode 100644 index 00000000..6a6d7c83 --- /dev/null +++ b/.claude/skills/gh-triage/SKILL.md @@ -0,0 +1,12 @@ +--- +name: gh-triage +description: Fetch all GitHub issues via gh CLI and use AI agents to deeply analyze, cluster, and prioritize issues +license: MIT +disable-model-invocation: true +metadata: + author: bmad-code-org + version: "3.0.0" +compatibility: Requires gh CLI, git repository, and BMad Method with Task tool support +--- + +Read `prompts/instructions.md` and execute. diff --git a/.claude/skills/gh-triage/prompts/agent-prompt.md b/.claude/skills/gh-triage/prompts/agent-prompt.md new file mode 100644 index 00000000..5c0d7d8d --- /dev/null +++ b/.claude/skills/gh-triage/prompts/agent-prompt.md @@ -0,0 +1,60 @@ +You are analyzing a batch of GitHub issues for deep understanding and triage. + +**YOUR TASK:** +Read the issues in your batch and provide DEEP analysis: + +1. **For EACH issue, analyze:** + - What is this ACTUALLY about? (beyond keywords) + - What component/system does it affect? + - What's the impact and severity? + - Is it a bug, feature request, or something else? + - What specific theme does it belong to? + +2. **PRIORITY ASSESSMENT:** + - CRITICAL: Blocks users, security issues, data loss, broken installers + - HIGH: Major functionality broken, important features missing + - MEDIUM: Workarounds available, minor bugs, nice-to-have features + - LOW: Edge cases, cosmetic issues, questions + +3. **RELATIONSHIPS:** + - Duplicates: Near-identical issues about the same problem + - Related: Issues connected by theme or root cause + - Dependencies: One issue blocks or requires another + +**YOUR BATCH:** +[Paste the batch of issues here - each with number, title, body, labels] + +**OUTPUT FORMAT (JSON only, no markdown):** +{ + "issues": [ + { + "number": 123, + "title": "issue title", + "deep_understanding": "2-3 sentences explaining what this is really about", + "affected_components": ["installer", "workflows", "docs"], + "issue_type": "bug/feature/question/tech-debt", + "priority": "CRITICAL/HIGH/MEDIUM/LOW", + "priority_rationale": "Why this priority level", + "theme": "installation/workflow/integration/docs/ide-support/etc", + "relationships": { + "duplicates_of": [456], + "related_to": [789, 101], + "blocks": [111] + } + } + ], + "cross_repo_issues": [ + {"number": 123, "target_repo": "bmad-builder", "reason": "about agent builder"} + ], + "cleanup_candidates": [ + {"number": 456, "reason": "v4-related/outdated/duplicate"} + ], + "themes_found": { + "Installation Blockers": { + "count": 5, + "root_cause": "Common pattern if identifiable" + } + } +} + +Return ONLY valid JSON. No explanations outside the JSON structure. diff --git a/.claude/skills/gh-triage/prompts/instructions.md b/.claude/skills/gh-triage/prompts/instructions.md new file mode 100644 index 00000000..782d2326 --- /dev/null +++ b/.claude/skills/gh-triage/prompts/instructions.md @@ -0,0 +1,74 @@ +# GitHub Issue Triage with AI Analysis + +**CRITICAL RULES:** +- NEVER include time or effort estimates in output or recommendations +- Focus on WHAT needs to be done, not HOW LONG it takes +- Use Bash tool with gh CLI for all GitHub operations + +## Execution + +### Step 1: Fetch Issues +Use `gh issue list --json number,title,body,labels` to fetch all open issues. + +### Step 2: Batch Creation +Split issues into batches of ~10 issues each for parallel analysis. + +### Step 3: Parallel Agent Analysis +For EACH batch, use the Task tool with `subagent_type=general-purpose` to launch an agent with prompt from `prompts/agent-prompt.md` + +### Step 4: Consolidate & Generate Report +After all agents complete, create a comprehensive markdown report saved to `_bmad-output/triage-reports/triage-YYYY-MM-DD.md` + +## Report Format + +### Executive Summary +- Total issues analyzed +- Issue count by priority (CRITICAL, HIGH, MEDIUM, LOW) +- Major themes discovered +- Top 5 critical issues requiring immediate attention + +### Critical Issues (CRITICAL Priority) +For each CRITICAL issue: +- **#123 - [Issue Title](url)** +- **What it's about:** [Deep understanding] +- **Affected:** [Components] +- **Why Critical:** [Rationale] +- **Suggested Action:** [Specific action] + +### High Priority Issues (HIGH Priority) +Same format as Critical, grouped by theme. + +### Theme Clusters +For each major theme: +- **Theme Name** (N issues) +- **What connects these:** [Pattern] +- **Root cause:** [If identifiable] +- **Consolidated actions:** [Bulk actions if applicable] +- **Issues:** #123, #456, #789 + +### Relationships & Dependencies +- **Duplicates:** List pairs with `gh issue close` commands +- **Related Issues:** Groups of related issues +- **Dependencies:** Blocking relationships + +### Cross-Repo Issues +Issues that should be migrated to other repositories. + +For each, provide: +``` +gh issue close XXX --repo CURRENT_REPO --comment "This issue belongs in REPO. Please report at https://github.com/TARGET_REPO/issues/new" +``` + +### Cleanup Candidates +- **v4-related:** Deprecated version issues with close commands +- **Stale:** No activity >30 days +- **Low priority + old:** Low priority issues >60 days old + +### Actionable Next Steps +Specific, prioritized actions: +1. [CRITICAL] Fix broken installer - affects all new users +2. [HIGH] Resolve Windows path escaping issues +3. [HIGH] Address workflow integration bugs +etc. + +Include `gh` commands where applicable for bulk actions. diff --git a/.claude/skills/release-module/README.md b/.claude/skills/release-module/README.md new file mode 100644 index 00000000..5dbaf254 --- /dev/null +++ b/.claude/skills/release-module/README.md @@ -0,0 +1,24 @@ +# release-module + +Automates the complete release process for npm modules. + +## Usage + +Run from project root or pass project path: +``` +bmad-utility-skills:release-module +``` + +## Prerequisite + +First run `draft-changelog` to analyze changes and create a draft changelog. + +## What It Does + +1. Gets and confirms changelog entry +2. Confirms version bump type (patch/minor/major) +3. Updates CHANGELOG.md +4. Bumps version with `npm version` +5. Pushes git tag +6. Publishes to npm +7. Creates GitHub release diff --git a/.claude/skills/release-module/SKILL.md b/.claude/skills/release-module/SKILL.md new file mode 100644 index 00000000..3ba15657 --- /dev/null +++ b/.claude/skills/release-module/SKILL.md @@ -0,0 +1,7 @@ +--- +name: release-module +description: Automates the complete release process for npm modules - version bump, changelog, git tag, npm publish, GitHub release +disable-model-invocation: true +--- + +Read `prompts/instructions.md` and execute. diff --git a/.claude/skills/release-module/prompts/instructions.md b/.claude/skills/release-module/prompts/instructions.md new file mode 100644 index 00000000..b026ed2d --- /dev/null +++ b/.claude/skills/release-module/prompts/instructions.md @@ -0,0 +1,57 @@ +# Release BMad Module Execution + +## Input +Project path (or run from project root) + +## Execution Steps + +### Step 1: Get Current State +- Verify git working tree is clean +- Get latest tag and current version +- Check for unpushed commits + +### Step 2: Get Changelog Entry + +Ask the user for the changelog entry (from draft-changelog skill or manual). + +### Step 3: Confirm Changelog + +Show project name, current version, proposed next version, and changelog. Get confirmation. + +### Step 4: Confirm Version Bump Type + +Ask what type of bump: patch, minor, major, prerelease, or custom. + +### Step 5: Update CHANGELOG.md + +Insert new entry at top, commit, and push. + +### Step 6: Bump Version + +Run `npm version` to update package.json, create commit, and create tag. + +### Step 7: Push Tag + +Push the new version tag to GitHub. + +### Step 8: Publish to npm + +Publish the package. + +### Step 9: Create GitHub Release + +Create release with changelog notes using `gh release create`. + +### Step 10: Confirm Completion + +Show npm and GitHub links. + +## Error Handling + +Stop immediately on any step failure. Inform user and suggest fix. + +## Important Notes + +- Wait for user confirmation before destructive operations +- Push changelog commit before version bump +- Use explicit directory paths in commands diff --git a/.gitignore b/.gitignore index 885cb245..6af83303 100644 --- a/.gitignore +++ b/.gitignore @@ -50,7 +50,7 @@ _bmad-output .qwen .rovodev .kilocodemodes -.claude +.claude/commands .codex .github/chatmodes .github/agents From 79067a94275df6ef34b1ca0d32667e15eb15c694 Mon Sep 17 00:00:00 2001 From: Brian Madison Date: Sun, 1 Feb 2026 16:13:15 -0600 Subject: [PATCH 7/9] changelog: v6.0.0-Beta.5 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ### 🎁 Features * Add generate-project-context workflow * Shard market research customer analysis ### 🐛 Bug Fixes * Fix npm install peer dependency issues (PR #1476) * Fix leaked source paths in PRD validation report (#1481) * Fix orphaned market research customer analysis (#1486) * Fix duplicate 2-letter brainstorming code (BS → BSP) * Fix tech writer sidecar functionality (#1487) * Fix relative paths in workflow steps (#1497, #1498) * Fix party-mode workflow file extension (#1499) * Fix generated slash commands (#1501) * Fix agent scan and help CSV files * Fix HELP_STEP placeholder replacement (#1437) ### 📚 Documentation * Add exact slash commands to Getting Started guide (#1505) * Remove .claude/commands from version control (#1506) ### 🔧 Maintenance * Update Starlight to 0.37.5 * Add GitHub issue templates --- CHANGELOG.md | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 953a4664..2420869b 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,37 @@ # Changelog +## [6.0.0-Beta.5] + +### 🎁 Features + +* **Add generate-project-context workflow** — New 3-step workflow for project context generation, integrated with quick-flow-solo-dev agent +* **Shard market research customer analysis** — Refactor monolithic customer insights into 4-step detailed customer behavior analysis workflow + +### 🐛 Bug Fixes + +* **Fix npm install peer dependency issues** — Add `.npmrc` with `legacy-peer-deps=true`, update Starlight to 0.37.5, and add `--legacy-peer-deps` flag to module installer (PR #1476) +* **Fix leaked source paths in PRD validation report** — Replace absolute `/src/core/` paths with `{project-root}/_bmad/core/` (#1481) +* **Fix orphaned market research customer analysis** — Connect step-01-init to step-02-customer-behavior to complete workflow sharding (#1486) +* **Fix duplicate 2-letter brainstorming code** — Change BS to BSP to resolve conflict with cis Brainstorming module +* **Fix tech writer sidecar functionality** — Enable proper sidecar operation (#1487) +* **Fix relative paths in workflow steps** — Correct paths in step-11-polish (#1497) and step-e-04-complete (#1498) +* **Fix party-mode workflow file extension** — Correct extension in workflow.xml (#1499) +* **Fix generated slash commands** — Add `disable-model-invocation` to all generated commands (#1501) +* **Fix agent scan and help CSV files** — Correct module-help.csv entries +* **Fix HELP_STEP placeholder replacement** — Fix placeholder not replaced in compiled agents, fix hardcoded path, fix single quote (#1437) + +### 📚 Documentation + +* **Add exact slash commands to Getting Started guide** — Provide precise command examples for users (#1505) +* **Remove .claude/commands from version control** — Commands are generated, not tracked (#1506) + +### 🔧 Maintenance + +* **Update Starlight to 0.37.5** — Latest version with peer dependency compatibility +* **Add GitHub issue templates** — New bug-report.yaml and documentation.yaml templates + +--- + ## [6.0.0-Beta.4] ### 🐛 Bug Fixes From 0c46ef0be2521ceeefed5de7a7e82422a8ae4567 Mon Sep 17 00:00:00 2001 From: Brian Madison Date: Sun, 1 Feb 2026 16:13:27 -0600 Subject: [PATCH 8/9] 6.0.0-Beta.5 --- package-lock.json | 4 ++-- package.json | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/package-lock.json b/package-lock.json index b5f966e7..fe41085b 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "bmad-method", - "version": "6.0.0-Beta.4", + "version": "6.0.0-Beta.5", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "bmad-method", - "version": "6.0.0-Beta.4", + "version": "6.0.0-Beta.5", "license": "MIT", "dependencies": { "@clack/prompts": "^0.11.0", diff --git a/package.json b/package.json index 76f24133..f3342a41 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "$schema": "https://json.schemastore.org/package.json", "name": "bmad-method", - "version": "6.0.0-Beta.4", + "version": "6.0.0-Beta.5", "description": "Breakthrough Method of Agile AI-driven Development", "keywords": [ "agile", From b0c35d595f64a4cdd4b60181b87ed5e2b5b11479 Mon Sep 17 00:00:00 2001 From: Brian Madison Date: Sun, 1 Feb 2026 16:59:43 -0600 Subject: [PATCH 9/9] social post skill helper --- .claude/skills/changelog-social/SKILL.md | 168 ++++++++++++++++++ .../release-module/prompts/instructions.md | 20 ++- 2 files changed, 186 insertions(+), 2 deletions(-) create mode 100644 .claude/skills/changelog-social/SKILL.md diff --git a/.claude/skills/changelog-social/SKILL.md b/.claude/skills/changelog-social/SKILL.md new file mode 100644 index 00000000..02ee2ae0 --- /dev/null +++ b/.claude/skills/changelog-social/SKILL.md @@ -0,0 +1,168 @@ +--- +name: changelog-social +description: Generate social media announcements for Discord and Twitter from the latest changelog entry.asks to create release announcements, social posts, or share changelog updates on Discord/Twitter. Reads CHANGELOG.md in current working directory. +disable-model-invocation: true +--- + +# Changelog Social + +Generate engaging social media announcements from changelog entries. + +## Workflow + +### Step 1: Extract Changelog Entry + +Read `./CHANGELOG.md` and extract the latest version entry. The changelog follows this format: + +```markdown +## [VERSION] + +### 🎁 Features +* **Title** — Description + +### 🐛 Bug Fixes +* **Title** — Description + +### 📚 Documentation +* **Title** — Description + +### 🔧 Maintenance +* **Title** — Description +``` + +Parse: +- **Version number** (e.g., `6.0.0-Beta.5`) +- **Features** - New functionality, enhancements +- **Bug Fixes** - Fixes users will care about +- **Documentation** - New or improved docs +- **Maintenance** - Dependency updates, tooling improvements + +### Step 2: Get Git Contributors + +Use git log to find contributors since the previous version. Get commits between the current version tag and the previous one: + +```bash +# Find the previous version tag first +git tag --sort=-version:refname | head -5 + +# Get commits between versions with PR numbers and authors +git log .. --pretty=format:"%h|%s|%an" --grep="#" +``` + +Extract PR numbers from commit messages that contain `#` followed by digits. Compile unique contributors. + +### Step 3: Generate Discord Announcement + +Use this template style: + +```markdown +🚀 **BMad vVERSION RELEASED!** + +🎉 [Brief hype sentence] + +🪥 **KEY HIGHLIGHT** - [One-line summary] + +🎯 **CATEGORY NAME** +• Feature one - brief description +• Feature two - brief description +• Coming soon: Future teaser + +🔧 **ANOTHER CATEGORY** +• Fix or feature +• Another item + +📚 **DOCS OR OTHER** +• Item +• Item with link + +🌟 **COMMUNITY PHILOSOPHY** (optional - include for major releases) +• Everything is FREE - No paywalls +• Knowledge shared, not sold + +📊 **STATS** +X commits | Y PRs merged | Z files changed + +🙏 **CONTRIBUTORS** +@username1 (X PRs!), @username2 (Y PRs!) +@username3, @username4, username5 + dependabot 🛡️ +Community-driven FTW! 🌟 + +📦 **INSTALL:** +`npx bmad-method@VERSION install` + +⭐ **SUPPORT US:** +🌟 GitHub: github.com/bmad-code-org/BMAD-METHOD/ +📺 YouTube: youtube.com/@BMadCode +☕ Donate: buymeacoffee.com/bmad + +🔥 **Next version tease!** +``` + +**Content Strategy:** +- Focus on **user impact** - what's better for them? +- Highlight **annoying bugs fixed** that frustrated users +- Show **new capabilities** that enable workflows +- Keep it **punchy** - use emojis and short bullets +- Add **personality** - excitement, humor, gratitude + +### Step 4: Generate Twitter Post + +Create a condensed version (280 chars or less for main tweet, optionally thread): + +``` +🚀 BMad vVERSION is live! + +[Most exciting feature] + [Critical bug fix] + +• Feature 1 +• Feature 2 +• Fix 3 + +Install: npx bmad-method@VERSION install + +#AI #DevTools +``` + +**For major releases**, create a thread: +1. Hook tweet - biggest news +2. Feature highlights tweet +3. Community/contributors tweet +4. Install CTA + +## Content Selection Guidelines + +**Include:** +- New features that change workflows +- Bug fixes for annoying/blocking issues +- Documentation that helps users +- Performance improvements +- New agents or workflows +- Breaking changes (call out clearly) + +**Skip/Minimize:** +- Internal refactoring +- Dependency updates (unless user-facing) +- Test improvements +- Minor style fixes + +**Emphasize:** +- "Finally fixed" issues +- "Faster" operations +- "Easier" workflows +- "Now supports" capabilities + +## Output Format + +Present both announcements in clearly labeled sections: + +```markdown +## Discord Announcement + +[paste Discord content here] + +## Twitter Post + +[paste Twitter content here] +``` + +Offer to make adjustments if the user wants different emphasis, tone, or content. diff --git a/.claude/skills/release-module/prompts/instructions.md b/.claude/skills/release-module/prompts/instructions.md index b026ed2d..39e45ac1 100644 --- a/.claude/skills/release-module/prompts/instructions.md +++ b/.claude/skills/release-module/prompts/instructions.md @@ -42,9 +42,25 @@ Publish the package. Create release with changelog notes using `gh release create`. -### Step 10: Confirm Completion +### Step 10: Create Social Announcement -Show npm and GitHub links. +Create a social media announcement file at `_bmad-output/social/{repo-name}-release.md`. + +Format: +```markdown +# {name} v{version} Released + +## Highlights +{2-3 bullet points of key features/changes} + +## Links +- GitHub: {release-url} +- npm: {npm-url} +``` + +### Step 11: Confirm Completion + +Show npm, GitHub, and social announcement file paths. ## Error Handling