shipquick 1.0.0 → 2.0.0

package/content/_bmad/_config/ides/antigravity.yaml

@@ -0,0 +1,5 @@
+ide: antigravity
+configured_date: 2026-02-13T19:55:53.405Z
+last_updated: 2026-02-13T19:55:53.405Z
+configuration:
+  _noConfigNeeded: true

package/content/_bmad/_config/ides/auggie.yaml

@@ -0,0 +1,5 @@
+ide: auggie
+configured_date: 2026-02-13T19:55:53.282Z
+last_updated: 2026-02-13T19:55:53.282Z
+configuration:
+  _noConfigNeeded: true

package/content/_bmad/_config/ides/claude-code.yaml

@@ -0,0 +1,5 @@
+ide: claude-code
+configured_date: 2026-02-13T19:55:53.157Z
+last_updated: 2026-02-13T19:55:53.157Z
+configuration:
+  _noConfigNeeded: true

package/content/_bmad/_config/ides/cline.yaml

@@ -0,0 +1,5 @@
+ide: cline
+configured_date: 2026-02-13T19:55:53.313Z
+last_updated: 2026-02-13T19:55:53.313Z
+configuration:
+  _noConfigNeeded: true

package/content/_bmad/_config/ides/codex.yaml

@@ -0,0 +1,5 @@
+ide: codex
+configured_date: 2026-02-13T19:55:53.199Z
+last_updated: 2026-02-13T19:55:53.199Z
+configuration:
+  installLocation: global

package/content/_bmad/_config/ides/crush.yaml

@@ -0,0 +1,5 @@
+ide: crush
+configured_date: 2026-02-13T19:55:53.339Z
+last_updated: 2026-02-13T19:55:53.339Z
+configuration:
+  _noConfigNeeded: true

package/content/_bmad/_config/ides/cursor.yaml

@@ -0,0 +1,5 @@
+ide: cursor
+configured_date: 2026-02-13T19:55:53.226Z
+last_updated: 2026-02-13T19:55:53.226Z
+configuration:
+  _noConfigNeeded: true

package/content/_bmad/_config/ides/gemini.yaml

@@ -0,0 +1,5 @@
+ide: gemini
+configured_date: 2026-02-13T19:55:53.369Z
+last_updated: 2026-02-13T19:55:53.369Z
+configuration:
+  _noConfigNeeded: true

package/content/_bmad/_config/ides/github-copilot.yaml

@@ -0,0 +1,5 @@
+ide: github-copilot
+configured_date: 2026-02-13T19:55:53.376Z
+last_updated: 2026-02-13T19:55:53.376Z
+configuration:
+  _noConfigNeeded: true

package/content/_bmad/_config/ides/iflow.yaml

@@ -0,0 +1,5 @@
+ide: iflow
+configured_date: 2026-02-13T19:55:53.432Z
+last_updated: 2026-02-13T19:55:53.432Z
+configuration:
+  _noConfigNeeded: true

package/content/_bmad/_config/ides/kilo.yaml

@@ -0,0 +1,5 @@
+ide: kilo
+configured_date: 2026-02-13T19:55:53.453Z
+last_updated: 2026-02-13T19:55:53.453Z
+configuration:
+  _noConfigNeeded: true

package/content/_bmad/_config/ides/kiro.yaml

@@ -0,0 +1,5 @@
+ide: kiro
+configured_date: 2026-02-13T19:55:53.480Z
+last_updated: 2026-02-13T19:55:53.480Z
+configuration:
+  _noConfigNeeded: true

package/content/_bmad/_config/ides/opencode.yaml

@@ -0,0 +1,5 @@
+ide: opencode
+configured_date: 2026-02-13T19:55:53.506Z
+last_updated: 2026-02-13T19:55:53.506Z
+configuration:
+  _noConfigNeeded: true

package/content/_bmad/_config/ides/qwen.yaml

@@ -0,0 +1,5 @@
+ide: qwen
+configured_date: 2026-02-13T19:55:53.532Z
+last_updated: 2026-02-13T19:55:53.532Z
+configuration:
+  _noConfigNeeded: true

package/content/_bmad/_config/ides/roo.yaml

@@ -0,0 +1,5 @@
+ide: roo
+configured_date: 2026-02-13T19:55:53.558Z
+last_updated: 2026-02-13T19:55:53.558Z
+configuration:
+  _noConfigNeeded: true

package/content/_bmad/_config/ides/rovo-dev.yaml

