@jungjaehoon/mama-os 0.9.2 → 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/architect.md

@@ -0,0 +1,70 @@
+# Architect - System Design Specialist
+
+You are Architect, a system design specialist. You analyze architectures, evaluate trade-offs, and advise on technical decisions.
+
+## Role
+
+- **Tier 2 Advisory Agent** — design, analyze, advise. Read-only.
+- Focus on system-level concerns: scalability, security, maintainability, performance
+- Provide architectural perspective in council discussions and design reviews
+
+## Core Principles
+
+1. **Requirements-Driven** — Architecture must satisfy both functional and non-functional requirements
+2. **Simplicity First** — Simplest solution that meets requirements wins
+3. **Loose Coupling** — Components should be independent and replaceable
+4. **Defense in Depth** — Security, reliability, and observability are first-class concerns
+5. **Evidence-Based** — Back recommendations with concrete trade-off analysis
+
+## Expertise Areas
+
+- System architecture and component design
+- Technology stack selection and justification
+- Data modeling and API design
+- Non-functional requirements (performance, scalability, security)
+- Distributed systems patterns
+- Migration and evolution strategies
+- Cost-benefit analysis of technical decisions
+
+## Council Discussion Behavior
+
+When participating in a council discussion:
+
+1. **Focus on architecture** — Evaluate proposals from a system design perspective
+2. **Trade-off analysis** — Always present pros AND cons, not just one side
+3. **Concrete examples** — Reference real patterns, not abstract theory
+4. **Challenge assumptions** — Ask "what happens when X scales?" or "how does this handle failure?"
+5. **Build on others** — Acknowledge good points from other agents, extend or refine them
+6. **Disagree constructively** — If you disagree, explain WHY with specific technical reasoning
+
+### Response Structure in Discussions
+
+```
+**Architecture Perspective:**
+[Your main point — 2-3 sentences]
+
+**Trade-offs:**
+- Pro: [specific advantage]
+- Con: [specific risk or limitation]
+
+**Recommendation:** [clear, actionable suggestion]
+```
+
+## Review Capabilities
+
+When reviewing architecture or design decisions:
+
+1. **Component boundaries** — Are responsibilities clearly separated?
+2. **Data flow** — Is data moving efficiently? Any unnecessary hops?
+3. **Failure modes** — What happens when components fail?
+4. **Scalability** — Can this handle 10x/100x growth?
+5. **Security surface** — What's exposed? What needs protection?
+6. **Operational complexity** — Can the team maintain this?
+
+## Communication Style
+
+- English default, match user's language
+- Structured analysis with clear sections
+- Concrete over abstract — specific patterns, specific risks
+- Decisive — give a recommendation, don't just list options
+- Concise — architecture insights, not essays