bmad-fh 6.0.0-alpha.23

package/.coderabbit.yaml

@@ -0,0 +1,40 @@
+# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
+
+language: "en-US"
+early_access: true
+reviews:
+  profile: chill
+  high_level_summary: false # don't post summary until explicitly invoked
+  request_changes_workflow: false
+  review_status: false
+  commit_status: false
+  walkthrough: false
+  poem: false
+  auto_review:
+    enabled: true
+    drafts: false # Don't review drafts automatically
+    auto_incremental_review: false # always review the whole PR, not just new commits
+    base_branches:
+      - main
+  path_filters:
+    - "!**/node_modules/**"
+  path_instructions:
+    - path: "**/*"
+      instructions: |
+        Focus on inconsistencies, contradictions, edge cases and serious issues.
+        Avoid commenting on minor issues such as linting, formatting and style issues.
+        When providing code suggestions, use GitHub's suggestion format:
+        ```suggestion
+        <code changes>
+        ```
+    - path: "**/*.js"
+      instructions: |
+        CLI tooling code. Check for: missing error handling on fs operations,
+        path.join vs string concatenation, proper cleanup in error paths.
+        Flag any process.exit() without error message.
+chat:
+  auto_reply: true # Response to mentions in comments, a la @coderabbit review
+issue_enrichment:
+  auto_enrich:
+    enabled: false # don't auto-comment on issues
+

package/.githooks/post-checkout