@@ -0,0 +1,5 @@
+ide: rovo-dev
+configured_date: 2026-02-13T19:55:53.587Z
+last_updated: 2026-02-13T19:55:53.587Z
+configuration:
+  _noConfigNeeded: true

package/content/_bmad/_config/ides/trae.yaml

@@ -0,0 +1,5 @@
+ide: trae
+configured_date: 2026-02-13T19:55:53.616Z
+last_updated: 2026-02-13T19:55:53.616Z
+configuration:
+  _noConfigNeeded: true

package/content/_bmad/_config/ides/windsurf.yaml

@@ -0,0 +1,5 @@
+ide: windsurf
+configured_date: 2026-02-13T19:55:53.256Z
+last_updated: 2026-02-13T19:55:53.256Z
+configuration:
+  _noConfigNeeded: true

package/content/_bmad/_config/manifest.yaml

@@ -0,0 +1,45 @@
+installation:
+  version: 6.0.0-Beta.8
+  installDate: 2026-02-13T19:55:53.059Z
+  lastUpdated: 2026-02-13T19:55:53.059Z
+modules:
+  - name: core
+    version: 6.0.0-Beta.8
+    installDate: 2026-02-13T19:55:52.100Z
+    lastUpdated: 2026-02-13T19:55:52.100Z
+    source: built-in
+    npmPackage: null
+    repoUrl: null
+  - name: bmm
+    version: 6.0.0-Beta.8
+    installDate: 2026-02-13T19:55:42.494Z
+    lastUpdated: 2026-02-13T19:55:52.100Z
+    source: built-in
+    npmPackage: null
+    repoUrl: null
+  - name: tea
+    version: 1.0.0
+    installDate: 2026-02-13T19:55:52.056Z
+    lastUpdated: 2026-02-13T19:55:53.059Z
+    source: external
+    npmPackage: bmad-method-test-architecture-enterprise
+    repoUrl: https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise
+ides:
+  - claude-code
+  - codex
+  - cursor
+  - windsurf
+  - auggie
+  - cline
+  - crush
+  - gemini
+  - github-copilot
+  - antigravity
+  - iflow
+  - kilo
+  - kiro
+  - opencode
+  - qwen
+  - roo
+  - rovo-dev
+  - trae

package/content/_bmad/_config/task-manifest.csv

@@ -0,0 +1,7 @@
+name,displayName,description,module,path,standalone
+"editorial-review-prose","Editorial Review - Prose","Clinical copy-editor that reviews text for communication issues","core","_bmad/core/tasks/editorial-review-prose.xml","true"
+"editorial-review-structure","Editorial Review - Structure","Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension","core","_bmad/core/tasks/editorial-review-structure.xml","true"
+"help","help","Get unstuck by showing what workflow steps come next or answering questions about what to do","core","_bmad/core/tasks/help.md","true"
+"index-docs","Index Docs","Generates or updates an index.md of all documents in the specified directory","core","_bmad/core/tasks/index-docs.xml","true"
+"review-adversarial-general","Adversarial Review (General)","Cynically review content and produce findings","core","_bmad/core/tasks/review-adversarial-general.xml","true"
+"shard-doc","Shard Document","Splits large markdown documents into smaller, organized files based on level 2 (default) sections","core","_bmad/core/tasks/shard-doc.xml","true"

package/content/_bmad/_config/tool-manifest.csv

@@ -0,0 +1 @@
+name,displayName,description,module,path,standalone

package/content/_bmad/_config/workflow-manifest.csv

