shipquick 1.0.0

package/_bmad-safe/bmm-safe/workflows/qa/automate/workflow.yaml

@@ -0,0 +1,47 @@
+# Quinn QA workflow: Automate
+name: qa-automate
+description: "Generate tests quickly for existing features using standard test patterns"
+author: "BMad"
+
+# Critical variables from config
+config_source: "{project-root}/_bmad-safe/bmm-safe/config.yaml"
+output_folder: "{config_source}:output_folder"
+implementation_artifacts: "{config_source}:implementation_artifacts"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+document_output_language: "{config_source}:document_output_language"
+date: system-generated
+
+# Workflow components
+installed_path: "{project-root}/_bmad-safe/bmm-safe/workflows/qa/automate"
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+template: false
+
+# Variables and inputs
+variables:
+  # Directory paths
+  test_dir: "{project-root}/tests" # Root test directory
+  source_dir: "{project-root}" # Source code directory
+
+# Output configuration
+default_output_file: "{implementation_artifacts}/tests/test-summary.md"
+
+# Required tools
+required_tools:
+  - read_file # Read source code and existing tests
+  - write_file # Create test files
+  - create_directory # Create test directories
+  - list_files # Discover features
+  - search_repo # Find patterns
+  - glob # Find files
+
+tags:
+  - qa
+  - automation
+  - testing
+
+execution_hints:
+  interactive: false
+  autonomous: true
+  iterative: false

package/_bmad-safe/core/agents/bmad-master.md

@@ -0,0 +1,56 @@
+---
+name: "bmad master"
+description: "BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator"
+---
+
+You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
+
+```xml
+<agent id="bmad-master.agent.yaml" name="BMad Master" title="BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator" icon="🧙">
+<activation critical="MANDATORY">
+      <step n="1">Load persona from this current agent file (already in context)</step>
+      <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
+          - Load and read {project-root}/_bmad-safe/core/config.yaml NOW
+          - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
+          - VERIFY: If config not loaded, STOP and report error to user
+          - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored
+      </step>
+      <step n="3">Remember: user's name is {user_name}</step>
+      <step n="4">Always greet the user and let them know they can use `/bmad-help` at any time to get advice on what to do next, and they can combine that with what they need help with <example>`/bmad-help where should I start with an idea I have that does XYZ`</example></step>
+      <step n="5">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of ALL menu items from menu section</step>
+      <step n="{HELP_STEP}">Let {user_name} know they can type command `/bmad-help` at any time to get advice on what to do next, and that they can combine that with what they need help with <example>`/bmad-help where should I start with an idea I have that does XYZ`</example></step>
+      <step n="6">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command match</step>
+      <step n="7">On user input: Number → process menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user to clarify | No match → show "Not recognized"</step>
+      <step n="8">When processing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
+
+      <menu-handlers>
+              <handlers>
+        <handler type="action">
+      When menu item has: action="#id" → Find prompt with id="id" in current agent XML, follow its content
+      When menu item has: action="text" → Follow the text directly as an inline instruction
+    </handler>
+        </handlers>
+      </menu-handlers>
+
+    <rules>
+      <r>ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style.</r>
+      <r> Stay in character until exit selected</r>
+      <r> Display Menu items as the item dictates and in the order given.</r>
+      <r> Load files ONLY when executing a user chosen workflow or a command requires it, EXCEPTION: agent activation step 2 config.yaml</r>
+    </rules>
+</activation>  <persona>
+    <role>Master Task Executor + BMad Expert + Guiding Facilitator Orchestrator</role>
+    <identity>Master-level expert in the BMAD Core Platform and all loaded modules with comprehensive knowledge of all resources, tasks, and workflows. Experienced in direct task execution and runtime resource management, serving as the primary execution engine for BMAD operations.</identity>
+    <communication_style>Direct and comprehensive, refers to himself in the 3rd person. Expert-level communication focused on efficient task execution, presenting information systematically using numbered lists with immediate command response capability.</communication_style>
+    <principles>- &quot;Load resources at runtime never pre-load, and always present numbered lists for choices.&quot;</principles>
+  </persona>
+  <menu>
+    <item cmd="MH or fuzzy match on menu or help">[MH] Redisplay Menu Help</item>
+    <item cmd="CH or fuzzy match on chat">[CH] Chat with the Agent about anything</item>
+    <item cmd="LT or fuzzy match on list-tasks" action="list all tasks from {project-root}/_bmad-safe/_config/task-manifest.csv">[LT] List Available Tasks</item>
+    <item cmd="LW or fuzzy match on list-workflows" action="list all workflows from {project-root}/_bmad-safe/_config/workflow-manifest.csv">[LW] List Workflows</item>
+    <item cmd="PM or fuzzy match on party-mode" exec="{project-root}/_bmad-safe/core/workflows/party-mode/workflow.md">[PM] Start Party Mode</item>
+    <item cmd="DA or fuzzy match on exit, leave, goodbye or dismiss agent">[DA] Dismiss Agent</item>
+  </menu>
+</agent>
+```

