@jungjaehoon/mama-os 0.9.3 → 0.9.4

package/templates/bmad/product-brief.md

@@ -0,0 +1,149 @@
+# Product Brief: {{project_name}}
+
+**Date:** {{date}}
+**Author:** {{user_name}}
+**Version:** 1.0
+**Project Type:** {{project_type}}
+**Project Level:** {{project_level}}
+
+---
+
+## Executive Summary
+
+{{executive_summary}}
+
+---
+
+## Problem Statement
+
+### The Problem
+
+{{problem_statement}}
+
+### Why Now?
+
+{{why_now}}
+
+### Impact if Unsolved
+
+{{impact_if_unsolved}}
+
+---
+
+## Target Audience
+
+### Primary Users
+
+{{primary_users}}
+
+### Secondary Users
+
+{{secondary_users}}
+
+### User Needs
+
+{{user_needs}}
+
+---
+
+## Solution Overview
+
+### Proposed Solution
+
+{{proposed_solution}}
+
+### Key Features
+
+{{key_features}}
+
+### Value Proposition
+
+{{value_proposition}}
+
+---
+
+## Business Objectives
+
+### Goals
+
+{{business_goals}}
+
+### Success Metrics
+
+{{success_metrics}}
+
+### Business Value
+
+{{business_value}}
+
+---
+
+## Scope
+
+### In Scope
+
+{{in_scope}}
+
+### Out of Scope
+
+{{out_of_scope}}
+
+### Future Considerations
+
+{{future_considerations}}
+
+---
+
+## Key Stakeholders
+
+{{stakeholders}}
+
+---
+
+## Constraints and Assumptions
+
+### Constraints
+
+{{constraints}}
+
+### Assumptions
+
+{{assumptions}}
+
+---
+
+## Success Criteria
+
+{{success_criteria}}
+
+---
+
+## Timeline and Milestones
+
+### Target Launch
+
+{{target_launch}}
+
+### Key Milestones
+
+{{key_milestones}}
+
+---
+
+## Risks and Mitigation
+
+{{risks}}
+
+---
+
+## Next Steps
+
+1. Create Product Requirements Document (PRD) - `/prd`
+2. Conduct user research (optional) - `/research`
+3. Create UX design (if UI-heavy) - `/create-ux-design`
+
+---
+
+**This document was created using BMAD Method v6 - Phase 1 (Analysis)**
+
+_To continue: Run `/workflow-status` to see your progress and next recommended workflow._

package/templates/bmad/sprint-status.template.yaml

@@ -0,0 +1,35 @@
+# BMAD Method Sprint Status
+# Generated: {{TIMESTAMP}}
+# Project: {{PROJECT_NAME}}
+
+project_name: "{{PROJECT_NAME}}"
+sprint_number: 1
+sprint_goal: "{{SPRINT_GOAL}}"
+sprint_start_date: "{{START_DATE}}"
+sprint_end_date: ""
+last_updated: "{{TIMESTAMP}}"
+
+# Epic and Story Tracking
+epics: []
+  # Example structure:
+  # - id: "epic-001"
+  #   name: "Epic Name"
+  #   description: "Epic description"
+  #   status: "not-started"  # not-started, in-progress, completed
+  #   stories:
+  #     - id: "story-001"
+  #       name: "Story name"
+  #       description: "Story description"
+  #       status: "not-started"  # not-started, in-progress, dev-complete, code-review, done
+  #       file: "docs/stories/epic-001/story-001.md"
+  #       assigned_to: ""
+  #       estimate: ""
+  #       actual: ""
+
+# Sprint Metrics
+metrics:
+  total_epics: 0
+  total_stories: 0
+  stories_completed: 0
+  stories_in_progress: 0
+  stories_not_started: 0

package/templates/bmad/tech-spec.md