@@ -0,0 +1,42 @@
+name,description,module,path
+"brainstorming","Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods","core","_bmad/core/workflows/brainstorming/workflow.md"
+"party-mode","Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations","core","_bmad/core/workflows/party-mode/workflow.md"
+"create-product-brief","Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.","bmm","_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md"
+"domain-research","Conduct domain research covering industry analysis, regulations, technology trends, and ecosystem dynamics using current web data and verified sources.","bmm","_bmad/bmm/workflows/1-analysis/research/workflow-domain-research.md"
+"market-research","Conduct market research covering market size, growth, competition, and customer insights using current web data and verified sources.","bmm","_bmad/bmm/workflows/1-analysis/research/workflow-market-research.md"
+"technical-research","Conduct technical research covering technology evaluation, architecture decisions, and implementation approaches using current web data and verified sources.","bmm","_bmad/bmm/workflows/1-analysis/research/workflow-technical-research.md"
+"create-prd","Create a comprehensive PRD (Product Requirements Document) through structured workflow facilitation","bmm","_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-create-prd.md"
+"edit-prd","Edit and improve an existing PRD - enhance clarity, completeness, and quality","bmm","_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-edit-prd.md"
+"validate-prd","Validate an existing PRD against BMAD standards - comprehensive review for completeness, clarity, and quality","bmm","_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-validate-prd.md"
+"create-ux-design","Work with a peer UX Design expert to plan your applications UX patterns, look and feel.","bmm","_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md"
+"check-implementation-readiness","Critical validation workflow that assesses PRD, Architecture, and Epics & Stories for completeness and alignment before implementation. Uses adversarial review approach to find gaps and issues.","bmm","_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md"
+"create-architecture","Collaborative architectural decision facilitation for AI-agent consistency. Replaces template-driven architecture with intelligent, adaptive conversation that produces a decision-focused architecture document optimized for preventing agent conflicts.","bmm","_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md"
+"create-epics-and-stories","Transform PRD requirements and Architecture decisions into comprehensive stories organized by user value. This workflow requires completed PRD + Architecture documents (UX recommended if UI exists) and breaks down requirements into implementation-ready epics and user stories that incorporate all available technical and design context. Creates detailed, actionable stories with complete acceptance criteria for development teams.","bmm","_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md"
+"code-review","Perform an ADVERSARIAL Senior Developer code review that finds 3-10 specific problems in every story. Challenges everything: code quality, test coverage, architecture compliance, security, performance. NEVER accepts `looks good` - must find minimum issues and can auto-fix with user approval.","bmm","_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml"
+"correct-course","Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation","bmm","_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml"
+"create-story","Create the next user story from epics+stories with enhanced context analysis and direct ready-for-dev marking","bmm","_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml"
+"dev-story","Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria","bmm","_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml"
+"retrospective","Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic","bmm","_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml"
+"sprint-planning","Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle","bmm","_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml"
+"sprint-status","Summarize sprint-status.yaml, surface risks, and route to the right implementation workflow.","bmm","_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml"
+"quick-dev","Flexible development - execute tech-specs OR direct instructions with optional planning.","bmm","_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md"
+"quick-spec","Conversational spec engineering - ask questions, investigate code, produce implementation-ready tech-spec.","bmm","_bmad/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md"
+"document-project","Analyzes and documents brownfield projects by scanning codebase, architecture, and patterns to create comprehensive reference documentation for AI-assisted development","bmm","_bmad/bmm/workflows/document-project/workflow.yaml"
+"generate-project-context","Creates a concise project-context.md file with critical rules and patterns that AI agents must follow when implementing code. Optimized for LLM context efficiency.","bmm","_bmad/bmm/workflows/generate-project-context/workflow.md"
+"qa-automate","Generate tests quickly for existing features using standard test patterns","bmm","_bmad/bmm/workflows/qa/automate/workflow.yaml"
+"sq-init","Initialize SAFe hierarchy with Strategic Theme and Portfolio Epic including WSJF calculation","bmm","_bmad/bmm/workflows/2-plan-workflows/sq-init/workflow-sq-init.md"
+"sq-analyze","Create Lean Business Case and finalize WSJF scoring for a Portfolio Epic","bmm","_bmad/bmm/workflows/2-plan-workflows/sq-analyze/workflow-sq-analyze.md"
+"sq-solve","Decompose approved Epic into Capabilities at Solution Train level","bmm","_bmad/bmm/workflows/3-solutioning/sq-solve/workflow-sq-solve.md"
+"sq-plan","Decompose Capabilities into Features at ART level for PI readiness","bmm","_bmad/bmm/workflows/3-solutioning/sq-plan/workflow-sq-plan.md"
+"sq-exec","Decompose Features into User Stories Dev Tasks and QA Test Cases","bmm","_bmad/bmm/workflows/4-implementation/sq-exec/workflow-sq-exec.md"
+"sq-audit","Validate SAFe hierarchy compliance including orphan check AC validation and WSJF consistency","bmm","_bmad/bmm/workflows/4-implementation/sq-audit/workflow-sq-audit.md"
+"sq-export","Generate enterprise-compatible CSV files for Jira or Rally bulk import","bmm","_bmad/bmm/workflows/4-implementation/sq-export/workflow-sq-export.md"
+"testarch-atdd","Generate failing acceptance tests before implementation using TDD red-green-refactor cycle","tea","_bmad/tea/workflows/testarch/atdd/workflow.yaml"
+"testarch-automate","Expand test automation coverage after implementation or analyze existing codebase to generate comprehensive test suite","tea","_bmad/tea/workflows/testarch/automate/workflow.yaml"
+"testarch-ci","Scaffold CI/CD quality pipeline with test execution, burn-in loops, and artifact collection","tea","_bmad/tea/workflows/testarch/ci/workflow.yaml"
+"testarch-framework","Initialize production-ready test framework architecture (Playwright or Cypress) with fixtures, helpers, and configuration","tea","_bmad/tea/workflows/testarch/framework/workflow.yaml"
+"testarch-nfr","Assess non-functional requirements (performance, security, reliability, maintainability) before release with evidence-based validation","tea","_bmad/tea/workflows/testarch/nfr-assess/workflow.yaml"
+"teach-me-testing","Multi-session learning companion that teaches testing progressively through 7 structured sessions with state persistence","tea","_bmad/tea/workflows/testarch/teach-me-testing/workflow.md"
+"testarch-test-design","Dual-mode workflow: (1) System-level testability review in Solutioning phase, or (2) Epic-level test planning in Implementation phase. Auto-detects mode based on project phase.","tea","_bmad/tea/workflows/testarch/test-design/workflow.yaml"
+"testarch-test-review","Review test quality using comprehensive knowledge base and best practices validation","tea","_bmad/tea/workflows/testarch/test-review/workflow.yaml"
+"testarch-trace","Generate requirements-to-tests traceability matrix, analyze coverage, and make quality gate decision (PASS/CONCERNS/FAIL/WAIVED)","tea","_bmad/tea/workflows/testarch/trace/workflow.yaml"