package/_bmad-safe/core/beads-acceptance.xml

@@ -0,0 +1,182 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+  BEADS ACCEPTANCE GATES - SAFe Dependency Enforcement
+  Ensures acceptance follows SAFe hierarchy via Beads dependencies
+  
+  Golden Rule: Parent cannot complete until ALL children complete
+-->
+<beads-acceptance version="1.0" standalone="true">
+  
+  <objective>Enforce SAFe acceptance gates via Beads dependency checking</objective>
+  
+  <!-- ACCEPTANCE GATE RULES -->
+  <rules>
+    <rule n="1">Task bd done requires: all subtasks complete</rule>
+    <rule n="2">Story bd done requires: all Tasks + Defects complete</rule>
+    <rule n="3">Feature bd done requires: all Stories complete</rule>
+    <rule n="4">Capability bd done requires: all Features complete</rule>
+    <rule n="5">Epic bd done requires: all Capabilities complete</rule>
+    <rule n="6">Theme bd done requires: all Epics complete</rule>
+  </rules>
+  
+  <!-- TASK ACCEPTANCE -->
+  <acceptance-gate level="task" agent="dev">
+    <step n="1" title="Verify Task Complete">
+      <action>Confirm all code written</action>
+      <action>Confirm all tests passing</action>
+      <action>Run: bd show {task_bead_id}</action>
+    </step>
+    <step n="2" title="Mark Done">
+      <action>Run: bd done {task_bead_id}</action>
+      <action>Update story file task checkbox: [x]</action>
+    </step>
+  </acceptance-gate>
+  
+  <!-- DEFECT ACCEPTANCE -->
+  <acceptance-gate level="defect" agent="qa">
+    <step n="1" title="Verify Defect Fixed">
+      <action>Confirm fix implemented</action>
+      <action>Confirm regression test added</action>
+      <action>Confirm all tests passing</action>
+    </step>
+    <step n="2" title="Mark Done">
+      <action>Run: bd done {defect_bead_id}</action>
+    </step>
+  </acceptance-gate>
+  
+  <!-- STORY ACCEPTANCE -->
+  <acceptance-gate level="story" agent="po">
+    <step n="1" title="Dependency Check">
+      <action>Run: bd show {story_bead_id} --children</action>
+      <check if="any child not done">
+        <action>BLOCK acceptance</action>
+        <action>Report: "Story blocked by: {pending_children}"</action>
+        <action>Return to lowest pending item</action>
+      </check>
+    </step>
+    <step n="2" title="Acceptance Criteria Verification">
+      <action>PO verifies all AC met</action>
+      <action>Confirm demo ready</action>
+    </step>
+    <step n="3" title="Mark Accepted">
+      <action>Run: bd done {story_bead_id}</action>
+      <action>Update sprint-status.yaml story status: accepted</action>
+    </step>
+  </acceptance-gate>
+  
+  <!-- FEATURE ACCEPTANCE -->
+  <acceptance-gate level="feature" agent="pm">
+    <step n="1" title="Dependency Check">
+      <action>Run: bd show {feature_bead_id} --children</action>
+      <check if="any story not accepted">
+        <action>BLOCK acceptance</action>
+        <action>Report: "Feature blocked by stories: {pending_stories}"</action>
+      </check>
+    </step>
+    <step n="2" title="Business Value Verification">
+      <action>PM confirms benefit hypothesis validated</action>
+      <action>System Demo complete</action>
+    </step>
+    <step n="3" title="Mark Accepted">
+      <action>Run: bd done {feature_bead_id}</action>
+      <action>Trigger Capability gate check</action>
+    </step>
+  </acceptance-gate>
+  
+  <!-- CAPABILITY ACCEPTANCE -->
+  <acceptance-gate level="capability" agent="solution-manager">
+    <step n="1" title="Dependency Check">
+      <action>Run: bd show {capability_bead_id} --children</action>
+      <check if="any feature not accepted">
+        <action>BLOCK acceptance</action>
+        <action>Report: "Capability blocked by features: {pending_features}"</action>
+      </check>
+    </step>
+    <step n="2" title="Solution Verification">
+      <action>Solution Manager confirms capability operational</action>
+      <action>All ARTs delivered their features</action>
+    </step>
+    <step n="3" title="Mark Accepted">
+      <action>Run: bd done {capability_bead_id}</action>
+      <action>Trigger Epic gate check</action>
+    </step>
+  </acceptance-gate>
+  
+  <!-- EPIC ACCEPTANCE -->
+  <acceptance-gate level="epic" agent="business-owner">
+    <step n="1" title="Dependency Check">
+      <action>Run: bd show {epic_bead_id} --children</action>
+      <check if="any capability not accepted">
+        <action>BLOCK acceptance</action>
+        <action>Report: "Epic blocked by capabilities: {pending_capabilities}"</action>
+      </check>
+    </step>
+    <step n="2" title="Business Value Verification">
+      <action>Business Owner confirms ROI achieved</action>
+      <action>Lean Business Case validated</action>
+    </step>
+    <step n="3" title="Mark Accepted">
+      <action>Run: bd done {epic_bead_id}</action>
+      <action>Trigger Theme gate check</action>
+    </step>
+  </acceptance-gate>
+  
+  <!-- THEME ACCEPTANCE -->
+  <acceptance-gate level="theme" agent="business-owner">
+    <step n="1" title="Dependency Check">
+      <action>Run: bd show {theme_bead_id} --children</action>
+      <check if="any epic not accepted">
+        <action>BLOCK acceptance</action>
+        <action>Report: "Theme blocked by epics: {pending_epics}"</action>
+      </check>
+    </step>
+    <step n="2" title="Strategic Outcome Verification">
+      <action>Confirm strategic outcome achieved</action>
+      <action>Portfolio leadership review</action>
+    </step>
+    <step n="3" title="Mark Complete">
+      <action>Run: bd done {theme_bead_id}</action>
+      <action>Report: "🎉 Theme '{theme_name}' successfully completed!"</action>
+    </step>
+  </acceptance-gate>
+  
+  <!-- SPILLOVER HANDLING -->
+  <spillover-protocol level="story" trigger="sprint end with incomplete story">
+    <step n="1" title="Analyze">
+      <action>Run: bd show {story_bead_id} --children</action>
+      <action>Identify pending tasks/defects</action>
+    </step>
+    <step n="2" title="Decision">
+      <ask>Spillover options: [S]plit story, [C]arry forward, [D]e-scope</ask>
+    </step>
+    <step n="3" title="Execute Split" if="response=S">
+      <action>Create new story for remaining work</action>
+      <action>bd create "Story: {story_name}-remainder" --parent {feature_bead_id}</action>
+      <action>Move pending tasks to new story</action>
+      <action>bd done original story (for completed portion)</action>
+    </step>
+    <step n="4" title="Execute Carry" if="response=C">
+      <action>Tag story with next_sprint: {sprint_id}</action>
+      <action>Update sprint-status.yaml</action>
+    </step>
+    <step n="5" title="Execute De-scope" if="response=D">
+      <action>Mark story as de-scoped</action>
+      <action>Return to backlog</action>
+    </step>
+  </spillover-protocol>
+  
+  <spillover-protocol level="feature" trigger="PI end with incomplete feature">
+    <step n="1" title="Analyze">
+      <action>Run: bd show {feature_bead_id} --children</action>
+      <action>Identify pending stories</action>
+    </step>
+    <step n="2" title="Decision">
+      <ask>PI Spillover: [S]plit feature, [M]ove to next PI, [D]e-scope</ask>
+    </step>
+    <step n="3" title="Execute">
+      <action>Apply selected option</action>
+      <action>Update PI planning documentation</action>
+    </step>
+  </spillover-protocol>
+  
+</beads-acceptance>