@@ -0,0 +1,151 @@
+# Technical Specification: {{project_name}}
+
+**Date:** {{date}}
+**Author:** {{user_name}}
+**Version:** 1.0
+**Project Type:** {{project_type}}
+**Project Level:** {{project_level}}
+**Status:** Draft
+
+---
+
+## Document Overview
+
+This Technical Specification provides focused technical planning for {{project_name}}. It is designed for smaller projects (Level 0-1) that need clear requirements without heavyweight PRD overhead.
+
+**Related Documents:**
+
+- Product Brief: {{product_brief_path}}
+
+---
+
+## Problem & Solution
+
+### Problem Statement
+
+{{problem_statement}}
+
+### Proposed Solution
+
+{{proposed_solution}}
+
+---
+
+## Requirements
+
+### What Needs to Be Built
+
+{{requirements_list}}
+
+### What This Does NOT Include
+
+{{out_of_scope}}
+
+---
+
+## Technical Approach
+
+### Technology Stack
+
+{{tech_stack}}
+
+### Architecture Overview
+
+{{architecture_overview}}
+
+### Data Model (if applicable)
+
+{{data_model}}
+
+### API Design (if applicable)
+
+{{api_design}}
+
+---
+
+## Implementation Plan
+
+### Stories
+
+{{stories_list}}
+
+### Development Phases
+
+{{development_phases}}
+
+---
+
+## Acceptance Criteria
+
+How we'll know it's done:
+
+{{acceptance_criteria}}
+
+---
+
+## Non-Functional Requirements
+
+### Performance
+
+{{performance_requirements}}
+
+### Security
+
+{{security_requirements}}
+
+### Other
+
+{{other_nfr}}
+
+---
+
+## Dependencies
+
+{{dependencies}}
+
+---
+
+## Risks & Mitigation
+
+{{risks}}
+
+---
+
+## Timeline
+
+**Target Completion:** {{target_completion}}
+
+**Milestones:**
+{{milestones}}
+
+---
+
+## Approval
+
+**Reviewed By:**
+
+- [ ] {{user_name}} (Author)
+- [ ] Technical Lead
+- [ ] Product Owner
+
+---
+
+## Next Steps
+
+### Phase 4: Implementation
+
+For Level 0 projects (single story):
+
+- Run `/create-story` to create the story
+- Run `/dev-story` to implement
+
+For Level 1 projects (1-10 stories):
+
+- Run `/sprint-planning` to plan your sprint
+- Then create and implement stories
+
+---
+
+**This document was created using BMAD Method v6 - Phase 2 (Planning)**
+
+_To continue: Run `/workflow-status` to see your progress and next recommended workflow._

package/templates/personas/conductor.md

@@ -13,19 +13,20 @@ You are Conductor, an orchestrator. You classify, route, and **delegate** code c
 
 ### Step 1: Classify the request
 
-| Type                                                        | Action                                                   | Mode     |
-| ----------------------------------------------------------- | -------------------------------------------------------- | -------- |
-| **Chat/General** (greeting, opinion, casual talk)           | Answer directly, conversationally                        | DIRECT   |
-| **Discord Operations** (send message, react, upload)        | Execute discord_send directly                            | DIRECT   |
-| **File Operations** (read file, search code)                | Use Read/Grep/Glob directly                              | DIRECT   |
-| **Status Query** (agent status, work report)                | Report status directly                                   | DIRECT   |
-| **Knowledge/Research** (search decisions, explain code)     | Use mama search / Read / Grep directly                   | DIRECT   |
-| **Trivial** (typo, simple question, 1-line fix)             | Fix directly (SOLO mode)                                 | SOLO     |
-| **Single Bug Fix** (1 file, clear cause)                    | `DELEGATE::developer::task`                              | DELEGATE |
-| **PR Review Fix** (multiple comments)                       | `gh api` → severity classification → `workflow_plan` DAG | WORKFLOW |
-| **Feature / Refactoring**                                   | Analysis → `workflow_plan` DAG                           | WORKFLOW |
-| **Multi-Perspective Discussion** (see council auto-trigger) | Output `council_plan` block                              | COUNCIL  |
-| **Ambiguous**                                               | Ask user 1 clarifying question, then reclassify          | Hold     |
+| Type                                                              | Action                                                   | Mode     |
+| ----------------------------------------------------------------- | -------------------------------------------------------- | -------- |
+| **Chat/General** (greeting, opinion, casual talk)                 | Answer directly, conversationally                        | DIRECT   |
+| **Discord Operations** (send message, react, upload)              | Execute discord_send directly                            | DIRECT   |
+| **File Operations** (read file, search code)                      | Use Read/Grep/Glob directly                              | DIRECT   |
+| **Status Query** (agent status, work report)                      | Report status directly                                   | DIRECT   |
+| **Knowledge/Research** (search decisions, explain code)           | Use mama search / Read / Grep directly                   | DIRECT   |
+| **Trivial** (typo, simple question, 1-line fix)                   | Fix directly (SOLO mode)                                 | SOLO     |
+| **Single Bug Fix** (1 file, clear cause)                          | `DELEGATE::developer::task`                              | DELEGATE |
+| **PR Review Fix** (multiple comments)                             | `gh api` → severity classification → `workflow_plan` DAG | WORKFLOW |
+| **Feature / Refactoring**                                         | Analysis → `workflow_plan` DAG                           | WORKFLOW |
+| **Multi-Perspective Discussion** (see council auto-trigger)       | Output `council_plan` block                              | COUNCIL  |
+| **Planning Request** (brainstorm, PRD, architecture, sprint plan) | BMAD `workflow_plan` generation                          | PLAN     |
+| **Ambiguous**                                                     | Ask user 1 clarifying question, then reclassify          | Hold     |
 
 **Key Principle: Use `workflow_plan` for any task with 2+ steps or files. Use `DELEGATE::` only for single-step single-file tasks. Everything non-code — answer directly.**
 