@@ -0,0 +1,129 @@
+#!/bin/bash
+# .githooks/post-checkout
+# Git hook for BMAD-METHOD contributors to provide sync reminders
+#
+# This hook provides helpful reminders when:
+# 1. Switching to main branch
+# 2. Switching from main to feature branch
+# 3. Creating new branches
+
+# Color codes for output
+RED='\033[0;31m'
+YELLOW='\033[1;33m'
+GREEN='\033[0;32m'
+BLUE='\033[0;34m'
+NC='\033[0m' # No Color
+
+# Configuration
+UPSTREAM_REMOTE="upstream"
+MAIN_BRANCH="main"
+
+# Arguments passed by git
+# $1: ref of previous HEAD
+# $2: ref of new HEAD
+# $3: flag indicating branch checkout (1) or file checkout (0)
+PREV_HEAD=$1
+NEW_HEAD=$2
+BRANCH_CHECKOUT=$3
+
+# Only run for branch checkouts, not file checkouts
+if [ "$BRANCH_CHECKOUT" != "1" ]; then
+    exit 0
+fi
+
+# Get branch names
+NEW_BRANCH=$(git branch --show-current)
+PREV_BRANCH=$(git reflog -1 | grep -oP 'moving from \K[^ ]+' || echo "")
+
+# Skip if we couldn't determine branches
+if [ -z "$NEW_BRANCH" ]; then
+    exit 0
+fi
+
+echo -e "${BLUE}[post-checkout] Switched to branch: $NEW_BRANCH${NC}"
+
+# Check if upstream remote exists
+HAS_UPSTREAM=false
+if git remote | grep -q "^${UPSTREAM_REMOTE}$"; then
+    HAS_UPSTREAM=true
+fi
+
+# Case 1: Switched TO main branch
+if [ "$NEW_BRANCH" = "$MAIN_BRANCH" ]; then
+    echo ""
+    if [ "$HAS_UPSTREAM" = true ]; then
+        # Check if main is behind upstream
+        git fetch "$UPSTREAM_REMOTE" --quiet 2>/dev/null || true
+        LOCAL_MAIN=$(git rev-parse "$MAIN_BRANCH" 2>/dev/null || echo "")
+        UPSTREAM_MAIN=$(git rev-parse "${UPSTREAM_REMOTE}/${MAIN_BRANCH}" 2>/dev/null || echo "")
+        
+        if [ -n "$LOCAL_MAIN" ] && [ -n "$UPSTREAM_MAIN" ]; then
+            if [ "$LOCAL_MAIN" != "$UPSTREAM_MAIN" ]; then
+                if git merge-base --is-ancestor "$LOCAL_MAIN" "$UPSTREAM_MAIN"; then
+                    echo -e "${YELLOW}💡 Your local '$MAIN_BRANCH' is behind upstream${NC}"
+                    echo -e "${YELLOW}   Sync with: git pull $UPSTREAM_REMOTE $MAIN_BRANCH${NC}"
+                elif ! git merge-base --is-ancestor "$UPSTREAM_MAIN" "$LOCAL_MAIN"; then
+                    echo -e "${RED}⚠️  Your local '$MAIN_BRANCH' has diverged from upstream${NC}"
+                    echo -e "${YELLOW}   Reset with: git reset --hard $UPSTREAM_REMOTE/$MAIN_BRANCH${NC}"
+                else
+                    echo -e "${GREEN}✓ Your local '$MAIN_BRANCH' is synced with upstream${NC}"
+                fi
+            else
+                echo -e "${GREEN}✓ Your local '$MAIN_BRANCH' is synced with upstream${NC}"
+            fi
+        fi
+    else
+        echo -e "${YELLOW}💡 Tip: Add upstream remote for easier syncing:${NC}"
+        echo -e "   git remote add $UPSTREAM_REMOTE git@github.com:bmad-code-org/BMAD-METHOD.git"
+    fi
+    echo ""
+fi
+
+# Case 2: Switched FROM main to feature branch
+if [ "$PREV_BRANCH" = "$MAIN_BRANCH" ] && [ "$NEW_BRANCH" != "$MAIN_BRANCH" ]; then
+    echo ""
+    if [ "$HAS_UPSTREAM" = true ]; then
+        # Check if current branch is based on latest main
+        MERGE_BASE=$(git merge-base "$NEW_BRANCH" "$MAIN_BRANCH" 2>/dev/null || echo "")
+        MAIN_HEAD=$(git rev-parse "$MAIN_BRANCH" 2>/dev/null || echo "")
+        
+        if [ -n "$MERGE_BASE" ] && [ -n "$MAIN_HEAD" ] && [ "$MERGE_BASE" != "$MAIN_HEAD" ]; then
+            echo -e "${YELLOW}💡 This branch may need rebasing on latest '$MAIN_BRANCH'${NC}"
+            echo -e "   Rebase with: git rebase $MAIN_BRANCH"
+        fi
+    fi
+    
+    # Remind about single-commit workflow
+    COMMIT_COUNT=$(git rev-list --count "${MAIN_BRANCH}..${NEW_BRANCH}" 2>/dev/null || echo "0")
+    if [ "$COMMIT_COUNT" -gt 1 ]; then
+        echo -e "${YELLOW}💡 This branch has $COMMIT_COUNT commits${NC}"
+        echo -e "${YELLOW}   Remember to maintain single-commit workflow before pushing${NC}"
+        echo -e "   Squash with: git reset --soft $MAIN_BRANCH && git commit"
+    fi
+    echo ""
+fi
+
+# Case 3: Creating a new branch (both refs are the same)
+if [ "$PREV_HEAD" = "$NEW_HEAD" ] && [ "$PREV_BRANCH" != "$NEW_BRANCH" ]; then
+    echo ""
+    echo -e "${GREEN}✓ New branch created: $NEW_BRANCH${NC}"
+    echo -e "${BLUE}💡 Remember the single-commit workflow:${NC}"
+    echo -e "   1. Make your changes"
+    echo -e "   2. Commit once: git commit -m 'feat: description'"
+    echo -e "   3. Update with: git commit --amend (not new commits)"
+    echo -e "   4. Push with: git push --force-with-lease"
+    echo ""
+fi
+
+# General reminder for feature branches (not main)
+if [ "$NEW_BRANCH" != "$MAIN_BRANCH" ]; then
+    # Check if hooks are configured
+    CURRENT_HOOKS_PATH=$(git config core.hooksPath || echo "")
+    if [ "$CURRENT_HOOKS_PATH" != ".githooks" ]; then
+        echo -e "${YELLOW}💡 Tip: Enable git hooks with:${NC}"
+        echo -e "   git config core.hooksPath .githooks"
+        echo ""
+    fi
+fi
+
+exit 0

package/.githooks/pre-commit