package/_bmad-safe/core/beads-hooks.xml

@@ -0,0 +1,179 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+  BEADS HOOKS - Enhanced ID Generation + Lifecycle Management
+  
+  ID Format: Type-ParentRef-Sequence
+  Example: T-001, E-T1-01, C-E1-01, F-C1-01, US-F1-01, TK-S1-01
+-->
+<beads-hooks version="2.0" standalone="true">
+  
+  <objective>Generate SAFe-aligned Bead IDs with parent visibility and manage lifecycle</objective>
+  
+  <!-- ID GENERATION PROTOCOL -->
+  <protocol name="generate_bead_id" desc="Generate next bead ID based on type and parent">
+    
+    <!-- THEME: T-001, T-002, T-003 -->
+    <generator type="theme">
+      <action>Read beads.counters.theme from config.yaml</action>
+      <action>Increment counter: counters.theme += 1</action>
+      <action>Format ID: "T-{counters.theme:03d}"</action>
+      <action>Store beads.current.theme_id and theme_seq</action>
+      <output>T-001, T-002, etc.</output>
+    </generator>
+    
+    <!-- EPIC: E-T1-01 (Epic 1 under Theme 1) -->
+    <generator type="epic">
+      <requires>beads.current.theme_seq</requires>
+      <action>Get parent_key = "T{theme_seq}"</action>
+      <action>Initialize counters.epic[parent_key] = 0 if not exists</action>
+      <action>Increment: counters.epic[parent_key] += 1</action>
+      <action>Format ID: "E-T{theme_seq}-{seq:02d}"</action>
+      <action>Store beads.current.epic_id and epic_seq</action>
+      <output>E-T1-01, E-T1-02, E-T2-01, etc.</output>
+    </generator>
+    
+    <!-- CAPABILITY: C-E1-01 (Capability 1 under Epic 1) -->
+    <generator type="capability">
+      <requires>beads.current.epic_seq</requires>
+      <action>Get parent_key = "E{epic_seq}"</action>
+      <action>Initialize counters.capability[parent_key] = 0 if not exists</action>
+      <action>Increment: counters.capability[parent_key] += 1</action>
+      <action>Format ID: "C-E{epic_seq}-{seq:02d}"</action>
+      <action>Store beads.current.capability_id and capability_seq</action>
+      <output>C-E1-01, C-E1-02, C-E2-01, etc.</output>
+    </generator>
+    
+    <!-- FEATURE: F-C1-01 (Feature 1 under Capability 1) -->
+    <generator type="feature">
+      <requires>beads.current.capability_seq</requires>
+      <action>Get parent_key = "C{capability_seq}"</action>
+      <action>Initialize counters.feature[parent_key] = 0 if not exists</action>
+      <action>Increment: counters.feature[parent_key] += 1</action>
+      <action>Format ID: "F-C{capability_seq}-{seq:02d}"</action>
+      <action>Store beads.current.feature_id and feature_seq</action>
+      <output>F-C1-01, F-C1-02, F-C2-01, etc.</output>
+    </generator>
+    
+    <!-- STORY: US-F1-01 (User Story 1 under Feature 1) -->
+    <generator type="story">
+      <requires>beads.current.feature_seq</requires>
+      <action>Get parent_key = "F{feature_seq}"</action>
+      <action>Initialize counters.story[parent_key] = 0 if not exists</action>
+      <action>Increment: counters.story[parent_key] += 1</action>
+      <action>Format ID: "US-F{feature_seq}-{seq:02d}"</action>
+      <action>Store beads.current.story_id and story_seq</action>
+      <output>US-F1-01, US-F1-02, US-F2-01, etc.</output>
+    </generator>
+    
+    <!-- TASK: TK-S1-01 (Task 1 under Story 1) -->
+    <generator type="task">
+      <requires>beads.current.story_seq</requires>
+      <action>Get parent_key = "S{story_seq}"</action>
+      <action>Initialize counters.task[parent_key] = 0 if not exists</action>
+      <action>Increment: counters.task[parent_key] += 1</action>
+      <action>Format ID: "TK-S{story_seq}-{seq:02d}"</action>
+      <output>TK-S1-01, TK-S1-02, TK-S2-01, etc.</output>
+    </generator>
+    
+    <!-- DEFECT: DF-S1-01 (Defect 1 under Story 1) -->
+    <generator type="defect">
+      <requires>beads.current.story_seq</requires>
+      <action>Get parent_key = "S{story_seq}"</action>
+      <action>Initialize counters.defect[parent_key] = 0 if not exists</action>
+      <action>Increment: counters.defect[parent_key] += 1</action>
+      <action>Format ID: "DF-S{story_seq}-{seq:02d}"</action>
+      <output>DF-S1-01, DF-S1-02, DF-S2-01, etc.</output>
+    </generator>
+  </protocol>
+  
+  <!-- SESSION START PROTOCOL -->
+  <protocol name="session_start" desc="Execute at every session initialization">
+    <step n="1" title="Check Beads Availability">
+      <action>Run: bd --version</action>
+      <check if="error">
+        <action>STOP execution</action>
+        <action>Report: "Beads not installed. Run: npm install -g @beads/bd"</action>
+      </check>
+    </step>
+    
+    <step n="2" title="Load Counter State">
+      <action>Read beads.counters from config.yaml</action>
+      <action>Read beads.current from config.yaml</action>
+      <action>Verify counters match bd list output</action>
+    </step>
+    
+    <step n="3" title="Resume Check">
+      <action>Run: bd ready</action>
+      <check if="ready tasks found">
+        <action>Display pending tasks with their IDs</action>
+        <wait-for-input/>
+      </check>
+    </step>
+  </protocol>
+  
+  <!-- WORKFLOW HOOKS -->
+  <hook name="on_theme_create" agent="analyst">
+    <action>Call generate_bead_id(type="theme")</action>
+    <action>Run: bd create "Theme: {theme_name}" --id {generated_id}</action>
+    <action>Save counters to config.yaml</action>
+  </hook>
+  
+  <hook name="on_epic_create" agent="pm">
+    <action>Call generate_bead_id(type="epic")</action>
+    <action>Run: bd create "Epic: {epic_name}" --id {generated_id} --parent {current.theme_id}</action>
+    <action>Save counters to config.yaml</action>
+  </hook>
+  
+  <hook name="on_capability_create" agent="solution-manager">
+    <action>Call generate_bead_id(type="capability")</action>
+    <action>Run: bd create "Capability: {capability_name}" --id {generated_id} --parent {current.epic_id}</action>
+    <action>Save counters to config.yaml</action>
+  </hook>
+  
+  <hook name="on_feature_create" agent="rte">
+    <action>Call generate_bead_id(type="feature")</action>
+    <action>Run: bd create "Feature: {feature_name}" --id {generated_id} --parent {current.capability_id}</action>
+    <action>Save counters to config.yaml</action>
+  </hook>
+  
+  <hook name="on_story_create" agent="po|sm">
+    <action>Call generate_bead_id(type="story")</action>
+    <action>Run: bd create "Story: {story_name}" --id {generated_id} --parent {current.feature_id}</action>
+    <action>Save counters to config.yaml</action>
+  </hook>
+  
+  <hook name="on_task_create" agent="dev">
+    <action>Call generate_bead_id(type="task")</action>
+    <action>Run: bd create "Task: {task_name}" --id {generated_id} --parent {current.story_id}</action>
+    <action>Save counters to config.yaml</action>
+  </hook>
+  
+  <hook name="on_defect_create" agent="qa">
+    <action>Call generate_bead_id(type="defect")</action>
+    <action>Run: bd create "Defect: {defect_name}" --id {generated_id} --parent {current.story_id}</action>
+    <action>Run: bd dep add {generated_id} {current.story_id}</action>
+    <action>Save counters to config.yaml</action>
+  </hook>
+  
+  <!-- CONTEXT SWITCH HOOKS -->
+  <hook name="on_set_context" desc="When switching to work on existing item">
+    <action>Parse bead_id to extract type and parent reference</action>
+    <action>Update beads.current.{type}_id and {type}_seq</action>
+    <action>Example: "F-C1-02" sets feature_id="F-C1-02", feature_seq=2</action>
+  </hook>
+  
+  <!-- ACCEPTANCE HOOKS (unchanged from beads-acceptance.xml) -->
+  <hook name="on_item_done">
+    <action>Run: bd done {item_id}</action>
+    <action>Trigger parent gate check via beads-acceptance.xml</action>
+  </hook>
+  
+  <!-- FAILURE HANDLING -->
+  <protocol name="counter_sync">
+    <trigger>Mismatch between config counters and bd list</trigger>
+    <action>Re-count items from bd list by type</action>
+    <action>Update counters in config.yaml</action>
+    <action>Report: "Counter sync completed"</action>
+  </protocol>
+  
+</beads-hooks>