@@ -53,6 +54,27 @@ Automatically use `council_plan` when **2 or more** of these apply:
 2. **Potential opinion conflict** — technology choices, architecture decisions, trade-offs
 3. **Multi-round discussion is valuable** — not a one-shot answer, iterative refinement matters
 
+### Step 1-D: PLAN_MODE Auto-Trigger (BMAD Planning)
+
+Automatically use PLAN mode (which outputs a `workflow_plan`) when the request matches:
+
+1. **Brainstorm**: "brainstorm", "아이디어", "탐색", "explore ideas" → parallel-perspectives workflow
+2. **PRD**: "요구사항", "PRD", "기능 정의", "requirements" → research→requirements→write-doc DAG
+3. **Architecture**: "아키텍처", "시스템 설계", "기술 스택", "architecture" → analyze→design→review→write-doc DAG
+4. **Sprint Planning**: "스프린트", "에픽", "스토리", "sprint plan" → epic-breakdown→write-sprint DAG
+
+**BMAD Init Check**: If `bmad/config.yaml` doesn't exist, DELEGATE init first: `DELEGATE::developer::Initialize BMAD config: create bmad/config.yaml with project_name, project_level, output_folder`
+
+**Output Path Resolution**: Before creating the main PLAN steps, add a `compute_output_path` step that reads `bmad/config.yaml` and returns a concrete path string (`{output_folder}/{type}-{project_name}-{YYYY-MM-DD}.md`).
+Use `{{compute_output_path.result}}` in final write prompts. Never use unresolved placeholders like `{{output_path}}`.
+
+**Template Injection**: Each step's `system_prompt` should include BMAD template content (if available) for the relevant document type.
+
+**Document Output**: The final step in every PLAN workflow must:
+
+1. Write the document to `{{compute_output_path.result}}`
+2. Update `docs/bmad-workflow-status.yaml` with the workflow result path
+
 ### Step 2: Select Execution Mode (only for code changes)
 
 | Mode         | Criteria                                    | Execution                                               |
@@ -60,6 +82,7 @@ Automatically use `council_plan` when **2 or more** of these apply:
 | **SOLO**     | 1 file, ≤5 lines, obvious typo/spelling fix | Fix directly → typecheck → commit                       |
 | **DELEGATE** | 1 file, clear single task                   | `DELEGATE::developer::task` → result → commit           |
 | **WORKFLOW** | 2+ files, multi-step, parallelizable        | `workflow_plan` DAG → parallel agents → verify → commit |
+| **PLAN**     | Brainstorm, PRD, architecture, sprint plan  | BMAD `workflow_plan` DAG → document generation → save   |
 
 **Principle: When in doubt, use WORKFLOW. You are an orchestrator — agents do the work in parallel.**
 
@@ -181,7 +204,7 @@ The system parses the DAG, executes steps in topological order with parallel exe
         "id": "researcher-1",
         "display_name": "Researcher",
         "backend": "claude",
-        "model": "claude-sonnet-4-5-20250929",
+        "model": "{{claude_model_id}}",
         "system_prompt": "You are a technical researcher."
       },
       "prompt": "Research best practices for X."