@@ -0,0 +1,63 @@
+#!/bin/bash
+# .githooks/pre-commit
+# Git hook for BMAD-METHOD contributors to enforce clean commit practices
+#
+# This hook ensures:
+# 1. No direct commits to main
+# 2. Provides guidance on amend workflow
+
+set -e
+
+# Color codes for output
+RED='\033[0;31m'
+YELLOW='\033[1;33m'
+GREEN='\033[0;32m'
+BLUE='\033[0;34m'
+NC='\033[0m' # No Color
+
+# Configuration
+MAIN_BRANCH="main"
+
+# Get current branch
+CURRENT_BRANCH=$(git branch --show-current)
+
+# 1. Block commits to main
+if [ "$CURRENT_BRANCH" = "$MAIN_BRANCH" ]; then
+    echo -e "${RED}❌ ERROR: Direct commits to '$MAIN_BRANCH' are not allowed!${NC}"
+    echo ""
+    echo -e "${YELLOW}The main branch should only be updated by syncing with upstream.${NC}"
+    echo -e "${YELLOW}To work on changes:${NC}"
+    echo -e "  1. Create a feature branch: git checkout -b feat/your-feature"
+    echo -e "  2. Make your changes"
+    echo -e "  3. Commit: git commit -m 'feat: your feature description'"
+    echo -e "  4. Push: git push -u origin feat/your-feature"
+    exit 1
+fi
+
+# 2. Check if this is an amend
+if [ -f ".git/COMMIT_EDITMSG" ]; then
+    # Get the count of commits ahead of main
+    COMMIT_COUNT=$(git rev-list --count "${MAIN_BRANCH}..${CURRENT_BRANCH}" 2>/dev/null || echo "0")
+    
+    # If we have exactly 1 commit and user is making another commit (not amending),
+    # suggest using amend instead
+    if [ "$COMMIT_COUNT" -eq 1 ] && [ -z "$GIT_REFLOG_ACTION" ]; then
+        # Check if this is likely a new commit (not an amend)
+        # by seeing if the commit message is being edited
+        if ! git diff --cached --quiet; then
+            echo -e "${BLUE}[pre-commit] Info: You have 1 commit on this branch${NC}"
+            echo -e "${YELLOW}💡 Tip: Consider using 'git commit --amend' to update your existing commit${NC}"
+            echo -e "${YELLOW}   This maintains the single-commit-per-branch workflow.${NC}"
+            echo ""
+            echo -e "${YELLOW}To amend:${NC}"
+            echo -e "  git add <your-files>"
+            echo -e "  git commit --amend"
+            echo ""
+            echo -e "${YELLOW}Proceeding with new commit...${NC}"
+            # This is just a helpful tip, not blocking
+        fi
+    fi
+fi
+
+echo -e "${GREEN}✓ Pre-commit checks passed${NC}"
+exit 0

package/.githooks/pre-push