package/_bmad-safe/core/beads-integration.md

@@ -0,0 +1,68 @@
+# BMAD-Beads Integration Rules
+
+## Single Source of Truth
+
+Beads (`.beads/`) is the ONLY system for:
+
+- Long-term memory
+- Task planning
+- Dependency tracking
+- Execution state
+- Session-to-session continuity
+
+## BMAD Responsibilities
+
+- Reasoning and decomposition
+- Prioritization decisions
+- Decision making
+
+## Beads Responsibilities
+
+- Storing every task created by BMAD
+- Storing all dependencies
+- Storing execution state
+
+## Integration Contract
+
+| BMAD Action       | Beads Command                     |
+| ----------------- | --------------------------------- |
+| Create plan step  | `bd create "Title" -p <priority>` |
+| Add dependency    | `bd dep add <child> <parent>`     |
+| Complete task     | `bd done <id>`                    |
+| Get next task     | `bd ready`                        |
+| Show task details | `bd show <id>`                    |
+| List all tasks    | `bd list`                         |
+
+## Execution Loop
+
+```
+1. On startup:
+   - Check `bd list` for existing tasks
+   - If empty, create root task
+
+2. Planning phase:
+   - BMAD generates plan
+   - Each step → `bd create`
+
+3. Execution phase:
+   - Run `bd ready`
+   - Execute ONE ready task
+   - Mark complete → `bd done <id>`
+
+4. Repeat until `bd ready` is empty
+```
+
+## Strict Rules
+
+1. **Beads = Single Source of Truth**
+2. Information not in Beads = NON-EXISTENT
+3. Never recreate plans already in Beads
+4. On restart, ALWAYS read from Beads first
+
+## Hierarchy
+
+```
+bmad-safe-xxxx          (Epic/Root)
+bmad-safe-xxxx.1        (Task)
+bmad-safe-xxxx.1.1      (Sub-task)
+```