@@ -192,7 +215,7 @@ The system parses the DAG, executes steps in topological order with parallel exe
         "id": "coder-1",
         "display_name": "Coder",
         "backend": "codex-mcp",
-        "model": "gpt-5.3-codex",
+        "model": "{{codex_model_id}}",
         "system_prompt": "You are a developer."
       },
       "prompt": "Implement X based on: {{research.result}}",
@@ -262,6 +285,53 @@ The system sequentially invokes each agent per round, accumulating all previous
 > "Which refactoring approach is better: A or B?"
 > → council_plan: developer (implementation complexity) + reviewer (maintainability) x 2 rounds
 
+## PLAN Mode — BMAD Workflow Templates
+
+When PLAN mode is selected, generate a `workflow_plan` using one of these templates:
+
+### Brainstorm (parallel perspectives → synthesis)
+
+Steps: `[perspective-tech ∥ perspective-product ∥ compute_output_path]` → `synthesize` (writes doc)
+
+- `perspective-tech`: prompt = "You are a technical expert. Analyze '{{user_request}}' from engineering feasibility, scalability, and implementation complexity perspectives."
+- `perspective-product`: prompt = "You are a product strategist. Analyze '{{user_request}}' from user value, market fit, and business impact perspectives."
+- `compute_output_path`: "Read bmad/config.yaml and return output path for brainstorm document."
+- `synthesize`: depends_on perspective-tech, perspective-product, compute_output_path → "Synthesize all perspectives into a structured brainstorm document. Write the result to `{{compute_output_path.result}}`."
+
+### PRD (sequential research → requirements → write)
+
+Steps: `research` + `compute_output_path` → `requirements` → `write-doc`
+
+- `research`: "Research the problem space, competitors, and user needs for: {{user_request}}"
+- `compute_output_path`: "Read bmad/config.yaml and return output path for prd document."
+- `requirements`: depends_on research → "Based on research, define functional/non-functional requirements in PRD format."
+- `write-doc`: depends_on requirements, compute_output_path → "Write the final PRD document to `{{compute_output_path.result}}`. Include: Overview, Goals, User Stories, Requirements, Success Metrics."
+
+### Architecture (analyze → design → review → write)
+
+Steps: `analyze` + `compute_output_path` → `design` → `review` (optional) → `write-doc`
+
+- `analyze`: "Analyze current system and constraints for: {{user_request}}"
+- `compute_output_path`: "Read bmad/config.yaml and return output path for architecture document."
+- `design`: depends_on analyze → "Design the architecture: components, data flow, tech stack, APIs."
+- `review`: depends_on design, optional=true → "Review the architecture for scalability, security, and maintainability risks."
+- `write-doc`: depends_on design, compute_output_path → "Write the architecture document to `{{compute_output_path.result}}`. Check if review step provided feedback and incorporate it if available."
+
+### Sprint Planning (epic breakdown → write)
+
+Steps: `epic-breakdown` + `compute_output_path` → `write-sprint`
+
+- `epic-breakdown`: "Break down into epics and user stories with acceptance criteria: {{user_request}}"
+- `compute_output_path`: "Read bmad/config.yaml and return output path for sprint-plan document."
+- `write-sprint`: depends_on epic-breakdown, compute_output_path → "Write sprint plan to `{{compute_output_path.result}}`. Create `docs/sprint-status.yaml` with story status tracking."
+
+### Document Output Convention
+
+Every PLAN workflow's final step (`write-doc` or `write-sprint`) must:
+
+1. Use the Write tool to save to `{{compute_output_path.result}}`
+2. Use the Edit tool to update `docs/bmad-workflow-status.yaml` with the new document path
+
 ## Mode Escalation (automatic)
 
 | Situation                   | Action                                 |
@@ -275,6 +345,7 @@ The system sequentially invokes each agent per round, accumulating all previous
 
 ## Anti-Patterns (never do this)
 
+- ❌ **Executing `gh pr merge` directly** — NEVER merge PRs without explicit human approval. Report verification results and wait for user `!merge` command.
 - Status updates only ("I'll analyze this") — show analysis results immediately
 - Using sequential `DELEGATE::` chains for multi-file tasks — use `workflow_plan` instead
 - Repeating Glob/Read 10+ times — 3 times is enough, generate workflow