package/content/_bmad/_memory/config.yaml

@@ -0,0 +1,8 @@
+# _MEMORY Module Configuration
+# Generated by BMAD installer
+
+# Core Configuration Values
+user_name: User
+communication_language: English
+document_output_language: English
+output_folder: "{project-root}/_bmad-output"

package/content/_bmad/_memory/storyteller-sidecar/stories-told.md

@@ -0,0 +1,7 @@
+# Story Record Template
+
+Purpose: Record a log detailing the stories I have crafted over time for the user.
+
+## Narratives Told Table Record
+
+<!-- track stories created metadata with the user over time -->

package/content/_bmad/_memory/storyteller-sidecar/story-preferences.md

@@ -0,0 +1,7 @@
+# Story Record Template
+
+Purpose: Record a log of learned users story telling or story building preferences.
+
+## User Preference Bullet List
+
+<!-- record any user preferences about story crafting the user prefers -->

package/content/_bmad/_memory/tech-writer-sidecar/documentation-standards.md

@@ -0,0 +1,224 @@
+# Technical Documentation Standards for BMAD
+
+CommonMark standards, technical writing best practices, and style guide compliance.
+
+## User Specified CRITICAL Rules - Supersedes General CRITICAL RULES
+
+None
+
+## General CRITICAL RULES
+
+### Rule 1: CommonMark Strict Compliance
+
+ALL documentation MUST follow CommonMark specification exactly. No exceptions.
+
+### Rule 2: NO TIME ESTIMATES
+
+NEVER document time estimates, durations, level of effort or completion times for any workflow, task, or activity unless EXPLICITLY asked by the user. This includes:
+
+- NO Workflow execution time (e.g., "30-60 min", "2-8 hours")
+- NO Task duration and level of effort estimates
+- NO Reading time estimates
+- NO Implementation time ranges
+- NO Any temporal or capacity based measurements
+
+**Instead:** Focus on workflow steps, dependencies, and outputs. Let users determine their own timelines and level of effort.
+
+### CommonMark Essentials
+
+**Headers:**
+
+- Use ATX-style ONLY: `#` `##` `###` (NOT Setext underlines)
+- Single space after `#`: `# Title` (NOT `#Title`)
+- No trailing `#`: `# Title` (NOT `# Title #`)
+- Hierarchical order: Don't skip levels (h1→h2→h3, not h1→h3)
+
+**Code Blocks:**
+
+- Use fenced blocks with language identifier:
+  ````markdown
+  ```javascript
+  const example = 'code';
+  ```
+  ````
+- NOT indented code blocks (ambiguous)
+
+**Lists:**
+
+- Consistent markers within list: all `-` or all `*` or all `+` (don't mix)
+- Proper indentation for nested items (2 or 4 spaces, stay consistent)
+- Blank line before/after list for clarity
+
+**Links:**
+
+- Inline: `[text](url)`
+- Reference: `[text][ref]` then `[ref]: url` at bottom
+- NO bare URLs without `<>` brackets
+
+**Emphasis:**
+
+- Italic: `*text*` or `_text_`
+- Bold: `**text**` or `__text__`
+- Consistent style within document
+
+**Line Breaks:**
+
+- Two spaces at end of line + newline, OR
+- Blank line between paragraphs
+- NO single line breaks (they're ignored)
+
+## Mermaid Diagrams: Valid Syntax Required
+
+**Critical Rules:**
+
+1. Always specify diagram type first line
+2. Use valid Mermaid v10+ syntax
+3. Test syntax before outputting (mental validation)
+4. Keep focused: 5-10 nodes ideal, max 15
+
+**Diagram Type Selection:**
+
+- **flowchart** - Process flows, decision trees, workflows
+- **sequenceDiagram** - API interactions, message flows, time-based processes
+- **classDiagram** - Object models, class relationships, system structure
+- **erDiagram** - Database schemas, entity relationships
+- **stateDiagram-v2** - State machines, lifecycle stages
+- **gitGraph** - Branch strategies, version control flows
+
+**Formatting:**
+
+````markdown
+```mermaid
+flowchart TD
+    Start[Clear Label] --> Decision{Question?}
+    Decision -->|Yes| Action1[Do This]
+    Decision -->|No| Action2[Do That]
+```
+````
+
+## Style Guide Principles (Distilled)
+
+Apply in this hierarchy:
+
+1. **Project-specific guide** (if exists) - always ask first
+2. **BMAD conventions** (this document)
+3. **Google Developer Docs style** (defaults below)
+4. **CommonMark spec** (when in doubt)
+
+### Core Writing Rules
+
+**Task-Oriented Focus:**
+
+- Write for user GOALS, not feature lists
+- Start with WHY, then HOW
+- Every doc answers: "What can I accomplish?"
+
+**Clarity Principles:**
+
+- Active voice: "Click the button" NOT "The button should be clicked"
+- Present tense: "The function returns" NOT "The function will return"
+- Direct language: "Use X for Y" NOT "X can be used for Y"
+- Second person: "You configure" NOT "Users configure" or "One configures"
+
+**Structure:**
+
+- One idea per sentence
+- One topic per paragraph
+- Headings describe content accurately
+- Examples follow explanations
+
+**Accessibility:**
+
+- Descriptive link text: "See the API reference" NOT "Click here"
+- Alt text for diagrams: Describe what it shows
+- Semantic heading hierarchy (don't skip levels)
+- Tables have headers
+
+## OpenAPI/API Documentation
+
+**Required Elements:**
+
+- Endpoint path and method
+- Authentication requirements
+- Request parameters (path, query, body) with types
+- Request example (realistic, working)
+- Response schema with types
+- Response examples (success + common errors)
+- Error codes and meanings
+
+**Quality Standards:**
+
+- OpenAPI 3.0+ specification compliance
+- Complete schemas (no missing fields)
+- Examples that actually work
+- Clear error messages
+- Security schemes documented
+
+## Documentation Types: Quick Reference
+
+**README:**
+
+- What (overview), Why (purpose), How (quick start)
+- Installation, Usage, Contributing, License
+- Under 500 lines (link to detailed docs)
+- Final Polish include a Table of Contents
+
+**API Reference:**
+
+- Complete endpoint coverage
+- Request/response examples
+- Authentication details
+- Error handling
+- Rate limits if applicable
+
+**User Guide:**
+
+- Task-based sections (How to...)
+- Step-by-step instructions
+- Screenshots/diagrams where helpful
+- Troubleshooting section
+
+**Architecture Docs:**
+
+- System overview diagram (Mermaid)
+- Component descriptions
+- Data flow
+- Technology decisions (ADRs)
+- Deployment architecture
+
+**Developer Guide:**
+
+- Setup/environment requirements
+- Code organization
+- Development workflow
+- Testing approach
+- Contribution guidelines
+
+## Quality Checklist
+
+Before finalizing ANY documentation:
+
+- [ ] CommonMark compliant (no violations)
+- [ ] NO time estimates anywhere (Critical Rule 2)
+- [ ] Headers in proper hierarchy
+- [ ] All code blocks have language tags
+- [ ] Links work and have descriptive text
+- [ ] Mermaid diagrams render correctly
+- [ ] Active voice, present tense
+- [ ] Task-oriented (answers "how do I...")
+- [ ] Examples are concrete and working
+- [ ] Accessibility standards met
+- [ ] Spelling/grammar checked
+- [ ] Reads clearly at target skill level
+
+**Frontmatter:**
+Use YAML frontmatter when appropriate, for example:
+
+```yaml
+---
+title: Document Title
+description: Brief description
+author: Author name
+date: YYYY-MM-DD
+---
+```

package/content/_bmad/bmm/agents/_deprecated/architect.md

@@ -0,0 +1,58 @@
+---
+name: "architect"
+description: "Architect"
+---
+
+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="architect.agent.yaml" name="Winston" title="Architect" 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/bmm/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">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="5">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="exec">
+        When menu item or handler has: exec="path/to/file.md":
+        1. Read fully and follow the file at that path
+        2. Process the complete file and follow all instructions within it
+        3. If there is data="some/path/data-foo.md" with the same item, pass that data path to the executed file as context.
+      </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>System Architect + Technical Design Leader</role>
+    <identity>Senior architect with expertise in distributed systems, cloud infrastructure, and API design. Specializes in scalable patterns and technology selection.</identity>
+    <communication_style>Speaks in calm, pragmatic tones, balancing &apos;what could be&apos; with &apos;what should be.&apos;</communication_style>
+    <principles>- Channel expert lean architecture wisdom: draw upon deep knowledge of distributed systems, cloud patterns, scalability trade-offs, and what actually ships successfully - User journeys drive technical decisions. Embrace boring technology for stability. - Design simple solutions that scale when needed. Developer productivity is architecture. Connect every decision to business value and user impact.</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="CA or fuzzy match on create-architecture" exec="{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md">[CA] Create Architecture: Guided Workflow to document technical decisions to keep implementation on track</item>
+    <item cmd="IR or fuzzy match on implementation-readiness" exec="{project-root}/_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md">[IR] Implementation Readiness: Ensure the PRD, UX, and Architecture and Epics and Stories List are all aligned</item>
+    <item cmd="PM or fuzzy match on party-mode" exec="{project-root}/_bmad/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/content/_bmad/bmm/agents/_deprecated/dev.md

@@ -0,0 +1,69 @@
+---
+name: "dev"
+description: "Developer Agent"
+---
+
+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="dev.agent.yaml" name="Amelia" title="Developer Agent" 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/bmm/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">READ the entire story file BEFORE any implementation - tasks/subtasks sequence is your authoritative implementation guide</step>
+  <step n="5">Execute tasks/subtasks IN ORDER as written in story file - no skipping, no reordering, no doing what you want</step>
+  <step n="6">Mark task/subtask [x] ONLY when both implementation AND tests are complete and passing</step>
+  <step n="7">Run full test suite after each task - NEVER proceed with failing tests</step>
+  <step n="8">Execute continuously without pausing until all tasks/subtasks are complete</step>
+  <step n="9">Document in story file Dev Agent Record what was implemented, tests created, and any decisions made</step>
+  <step n="10">Update story file File List with ALL changed files after each task completion</step>
+  <step n="11">NEVER lie about tests being written or passing - tests must actually exist and pass 100%</step>
+      <step n="12">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="13">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="14">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command match</step>
+      <step n="15">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="16">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="workflow">
+        When menu item has: workflow="path/to/workflow.yaml":
+
+        1. CRITICAL: Always LOAD {project-root}/_bmad/core/tasks/workflow.xml
+        2. Read the complete file - this is the CORE OS for processing BMAD workflows
+        3. Pass the yaml path as 'workflow-config' parameter to those instructions
+        4. Follow workflow.xml instructions precisely following all steps
+        5. Save outputs after completing EACH workflow step (never batch multiple steps together)
+        6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
+      </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>Senior Software Engineer</role>
+    <identity>Executes approved stories with strict adherence to story details and team standards and practices.</identity>
+    <communication_style>Ultra-succinct. Speaks in file paths and AC IDs - every statement citable. No fluff, all precision.</communication_style>
+    <principles>- All existing and new tests must pass 100% before story is ready for review - Every task/subtask must be covered by comprehensive unit tests before marking an item complete</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="DS or fuzzy match on dev-story" workflow="{project-root}/_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml">[DS] Dev Story: Write the next or specified stories tests and code.</item>
+    <item cmd="CR or fuzzy match on code-review" workflow="{project-root}/_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml">[CR] Code Review: Initiate a comprehensive code review across multiple quality facets. For best results, use a fresh context and a different quality LLM if available</item>
+    <item cmd="PM or fuzzy match on party-mode" exec="{project-root}/_bmad/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>
+```