package/_bmad-safe/core/config.yaml

@@ -0,0 +1,9 @@
+# CORE Module Configuration
+# Generated by BMAD installer
+# Version: 6.0.0-Beta.4
+# Date: 2026-01-31T15:19:46.048Z
+
+user_name: Satvik
+communication_language: Romanised Hindi
+document_output_language: English
+output_folder: "{project-root}/_bmad-output"

package/_bmad-safe/core/module-help.csv

@@ -0,0 +1,9 @@
+module,phase,name,code,sequence,workflow-file,command,required,agent,options,description,output-location,outputs
+core,,Brainstorming,BS,20,_bmad-safe/core/workflows/brainstorming/workflow.md,bmad-brainstorming,false,analyst,,Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods,{output_folder}/brainstorming/brainstorming-session-{{date}}.md,,
+core,,Party Mode,PM,30,_bmad-safe/core/workflows/party-mode/workflow.md,bmad-party-mode,false,party-mode facilitator,,Orchestrates group discussions between all installed BMAD agents enabling natural multi-agent conversations,,
+core,,bmad-help,BH,40,_bmad-safe/core/tasks/help.md,bmad-help,false,,,Get unstuck by showing what workflow steps come next or answering questions about what to do in the BMad Method,,
+core,,Index Docs,ID,50,_bmad-safe/core/tasks/index-docs.xml,bmad-index-docs,false,,,Generates or updates an index.md of all documents in the specified directory,,
+core,,Shard Document,SD,70,_bmad-safe/core/tasks/shard-doc.xml,bmad-shard-doc,false,,,Splits large markdown documents into smaller organized files based on level 2 sections,,
+core,,Editorial Review - Prose,EP,80,_bmad-safe/core/tasks/editorial-review-prose.xml,bmad-editorial-review-prose,false,,,Clinical copy-editor that reviews text for communication issues,,"three-column markdown table with suggested fixes",
+core,,Editorial Review - Structure,ES,90,_bmad-safe/core/tasks/editorial-review-structure.xml,bmad-editorial-review-structure,false,,,Structural editor that proposes cuts reorganization and simplification while preserving comprehension,,
+core,,Adversarial Review (General),AR,100,_bmad-safe/core/tasks/review-adversarial-general.xml,bmad-review-adversarial-general,false,,,Cynically review content and produce findings,,