bmad-method 6.0.0-alpha.8 → 6.0.0-alpha.9

package/src/modules/bmm/tasks/daily-standup.xml

@@ -1,85 +0,0 @@
-<task id="{bmad_folder}/bmm/tasks/daily-standup.xml" name="Daily Standup">
-  <llm critical="true">
-    <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
-    <i>DO NOT skip steps or change the sequence</i>
-    <i>HALT immediately when halt-conditions are met</i>
-    <i>Each action tag within a step tag is a REQUIRED action to complete that step</i>
-    <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
-  </llm>
-  <flow>
-    <step n="1" title="Project Context Discovery">
-      <action>Check for stories folder at {project-root}{output_folder}/stories/</action>
-      <action>Find current story by identifying highest numbered story file</action>
-      <action>Read story status (In Progress, Ready for Review, etc.)</action>
-      <action>Extract agent notes from Dev Agent Record, TEA Results, PO Notes sections</action>
-      <action>Check for next story references from epics</action>
-      <action>Identify blockers from story sections</action>
-    </step>
-
-    <step n="2" title="Initialize Standup with Context">
-      <output>
-        🏃 DAILY STANDUP - Story-{{number}}: {{title}}
-
-        Current Sprint Status:
-        - Active Story: story-{{number}} ({{status}} - {{percentage}}% complete)
-        - Next in Queue: story-{{next-number}}: {{next-title}}
-        - Blockers: {{blockers-from-story}}
-
-        Team assembled based on story participants:
-        {{ List Agents from {project-root}/{bmad_folder}/_cfg/agent-manifest.csv }}
-      </output>
-    </step>
-
-    <step n="3" title="Structured Standup Discussion">
-      <action>Each agent provides three items referencing real story data</action>
-      <action>What I see: Their perspective on current work, citing story sections (1-2 sentences)</action>
-      <action>What concerns me: Issues from their domain or story blockers (1-2 sentences)</action>
-      <action>What I suggest: Actionable recommendations for progress (1-2 sentences)</action>
-    </step>
-
-    <step n="4" title="Create Standup Summary">
-      <output>
-        📋 STANDUP SUMMARY:
-        Key Items from Story File:
-        - {{completion-percentage}}% complete ({{tasks-complete}}/{{total-tasks}} tasks)
-        - Blocker: {{main-blocker}}
-        - Next: {{next-story-reference}}
-
-        Action Items:
-        - {{agent}}: {{action-item}}
-        - {{agent}}: {{action-item}}
-        - {{agent}}: {{action-item}}
-
-        Need extended discussion? Use *party-mode for detailed breakout.
-      </output>
-    </step>
-  </flow>
-
-  <agent-selection>
-    <context type="prd-review">
-      <i>Primary: Sarah (PO), Mary (Analyst), Winston (Architect)</i>
-      <i>Secondary: Murat (TEA), James (Dev)</i>
-    </context>
-    <context type="story-planning">
-      <i>Primary: Sarah (PO), Bob (SM), James (Dev)</i>
-      <i>Secondary: Murat (TEA)</i>
-    </context>
-    <context type="validate-architecture">
-      <i>Primary: Winston (Architect), James (Dev), Murat (TEA)</i>
-      <i>Secondary: Sarah (PO)</i>
-    </context>
-    <context type="implementation">
-      <i>Primary: James (Dev), Murat (TEA), Winston (Architect)</i>
-      <i>Secondary: Sarah (PO)</i>
-    </context>
-  </agent-selection>
-
-  <llm critical="true">
-    <i>This task extends party-mode with agile-specific structure</i>
-    <i>Time-box responses (standup = brief)</i>
-    <i>Focus on actionable items from real story data when available</i>
-    <i>End with clear next steps</i>
-    <i>No deep dives (suggest breakout if needed)</i>
-    <i>If no stories folder detected, run general standup format</i>
-  </llm>
-</task>