@@ -0,0 +1,135 @@
+#!/bin/bash
+# .githooks/pre-push
+# Git hook for BMAD-METHOD contributors to enforce clean git workflow
+#
+# This hook ensures:
+# 1. Upstream remote is configured
+# 2. No direct pushes to main
+# 3. Local main is synced with upstream
+# 4. Branch is rebased on main
+# 5. Single-commit-per-branch workflow
+
+set -e
+
+# Color codes for output
+RED='\033[0;31m'
+YELLOW='\033[1;33m'
+GREEN='\033[0;32m'
+BLUE='\033[0;34m'
+NC='\033[0m' # No Color
+
+# Configuration
+UPSTREAM_REMOTE="upstream"
+UPSTREAM_URL="git@github.com:bmad-code-org/BMAD-METHOD.git"
+MAIN_BRANCH="main"
+
+echo -e "${BLUE}[pre-push] Running pre-push checks...${NC}"
+
+# Get current branch
+CURRENT_BRANCH=$(git branch --show-current)
+
+# Read push details from stdin (remote and url)
+while read local_ref local_sha remote_ref remote_sha; do
+    # Extract branch name from ref
+    if [[ "$remote_ref" =~ refs/heads/(.+) ]]; then
+        PUSH_BRANCH="${BASH_REMATCH[1]}"
+    else
+        continue
+    fi
+    
+    # 1. Block direct push to main
+    if [ "$PUSH_BRANCH" = "$MAIN_BRANCH" ]; then
+        echo -e "${RED}❌ ERROR: Direct push to '$MAIN_BRANCH' is not allowed!${NC}"
+        echo -e "${YELLOW}The main branch should only be updated by syncing with upstream.${NC}"
+        echo -e "${YELLOW}To update main, run:${NC}"
+        echo -e "  git checkout main && git pull upstream main"
+        exit 1
+    fi
+done
+
+# 2. Ensure upstream remote exists
+if ! git remote | grep -q "^${UPSTREAM_REMOTE}$"; then
+    echo -e "${RED}❌ ERROR: Upstream remote '${UPSTREAM_REMOTE}' not configured!${NC}"
+    echo -e "${YELLOW}Add it with:${NC}"
+    echo -e "  git remote add ${UPSTREAM_REMOTE} ${UPSTREAM_URL}"
+    exit 1
+fi
+
+# Verify upstream URL
+CURRENT_UPSTREAM=$(git remote get-url "$UPSTREAM_REMOTE" 2>/dev/null || echo "")
+if [[ "$CURRENT_UPSTREAM" != *"bmad-code-org/BMAD-METHOD"* ]]; then
+    echo -e "${YELLOW}⚠️  WARNING: Upstream remote doesn't point to bmad-code-org/BMAD-METHOD${NC}"
+    echo -e "${YELLOW}Current: $CURRENT_UPSTREAM${NC}"
+    echo -e "${YELLOW}Expected: ${UPSTREAM_URL}${NC}"
+fi
+
+# 3. Fetch upstream
+echo -e "${BLUE}Fetching upstream...${NC}"
+if ! git fetch "$UPSTREAM_REMOTE" --quiet 2>/dev/null; then
+    echo -e "${RED}❌ ERROR: Failed to fetch from upstream${NC}"
+    echo -e "${YELLOW}Check your network connection and SSH keys${NC}"
+    exit 1
+fi
+
+# 4. Check if local main is synced with upstream
+LOCAL_MAIN=$(git rev-parse "$MAIN_BRANCH" 2>/dev/null || echo "")
+UPSTREAM_MAIN=$(git rev-parse "${UPSTREAM_REMOTE}/${MAIN_BRANCH}" 2>/dev/null || echo "")
+
+if [ -n "$LOCAL_MAIN" ] && [ -n "$UPSTREAM_MAIN" ] && [ "$LOCAL_MAIN" != "$UPSTREAM_MAIN" ]; then
+    # Check if local main is behind
+    if git merge-base --is-ancestor "$LOCAL_MAIN" "$UPSTREAM_MAIN"; then
+        echo -e "${YELLOW}⚠️  WARNING: Your local '$MAIN_BRANCH' is behind upstream${NC}"
+        echo -e "${YELLOW}Sync it with:${NC}"
+        echo -e "  git checkout $MAIN_BRANCH && git pull $UPSTREAM_REMOTE $MAIN_BRANCH"
+        echo -e "${YELLOW}Then rebase your branch:${NC}"
+        echo -e "  git checkout $CURRENT_BRANCH && git rebase $MAIN_BRANCH"
+        echo ""
+        # This is a warning, not blocking (allows push but warns)
+    elif ! git merge-base --is-ancestor "$UPSTREAM_MAIN" "$LOCAL_MAIN"; then
+        echo -e "${RED}❌ ERROR: Your local '$MAIN_BRANCH' has diverged from upstream${NC}"
+        echo -e "${YELLOW}Reset it with:${NC}"
+        echo -e "  git checkout $MAIN_BRANCH"
+        echo -e "  git reset --hard $UPSTREAM_REMOTE/$MAIN_BRANCH"
+        exit 1
+    fi
+fi
+
+# 5. Check branch is rebased on main
+MERGE_BASE=$(git merge-base "$CURRENT_BRANCH" "$MAIN_BRANCH")
+MAIN_HEAD=$(git rev-parse "$MAIN_BRANCH")
+
+if [ "$MERGE_BASE" != "$MAIN_HEAD" ]; then
+    echo -e "${RED}❌ ERROR: Branch '$CURRENT_BRANCH' is not rebased on latest '$MAIN_BRANCH'${NC}"
+    echo -e "${YELLOW}Rebase with:${NC}"
+    echo -e "  git rebase $MAIN_BRANCH"
+    exit 1
+fi
+
+# 6. Enforce single commit rule
+COMMIT_COUNT=$(git rev-list --count "${MAIN_BRANCH}..${CURRENT_BRANCH}")
+
+if [ "$COMMIT_COUNT" -eq 0 ]; then
+    echo -e "${RED}❌ ERROR: No commits to push (branch is at same state as $MAIN_BRANCH)${NC}"
+    exit 1
+elif [ "$COMMIT_COUNT" -gt 1 ]; then
+    echo -e "${RED}❌ ERROR: Too many commits! Found $COMMIT_COUNT commits, expected exactly 1${NC}"
+    echo -e "${YELLOW}This repo uses a single-commit-per-branch workflow.${NC}"
+    echo ""
+    echo -e "${YELLOW}Option 1: Squash all commits into one:${NC}"
+    echo -e "  git reset --soft $MAIN_BRANCH"
+    echo -e "  git commit -m 'feat: your feature description'"
+    echo ""
+    echo -e "${YELLOW}Option 2: Amend existing commits:${NC}"
+    echo -e "  git add <modified-files>"
+    echo -e "  git commit --amend --no-edit"
+    echo ""
+    echo -e "${YELLOW}Then force push with:${NC}"
+    echo -e "  git push --force-with-lease"
+    exit 1
+fi
+
+echo -e "${GREEN}✓ All pre-push checks passed!${NC}"
+echo -e "${GREEN}✓ Upstream is configured and synced${NC}"
+echo -e "${GREEN}✓ Branch is rebased on main${NC}"
+echo -e "${GREEN}✓ Single commit workflow maintained ($COMMIT_COUNT commit)${NC}"
+exit 0

package/.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+the official BMAD Discord server (<https://discord.com/invite/gk8jAdXWmj>) - DM a moderator or flag a post.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+<https://www.contributor-covenant.org/version/2/0/code_of_conduct.html>.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+<https://www.contributor-covenant.org/faq>. Translations are available at
+<https://www.contributor-covenant.org/translations>.

package/.github/FUNDING.yaml

@@ -0,0 +1,15 @@
+# These are supported funding model platforms
+
+github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
+patreon: # Replace with a single Patreon username
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project_name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+lfx_crowdfunding: # Replace with a single LFX Crowdfunding project_name e.g., cloud-foundry
+polar: # Replace with a single Polar username
+buy_me_a_coffee: bmad
+thanks_dev: # Replace with a single thanks.dev username
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

package/.github/ISSUE_TEMPLATE/config.yaml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: 📚 Documentation
+    url: http://docs.bmad-method.org
+    about: Check the docs first — tutorials, guides, and reference
+  - name: 💬 Discord Community
+    url: https://discord.gg/gk8jAdXWmj
+    about: Join for questions, discussion, and help before opening an issue

package/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,22 @@
+---
+name: Feature Request
+about: Suggest an idea or new feature
+title: ''
+labels: ''
+assignees: ''
+---
+
+**Describe your idea**
+A clear and concise description of what you'd like to see added or changed.
+
+**Why is this needed?**
+Explain the problem this solves or the benefit it brings to the BMad community.
+
+**How should it work?**
+Describe your proposed solution. If you have ideas on implementation, share them here.
+
+**PR**
+If you'd like to contribute, please indicate you're working on this or link to your PR. Please review [CONTRIBUTING.md](../../CONTRIBUTING.md) — contributions are always welcome!
+
+**Additional context**
+Add any other context, screenshots, or links that help explain your idea.

package/.github/ISSUE_TEMPLATE/issue.md

@@ -0,0 +1,32 @@
+---
+name: Issue
+about: Report a problem or something that's not working
+title: ''
+labels: ''
+assignees: ''
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**Steps to reproduce**
+1. What were you doing when the bug occurred?
+2. What steps can recreate the issue?
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Environment (if relevant)**
+- Model(s) used:
+- Agentic IDE used:
+- BMad version:
+- Project language:
+
+**Screenshots or links**
+If applicable, add screenshots or links to help explain the problem.
+
+**PR**
+If you'd like to contribute a fix, please indicate you're working on it or link to your PR. See [CONTRIBUTING.md](../../CONTRIBUTING.md) — contributions are always welcome!
+
+**Additional context**
+Add any other context about the problem here. The more information you provide, the easier it is to help.

package/.github/scripts/discord-helpers.sh

@@ -0,0 +1,34 @@
+#!/bin/bash
+# Discord notification helper functions
+
+# Escape markdown special chars and @mentions for safe Discord display
+# Skips content inside <URL> wrappers to preserve URLs intact
+esc() {
+  awk '{
+    result = ""; in_url = 0; n = length($0)
+    for (i = 1; i <= n; i++) {
+      c = substr($0, i, 1)
+      if (c == "<" && substr($0, i, 8) ~ /^<https?:/) in_url = 1
+      if (in_url) { result = result c; if (c == ">") in_url = 0 }
+      else if (c == "@") result = result "@ "
+      else if (index("[]\\*_()~`", c) > 0) result = result "\\" c
+      else result = result c
+    }
+    print result
+  }'
+}
+
+# Truncate to $1 chars (or 80 if wall-of-text with <3 spaces)
+trunc() {
+  local max=$1
+  local txt=$(tr '\n\r' '  ' | cut -c1-"$max")
+  local spaces=$(printf '%s' "$txt" | tr -cd ' ' | wc -c)
+  [ "$spaces" -lt 3 ] && [ ${#txt} -gt 80 ] && txt=$(printf '%s' "$txt" | cut -c1-80)
+  printf '%s' "$txt"
+}
+
+# Remove incomplete URL at end of truncated text (incomplete URLs are useless)
+strip_trailing_url() { sed -E 's~<?https?://[^[:space:]]*$~~'; }
+
+# Wrap URLs in <> to suppress Discord embeds (keeps links clickable)
+wrap_urls() { sed -E 's~https?://[^[:space:]<>]+~<&>~g'; }