package/src/modules/bmm/workflows/2-plan-workflows/tech-spec/instructions-level0-story.md

@@ -1,200 +0,0 @@
-# Level 0 - Minimal User Story Generation
-
-<workflow>
-
-<critical>This generates a single user story for Level 0 atomic changes</critical>
-<critical>Level 0 = single file change, bug fix, or small isolated task</critical>
-<critical>This workflow runs AFTER tech-spec.md has been completed</critical>
-<critical>Output format MUST match create-story template for compatibility with story-context and dev-story workflows</critical>
-
-<step n="1" goal="Load tech spec and extract the change">
-
-<action>Read the completed tech-spec.md file from {output_folder}/tech-spec.md</action>
-<action>Load bmm-workflow-status.yaml from {output_folder}/bmm-workflow-status.yaml (if exists)</action>
-<action>Extract dev_ephemeral_location from config (where stories are stored)</action>
-
-<action>Extract from the ENHANCED tech-spec structure:
-
-- Problem statement from "The Change → Problem Statement" section
-- Solution overview from "The Change → Proposed Solution" section
-- Scope from "The Change → Scope" section
-- Source tree from "Implementation Details → Source Tree Changes" section
-- Time estimate from "Implementation Guide → Implementation Steps" section
-- Acceptance criteria from "Implementation Guide → Acceptance Criteria" section
-- Framework dependencies from "Development Context → Framework/Libraries" section
-- Existing code references from "Development Context → Relevant Existing Code" section
-- File paths from "Developer Resources → File Paths Reference" section
-- Key code locations from "Developer Resources → Key Code Locations" section
-- Testing locations from "Developer Resources → Testing Locations" section
-  </action>
-
-</step>
-
-<step n="2" goal="Generate story slug and filename">
-
-<action>Derive a short URL-friendly slug from the feature/change name</action>
-<action>Max slug length: 3-5 words, kebab-case format</action>
-
-<example>
-- "Migrate JS Library Icons" → "icon-migration"
-- "Fix Login Validation Bug" → "login-fix"
-- "Add OAuth Integration" → "oauth-integration"
-</example>
-
-<action>Set story_filename = "story-{slug}.md"</action>
-<action>Set story_path = "{dev_ephemeral_location}/story-{slug}.md"</action>
-
-</step>
-
-<step n="3" goal="Create user story in standard format">
-
-<action>Create 1 story that describes the technical change as a deliverable</action>
-<action>Story MUST use create-story template format for compatibility</action>
-
-<guidelines>
-**Story Point Estimation:**
-- 1 point = < 1 day (2-4 hours)
-- 2 points = 1-2 days
-- 3 points = 2-3 days
-- 5 points = 3-5 days (if this high, question if truly Level 0)
-
-**Story Title Best Practices:**
-
-- Use active, user-focused language
-- Describe WHAT is delivered, not HOW
-- Good: "Icon Migration to Internal CDN"
-- Bad: "Run curl commands to download PNGs"
-
-**Story Description Format:**
-
-- As a [role] (developer, user, admin, etc.)
-- I want [capability/change]
-- So that [benefit/value]
-
-**Acceptance Criteria:**
-
-- Extract from tech-spec "Testing Approach" section
-- Must be specific, measurable, and testable
-- Include performance criteria if specified
-
-**Tasks/Subtasks:**
-
-- Map directly to tech-spec "Implementation Guide" tasks
-- Use checkboxes for tracking
-- Reference AC numbers: (AC: #1), (AC: #2)
-- Include explicit testing subtasks
-
-**Dev Notes:**
-
-- Extract technical constraints from tech-spec
-- Include file paths from "Developer Resources → File Paths Reference"
-- Include existing code references from "Development Context → Relevant Existing Code"
-- Reference architecture patterns if applicable
-- Cite tech-spec sections for implementation details
-- Note dependencies (internal and external)
-
-**NEW: Comprehensive Context**
-
-Since tech-spec is now context-rich, populate all new template fields:
-
-- dependencies: Extract from "Development Context" and "Implementation Details → Integration Points"
-- existing_code_references: Extract from "Development Context → Relevant Existing Code" and "Developer Resources → Key Code Locations"
-  </guidelines>
-
-<action>Initialize story file using user_story_template</action>
-
-<template-output file="{story_path}">story_title</template-output>
-<template-output file="{story_path}">role</template-output>
-<template-output file="{story_path}">capability</template-output>
-<template-output file="{story_path}">benefit</template-output>
-<template-output file="{story_path}">acceptance_criteria</template-output>
-<template-output file="{story_path}">tasks_subtasks</template-output>
-<template-output file="{story_path}">technical_summary</template-output>
-<template-output file="{story_path}">files_to_modify</template-output>
-<template-output file="{story_path}">test_locations</template-output>
-<template-output file="{story_path}">story_points</template-output>
-<template-output file="{story_path}">time_estimate</template-output>
-<template-output file="{story_path}">dependencies</template-output>
-<template-output file="{story_path}">existing_code_references</template-output>
-<template-output file="{story_path}">architecture_references</template-output>
-
-</step>
-
-<step n="4" goal="Update status - Level 0 single story">
-
-<invoke-workflow path="{project-root}/{bmad_folder}/bmm/workflows/workflow-status">
-  <param>mode: update</param>
-  <param>action: complete_workflow</param>
-  <param>workflow_name: tech-spec</param>
-</invoke-workflow>
-
-<check if="success == true">
-  <output>✅ Tech-spec complete! Next: {{next_workflow}}</output>
-</check>
-
-<action>Load {{status_file_path}}</action>
-<action>Set STORIES_SEQUENCE: [{slug}]</action>
-<action>Set TODO_STORY: {slug}</action>
-<action>Set TODO_TITLE: {{story_title}}</action>
-<action>Set IN_PROGRESS_STORY: (empty)</action>
-<action>Set STORIES_DONE: []</action>
-<action>Save {{status_file_path}}</action>
-
-<output>Story queue initialized with single story: {slug}</output>
-
-</step>
-
-<step n="5" goal="Provide user guidance for next steps">
-
-<action>Display completion summary</action>
-
-**Level 0 Planning Complete!**
-
-**Generated Artifacts:**
-
-- `tech-spec.md` → Technical source of truth
-- `story-{slug}.md` → User story ready for implementation
-
-**Story Location:** `{story_path}`
-
-**Next Steps:**
-
-**🎯 RECOMMENDED - Direct to Development (Level 0):**
-
-Since the tech-spec is now CONTEXT-RICH with:
-
-- ✅ Brownfield codebase analysis (if applicable)
-- ✅ Framework and library details with exact versions
-- ✅ Existing patterns and code references
-- ✅ Complete file paths and integration points
-
-**You can skip story-context and go straight to dev!**
-
-1. Load DEV agent: `{project-root}/{bmad_folder}/bmm/agents/dev.md`
-2. Run `dev-story` workflow
-3. Begin implementation immediately
-
-**Option B - Generate Additional Context (optional):**
-
-Only needed for extremely complex scenarios:
-
-1. Load SM agent: `{project-root}/{bmad_folder}/bmm/agents/sm.md`
-2. Run `story-context` workflow (generates additional XML context)
-3. Then load DEV agent and run `dev-story` workflow
-
-**Progress Tracking:**
-
-- All decisions logged in: `bmm-workflow-status.yaml`
-- Next action clearly identified
-
-<ask>Ready to proceed? Choose your path:
-
-1. Go directly to dev-story (RECOMMENDED - tech-spec has all context)
-2. Generate additional story context (for complex edge cases)
-3. Exit for now
-
-Select option (1-3):</ask>
-
-</step>
-
-</workflow>