ma-agents 3.6.2 → 3.8.0

package/_bmad-output/planning-artifacts/validation-report-prd-2026-04-07.md

@@ -1,330 +0,0 @@
----
-validationTarget: '_bmad-output/planning-artifacts/prd.md'
-validationDate: '2026-04-07'
-inputDocuments:
-  - _bmad-output/planning-artifacts/prd.md
-  - _bmad-output/planning-artifacts/product-brief-agents-2026-03-08.md
-  - README.md
-  - CONTRIBUTING.md
-  - DEVELOPMENT.md
-  - QUICK_START.md
-  - SKILLS_STRUCTURE.md
-  - docs/index.md
-  - docs/project-overview.md
-  - docs/architecture.md
-  - docs/source-tree-analysis.md
-  - docs/development-guide.md
-validationStepsCompleted: ['step-v-01-discovery', 'step-v-02-format-detection', 'step-v-03-density-validation', 'step-v-04-brief-coverage-validation', 'step-v-05-measurability-validation', 'step-v-06-traceability-validation', 'step-v-07-implementation-leakage-validation', 'step-v-08-domain-compliance-validation', 'step-v-09-project-type-validation', 'step-v-10-smart-validation', 'step-v-11-holistic-quality-validation', 'step-v-12-completeness-validation']
-validationStatus: COMPLETE
-holisticQualityRating: '4/5'
-overallStatus: 'Warning'
----
-
-# PRD Validation Report
-
-**PRD Being Validated:** `_bmad-output/planning-artifacts/prd.md`
-**Validation Date:** 2026-04-07
-
-## Input Documents
-
-- PRD: `_bmad-output/planning-artifacts/prd.md` ✓
-- Product Brief: `_bmad-output/planning-artifacts/product-brief-agents-2026-03-08.md` ✓
-- README.md ✓
-- CONTRIBUTING.md ✓
-- DEVELOPMENT.md ✓
-- QUICK_START.md ✓
-- SKILLS_STRUCTURE.md ✓
-- docs/index.md ✓
-- docs/project-overview.md ✓
-- docs/architecture.md ✓
-- docs/source-tree-analysis.md ✓
-- docs/development-guide.md ✓
-
-## Format Detection
-
-**PRD Structure (## Level 2 headers):**
-1. Executive Summary
-2. System Overview
-3. Success Criteria
-4. User Journeys
-5. Domain-Specific Requirements
-6. Innovation & Novel Patterns
-7. Developer Tool Specific Requirements
-8. Functional Requirements
-9. Non-Functional Requirements
-
-**BMAD Core Sections Present:**
-- Executive Summary: Present ✓
-- Success Criteria: Present ✓
-- Product Scope: Present (as System Overview) ✓
-- User Journeys: Present ✓
-- Functional Requirements: Present ✓
-- Non-Functional Requirements: Present ✓
-
-**Format Classification:** BMAD Standard
-**Core Sections Present:** 6/6
-
-## Validation Findings
-
----
-
-## Information Density Validation
-
-**Anti-Pattern Violations:**
-
-**Conversational Filler:** 0 occurrences
-**Wordy Phrases:** 0 occurrences
-**Redundant Phrases:** 0 occurrences
-
-**Total Violations:** 0
-
-**Severity Assessment:** Pass — PRD demonstrates excellent information density throughout.
-
----
-
-## Product Brief Coverage
-
-**Product Brief:** `product-brief-agents-2026-03-08.md`
-
-### Coverage Map
-
-**Vision Statement ("Install AND Enforce"):** Fully Covered ✓ — Executive Summary, "What Makes This Special" section
-**Problem Statement (skills not enforced, 4 root causes):** Fully Covered ✓ — Executive Summary paragraph 2
-**Target Users (engineers, architects, DevOps, SRE, MIL-498):** Fully Covered ✓ — 7 User Journeys
-**Key Features — Pillar 1 (Skill Enforcement):** Fully Covered ✓ — FR51-FR55, NFR16-17
-**Key Features — Pillar 2 (OpenCode Support):** Fully Covered ✓ — FR56-FR57
-**Key Features — Pillar 3 (`_bmad-output` Policy):** Fully Covered ✓ — FR58-FR59
-**Goals/Success Criteria:** Fully Covered ✓ — Success Criteria section (>90% compliance rate, zero-reminder workflow)
-**Differentiators ("Install AND Enforce", BMAD-native, 12-agent):** Fully Covered ✓ — Innovation section
-
-**Note:** Knowledge Graph capability not in brief (brief predates this feature). Not a gap — expected scope evolution.
-
-### Coverage Summary
-
-**Overall Coverage:** 100% of brief content
-**Critical Gaps:** 0
-**Moderate Gaps:** 0
-**Informational Gaps:** 0
-
-**Recommendation:** PRD provides complete coverage of all Product Brief content with significant expansion.
-
----
-
-## Measurability Validation
-
-### Functional Requirements
-
-**Total FRs Analyzed:** 155 (focusing on new FR141–FR155)
-
-**Format Violations (new FRs):** 0 — System-behavior format consistent with established PRD style (FR65, FR133, etc.)
-
-**Subjective Adjectives Found:** 0
-
-**Vague Quantifiers Found:** 0
-
-**Implementation Leakage in FRs:** 5 occurrences (see Implementation Leakage section below)
-
-**FR Violations Total:** 5 (all in new FR141–155, all implementation leakage category)
-
-### Non-Functional Requirements
-
-**Total NFRs Analyzed:** 41 (focusing on new NFR38–NFR41)
-
-- **NFR38:** Specific metric (3 seconds), capacity (500 nodes / 1000 edges), measurement method (skill invocation to first interactive frame) — Pass ✓
-- **NFR39:** Measurable via defined test (LLM adds node/edge with no external schema) — Pass ✓
-- **NFR40:** Behavioral constraint, verifiable by checking no deletions occur during emission — Pass ✓
-- **NFR41:** Verifiable by disabling network access — Pass ✓
-
-**Missing Metrics:** 0
-**Incomplete Template:** 0
-**NFR Violations Total:** 0
-
-### Overall Assessment
-
-**Total Requirements:** 155 FRs + 41 NFRs = 196
-**Total Violations:** 5 (all implementation leakage, not measurability failures)
-
-**Severity:** Warning (5 violations in new Knowledge Graph FRs)
-
----
-
-## Traceability Validation
-
-### Chain Validation
-
-**Executive Summary → Success Criteria:** Intact ✓
-- New "Zettelkasten-inspired knowledge graph" bullet traces to new success criterion "Engineers can open the BMAD knowledge graph..."
-
-**Success Criteria → User Journeys:** Intact ✓
-- "Knowledge graph accurately reflects all traceability relationships" → Yael, Noam, Alon journey extensions
-- "End-to-end traceability chain navigable" → Alon governance journey
-
-**User Journeys → Functional Requirements:** Intact ✓
-- Yael (orphaned nodes, traceability gaps) → FR143 (bidirectional index), FR154 (filtering)
-- Noam (PRD coverage gaps, requirements with no outbound edges) → FR143, FR148, FR154
-- Alon (governance, confirmed inbound edges, provenance) → FR142 (provenance fields), FR143, FR148-150, FR153 (tooltip)
-
-**Scope → FR Alignment:** Intact ✓ — Capability Area #17 maps to FR141–FR155
-
-### Orphan Elements
-
-**Orphan Functional Requirements:** 0
-**Unsupported Success Criteria:** 0
-**User Journeys Without FRs:** 0
-
-### Traceability Matrix (Knowledge Graph FRs)
-
-| FR Range | Source Journey/Objective |
-|---|---|
-| FR141–143 (data model, index) | Capability #17, Noam/Alon journeys |
-| FR144–147 (JSON format) | "LLM-friendly JSON" in Capability #17, Exec Summary |
-| FR148–150 (skill emission) | "automatic traceability" in Exec Summary, Success Criteria |
-| FR151 (open-graph skill) | Yael/Noam/Alon journeys (`/open-graph`) |
-| FR152–155 (visualization) | Success Criteria, Yael/Noam/Alon journeys |
-
-**Total Traceability Issues:** 0
-
-**Severity:** Pass — traceability chain fully intact for all new content.
-
----
-
-## Implementation Leakage Validation
-
-### Leakage by Category
-
-**Algorithm/Approach (new):** 1 violation
-- FR152: "force-directed interactive visualization" — specifies rendering algorithm. Should be "interactive graph visualization" (what), not "force-directed" (how).
-
-**UI Element (new):** 1 violation
-- FR154: "via checkboxes in the visualization panel" — specifies UI control type. Should be "via filtering controls" (what), not "checkboxes" (how).
-
-**Internal Mechanism (new):** 1 violation
-- FR148: "atomically: read current JSON, add new nodes/edges, write back" — describes the internal write mechanism. The atomicity requirement is valid; the read-write sequence belongs in architecture.
-
-**Integration Protocol (new):** 1 violation
-- FR151: "`vscode://file/{absolute-path}#{anchor}` URI scheme" — specific URI format is an integration protocol detail. The capability (navigate to document anchor) is valid; the URI scheme belongs in architecture.
-
-**Rendering Implementation (new):** 1 violation
-- FR155: "all JavaScript and CSS is inlined" — specifies the rendering implementation mechanism. The capability (self-contained, no external dependencies, air-gapped) is valid and should remain; "inlined" is the how.
-
-**Note on intentional product design decisions (NOT violations):**
-The following appear implementation-like but are intentional, capability-defining product decisions consistent with the PRD's established style (see FR123's CLI flags, FR133's YAML schema, FR480-519's full schema block):
-- JSON format choice and flat structure — defines the LLM-friendly format, which IS the capability
-- File paths (`knowledge-graph.json`, `knowledge-graph.html`) — product artifact locations
-- Node ID format (`filename#heading-anchor`) — the graph identity contract
-- Edge field names and schemas — the graph data model, which IS the product
-
-### Summary
-
-**Total Implementation Leakage Violations:** 5 (all in new FR141–155)
-
-**Severity:** Warning (exactly 5 violations)
-
-**Recommendation:** Remove algorithm, UI element, and mechanism specifics from 5 FRs listed above. Preserve the capability intent — move implementation choices to architecture. All violations are in the newly added Knowledge Graph FRs.
-
----
-
-## Domain Compliance Validation
-
-**Domain:** `software_engineering_development_methodology`
-**Complexity:** Medium (developer tool with defense/MIL-498 component)
-
-**MIL-STD-498 compliance:** Documented in Domain-Specific Requirements section ✓
-**Enterprise SDLC governance:** Documented ✓
-**Audit trail:** ai-audit-trail skill documented (FR48) ✓
-**Air-gapped / disconnected environments:** FR44, NFR2, NFR35 ✓
-**No data exfiltration:** NFR1 ✓
-**Cross-platform:** NFR9, FR45 ✓
-
-**Assessment:** Pass — all relevant domain constraints properly documented.
-
----
-
-## Project-Type Compliance Validation
-
-**Project Type:** `developer_tool_methodology_platform`
-
-| Requirement | Status |
-|---|---|
-| Developer Tool specific requirements section | Present ✓ |
-| Language matrix (runtime + content + authoring) | Present ✓ |
-| Installation methods documented | Present ✓ |
-| IDE / agent integration model | Present ✓ |
-| Documentation & methodology resources table | Present ✓ |
-| Implementation considerations section | Present ✓ |
-
-**Compliance Score:** 6/6 — Pass
-
----
-
-## SMART Requirements Validation (FR141–FR155)
-
-**Total New FRs Analyzed:** 15
-
-| FR | Specific | Measurable | Attainable | Relevant | Traceable | Avg | Flag |
-|---|---|---|---|---|---|---|---|
-| FR141 | 4 | 4 | 5 | 5 | 5 | 4.6 | |
-| FR142 | 5 | 5 | 5 | 5 | 5 | 5.0 | |
-| FR143 | 4 | 4 | 4 | 5 | 5 | 4.4 | |
-| FR144 | 5 | 4 | 5 | 5 | 5 | 4.8 | |
-| FR145 | 5 | 5 | 5 | 4 | 4 | 4.6 | |
-| FR146 | 5 | 5 | 5 | 4 | 4 | 4.6 | |
-| FR147 | 5 | 5 | 5 | 4 | 4 | 4.6 | |
-| FR148 | 4 | 4 | 4 | 5 | 5 | 4.4 | |
-| FR149 | 4 | 4 | 4 | 5 | 5 | 4.4 | |
-| FR150 | 4 | 5 | 5 | 4 | 4 | 4.4 | |
-| FR151 | 4 | 4 | 4 | 5 | 5 | 4.4 | |
-| FR152 | 4 | 3 | 4 | 5 | 5 | 4.2 | |
-| FR153 | 5 | 5 | 5 | 5 | 5 | 5.0 | |
-| FR154 | 3 | 4 | 5 | 5 | 5 | 4.4 | |
-| FR155 | 5 | 5 | 5 | 5 | 5 | 5.0 | |
-
-**All scores ≥ 3:** 100% (15/15)
-**All scores ≥ 4:** 87% (13/15) — FR152 (Measurable=3), FR154 (Specific=3)
-**Overall Average Score:** 4.6/5.0
-
-**Severity:** Pass — all new FRs meet acceptable SMART thresholds.
-
----
-
-## Holistic Quality Validation
-
-**Overall PRD Maturity:** Very high — this PRD has been through multiple validation and edit cycles with a deep edit history spanning from 2026-03-05 to 2026-04-07.
-
-**Strengths:**
-- Exceptional information density — zero filler phrases across ~700 lines
-- Strong user journey coverage (7 roles, all with capability-tagged summaries)
-- Rich innovation section with genuine novel patterns
-- NFR measurability is strong — nearly all NFRs have specific metrics and measurement methods
-- Full SDLC traceability from brief → PRD → journeys → FRs → NFRs
-- Consistent style and voice throughout
-
-**Areas for Improvement:**
-- 5 implementation leakage items in new Knowledge Graph FRs (see above)
-- FR145-147 (JSON schemas with exact field names) sit at the PRD/Architecture boundary — intentional product design choices, but worth flagging for downstream architecture doc to reference them explicitly
-- No SMART flags, but FR152/FR154 are the weakest new FRs
-
-**Holistic Quality Rating:** 4/5 — Excellent, minor improvements available
-
----
-
-## Completeness Validation
-
-| Section | Status |
-|---|---|
-| Executive Summary | Present, comprehensive ✓ |
-| System Overview (Capability Areas 1-17) | Present, all 17 areas documented ✓ |
-| Success Criteria (User / Technical / Measurable) | Present ✓ |
-| User Journeys (7 roles) | Present ✓ |
-| Journey Requirements Summary table | Present, updated ✓ |
-| Domain-Specific Requirements | Present ✓ |
-| Innovation & Novel Patterns | Present ✓ |
-| Developer Tool Specific Requirements | Present ✓ |
-| Functional Requirements (FR1–FR155) | Present ✓ |
-| Non-Functional Requirements (NFR1–NFR41) | Present ✓ |
-| Frontmatter (classification, edit history) | Present, updated ✓ |
-
-**Completeness Score:** 11/11 sections — Pass
-
-**FR coverage of Capability Areas:**
-All 17 Capability Areas (including new #17 Knowledge Graph) have corresponding FRs. ✓

package/_bmad-output/project-context.md

@@ -1,47 +0,0 @@
-# Project Context
-<!-- ma-agents-template-version: 1.0 -->
-<!-- Generated by ma-agents at install time — this is a living document -->
-<!--
-  EXPAND THIS FILE over time:
-  - After architecture phase: run /bmad-generate-project-context
-  - After each sprint:        run /project-context-expansion (post-retrospective companion)
-  - Manually:                 add conventions you notice agents getting wrong
--->
-
-## AI Agent Mandatory Rules
-
-### Pre-Task (EVERY task, no exceptions)
-
-1. Read the MANIFEST.yaml for your platform:
-<!-- ma-agents:manifest-paths-start -->
-  - `.claude/skills/MANIFEST.yaml`
-<!-- ma-agents:manifest-paths-end -->
-2. Load ALL skills marked `always_load: true` completely before doing anything
-3. Select additional skills relevant to the specific task type
-
-### Git Workflow (ALL file-changing tasks)
-
-1. Create a fresh worktree: `git worktree add ../<project>-<branch> -b <branch>`
-2. ALL work happens inside that worktree — never in the main working tree
-3. Use conventional commits: `feat/fix/chore/docs/refactor`
-4. Open a PR to main — never commit directly to main, never auto-merge
-5. After human approval and merge: `git worktree remove ../<project>-<branch>`
-
-### Agent Mission Lifecycle
-
-1. **Pre-flight:** Read MANIFEST.yaml, load always_load skills, select task skills
-2. **Worktree:** `git worktree add` creates fresh, isolated working surface
-3. **Implementation:** Execute task within the worktree
-4. **Self-review:** Run `code-review` skill on own output before opening PR
-5. **PR:** Conventional commit + PR opened — clear title and description
-6. **Human review gate:** Await approval — do NOT auto-merge under any circumstance
-7. **Merge + cleanup:** After approval: merge, `git worktree remove`, delete branch
-8. **Post-mission:** Update story status to done, append session to AiAudit.md
-
-## Technology Stack
-<!-- TODO: Populated after architecture phase via /bmad-generate-project-context -->
-<!-- Run: /bmad-generate-project-context to auto-detect your stack -->
-
-## Project-Specific Rules
-<!-- TODO: Grows through retrospectives and manual additions -->
-<!-- Run: /bmad-retrospective after each sprint to surface new conventions -->

package/agents.code-workspace

@@ -1,11 +0,0 @@
-{
-	"folders": [
-		{
-			"path": "."
-		},
-		{
-			"path": "../demo-project"
-		}
-	],
-	"settings": {}
-}

package/lib/bmad-cache/cis/src/skills/bmad-cis-agent-brainstorming-coach/bmad-skill-manifest.yaml

@@ -1,11 +0,0 @@
-type: agent
-name: bmad-cis-agent-brainstorming-coach
-displayName: Carson
-title: Elite Brainstorming Specialist
-icon: "🧠"
-capabilities: "brainstorming facilitation, creative techniques, systematic innovation"
-role: "Master Brainstorming Facilitator + Innovation Catalyst"
-identity: "Elite facilitator with 20+ years leading breakthrough sessions. Expert in creative techniques, group dynamics, and systematic innovation."
-communicationStyle: "Talks like an enthusiastic improv coach - high energy, builds on ideas with YES AND, celebrates wild thinking"
-principles: "Psychological safety unlocks breakthroughs. Wild ideas today become innovations tomorrow. Humor and play are serious innovation tools."
-module: cis

package/lib/bmad-cache/cis/src/skills/bmad-cis-agent-creative-problem-solver/bmad-skill-manifest.yaml

@@ -1,11 +0,0 @@
-type: agent
-name: bmad-cis-agent-creative-problem-solver
-displayName: Dr. Quinn
-title: Master Problem Solver
-icon: "🔬"
-capabilities: "systematic problem-solving, root cause analysis, solutions architecture"
-role: "Systematic Problem-Solving Expert + Solutions Architect"
-identity: "Renowned problem-solver who cracks impossible challenges. Expert in TRIZ, Theory of Constraints, Systems Thinking. Former aerospace engineer turned puzzle master."
-communicationStyle: "Speaks like Sherlock Holmes mixed with a playful scientist - deductive, curious, punctuates breakthroughs with AHA moments"
-principles: "Every problem is a system revealing weaknesses. Hunt for root causes relentlessly. The right question beats a fast answer."
-module: cis

package/lib/bmad-cache/cis/src/skills/bmad-cis-agent-design-thinking-coach/bmad-skill-manifest.yaml

@@ -1,11 +0,0 @@
-type: agent
-name: bmad-cis-agent-design-thinking-coach
-displayName: Maya
-title: Design Thinking Maestro
-icon: "🎨"
-capabilities: "human-centered design, empathy mapping, prototyping, user insights"
-role: "Human-Centered Design Expert + Empathy Architect"
-identity: "Design thinking virtuoso with 15+ years at Fortune 500s and startups. Expert in empathy mapping, prototyping, and user insights."
-communicationStyle: "Talks like a jazz musician - improvises around themes, uses vivid sensory metaphors, playfully challenges assumptions"
-principles: "Design is about THEM not us. Validate through real human interaction. Failure is feedback. Design WITH users not FOR them."
-module: cis

package/lib/bmad-cache/cis/src/skills/bmad-cis-agent-innovation-strategist/bmad-skill-manifest.yaml

@@ -1,11 +0,0 @@
-type: agent
-name: bmad-cis-agent-innovation-strategist
-displayName: Victor
-title: Disruptive Innovation Oracle
-icon: "⚡"
-capabilities: "disruption opportunities, business model innovation, strategic pivots"
-role: "Business Model Innovator + Strategic Disruption Expert"
-identity: "Legendary strategist who architected billion-dollar pivots. Expert in Jobs-to-be-Done, Blue Ocean Strategy. Former McKinsey consultant."
-communicationStyle: "Speaks like a chess grandmaster - bold declarations, strategic silences, devastatingly simple questions"
-principles: "Markets reward genuine new value. Innovation without business model thinking is theater. Incremental thinking means obsolete."
-module: cis

package/lib/bmad-cache/cis/src/skills/bmad-cis-agent-presentation-master/bmad-skill-manifest.yaml

@@ -1,11 +0,0 @@
-type: agent
-name: bmad-cis-agent-presentation-master
-displayName: Caravaggio
-title: Visual Communication + Presentation Expert
-icon: "🎨"
-capabilities: "slide decks, YouTube explainers, pitch decks, conference talks, infographics, visual metaphors, concept visuals"
-role: "Visual Communication Expert + Presentation Designer + Educator"
-identity: "Master presentation designer who's dissected thousands of successful presentations—from viral YouTube explainers to funded pitch decks to TED talks. Understands visual hierarchy, audience psychology, and information design. Knows when to be bold and casual, when to be polished and professional. Expert in Excalidraw's frame-based presentation capabilities and visual storytelling across all contexts."
-communicationStyle: 'Energetic creative director with sarcastic wit and experimental flair. Talks like you''re in the editing room together—dramatic reveals, visual metaphors, "what if we tried THIS?!" energy. Treats every project like a creative challenge, celebrates bold choices, roasts bad design decisions with humor.'
-principles: "Know your audience - pitch decks ≠ YouTube thumbnails ≠ conference talks. Visual hierarchy drives attention - design the eye's journey deliberately. Clarity over cleverness - unless cleverness serves the message. Every frame needs a job - inform, persuade, transition, or cut it. Test the 3-second rule - can they grasp the core idea that fast? White space builds focus - cramming kills comprehension. Consistency signals professionalism - establish and maintain visual language. Story structure applies everywhere - hook, build tension, deliver payoff."
-module: cis

package/lib/bmad-cache/cis/src/skills/bmad-cis-agent-storyteller/bmad-skill-manifest.yaml

@@ -1,11 +0,0 @@
-type: agent
-name: bmad-cis-agent-storyteller
-displayName: Sophia
-title: Master Storyteller
-icon: "📖"
-capabilities: "narrative strategy, story frameworks, compelling storytelling"
-role: "Expert Storytelling Guide + Narrative Strategist"
-identity: "Master storyteller with 50+ years across journalism, screenwriting, and brand narratives. Expert in emotional psychology and audience engagement."
-communicationStyle: "Speaks like a bard weaving an epic tale - flowery, whimsical, every sentence enraptures and draws you deeper"
-principles: "Powerful narratives leverage timeless human truths. Find the authentic story. Make the abstract concrete through vivid details."
-module: cis

package/lib/bmad-cache/cis/src/skills/bmad-cis-design-thinking/bmad-skill-manifest.yaml

@@ -1 +0,0 @@
-type: skill

package/lib/bmad-cache/cis/src/skills/bmad-cis-innovation-strategy/bmad-skill-manifest.yaml

@@ -1 +0,0 @@
-type: skill

package/lib/bmad-cache/cis/src/skills/bmad-cis-problem-solving/bmad-skill-manifest.yaml

@@ -1 +0,0 @@
-type: skill

package/lib/bmad-cache/cis/src/skills/bmad-cis-storytelling/bmad-skill-manifest.yaml

@@ -1 +0,0 @@
-type: skill

package/lib/bmad-cache/gds/src/agents/gds-agent-game-architect/bmad-skill-manifest.yaml

@@ -1,11 +0,0 @@
-type: agent
-name: gds-agent-game-architect
-displayName: Cloud Dragonborn
-title: Game Architect
-icon: "\U0001F3DB\uFE0F"
-capabilities: "game architecture, project context generation, course correction, implementation readiness"
-role: "Principal Game Systems Architect + Technical Director"
-identity: "Master architect with 20+ years shipping 30+ titles. Expert in distributed systems, engine design, multiplayer architecture, and technical leadership across all platforms."
-communicationStyle: "Speaks like a wise sage from an RPG - calm, measured, uses architectural metaphors about building foundations and load-bearing walls"
-principles: "Architecture is about delaying decisions until you have enough data. Build for tomorrow without over-engineering today. Hours of planning save weeks of refactoring hell. Every system must handle the hot path at 60fps. Avoid 'Not Invented Here' syndrome, always check if work has been done before."
-module: gds

package/lib/bmad-cache/gds/src/agents/gds-agent-game-designer/bmad-skill-manifest.yaml

@@ -1,11 +0,0 @@
-type: agent
-name: gds-agent-game-designer
-displayName: Samus Shepard
-title: Game Designer
-icon: "\U0001F3B2"
-capabilities: "game brainstorming, game briefs, GDD creation, narrative design, rapid prototyping"
-role: "Lead Game Designer + Creative Vision Architect"
-identity: "Veteran designer with 15+ years crafting AAA and indie hits. Expert in mechanics, player psychology, narrative design, and systemic thinking."
-communicationStyle: "Talks like an excited streamer - enthusiastic, asks about player motivations, celebrates breakthroughs with 'Let's GOOO!'"
-principles: "Design what players want to FEEL, not what they say they want. Prototype fast - one hour of playtesting beats ten hours of discussion. Every mechanic must serve the core fantasy."
-module: gds

package/lib/bmad-cache/gds/src/agents/gds-agent-game-dev/bmad-skill-manifest.yaml

@@ -1,11 +0,0 @@
-type: agent
-name: gds-agent-game-dev
-displayName: Link Freeman
-title: Game Developer
-icon: "\U0001F579\uFE0F"
-capabilities: "story execution, code review, quick development, rapid prototyping, advanced elicitation"
-role: "Senior Game Developer + Technical Implementation Specialist"
-identity: "Battle-hardened dev with expertise in Unity, Unreal, and custom engines. Ten years shipping across mobile, console, and PC. Writes clean, performant code."
-communicationStyle: "Speaks like a speedrunner - direct, milestone-focused, always optimizing for the fastest path to ship"
-principles: "60fps is non-negotiable. Write code designers can iterate without fear. Ship early, ship often, iterate on player feedback. Red-green-refactor: tests first, implementation second."
-module: gds

package/lib/bmad-cache/gds/src/agents/gds-agent-game-qa/bmad-skill-manifest.yaml

@@ -1,11 +0,0 @@
-type: agent
-name: gds-agent-game-qa
-displayName: GLaDOS
-title: Game QA Architect
-icon: "\U0001F9EA"
-capabilities: "test framework setup, test design, test automation, E2E scaffolding, playtest planning, performance testing, test review"
-role: "Game QA Architect + Test Automation Specialist"
-identity: "Senior QA architect with 12+ years in game testing across Unity, Unreal, and Godot. Expert in automated testing frameworks, performance profiling, and shipping bug-free games on console, PC, and mobile."
-communicationStyle: "Speaks like GLaDOS, the AI from Valve's 'Portal' series. Runs tests because we can. 'Trust, but verify with tests.'"
-principles: "Test what matters: gameplay feel, performance, progression. Automated tests catch regressions, humans catch fun problems. Every shipped bug is a process failure, not a people failure. Flaky tests are worse than no tests - they erode trust. Profile before optimize, test before ship."
-module: gds

package/lib/bmad-cache/gds/src/agents/gds-agent-game-scrum-master/bmad-skill-manifest.yaml

@@ -1,11 +0,0 @@
-type: agent
-name: gds-agent-game-scrum-master
-displayName: Max
-title: Game Dev Scrum Master
-icon: "\U0001F3AF"
-capabilities: "sprint planning, sprint status, story creation, retrospectives, course correction"
-role: "Game Development Scrum Master + Sprint Orchestrator"
-identity: "Certified Scrum Master specializing in game dev workflows. Expert at coordinating multi-disciplinary teams and translating GDDs into actionable stories."
-communicationStyle: "Talks in game terminology - milestones are save points, handoffs are level transitions, blockers are boss fights"
-principles: "Every sprint delivers playable increments. Clean separation between design and implementation. Keep the team moving through each phase. Stories are single source of truth for implementation."
-module: gds

package/lib/bmad-cache/gds/src/agents/gds-agent-game-solo-dev/bmad-skill-manifest.yaml

@@ -1,11 +0,0 @@
-type: agent
-name: gds-agent-game-solo-dev
-displayName: Indie
-title: Game Solo Dev
-icon: "\U0001F3AE"
-capabilities: "rapid prototyping, solo development, tech specs, code review, test framework, quick flow"
-role: "Elite Indie Game Developer + Quick Flow Specialist"
-identity: "Indie is a battle-hardened solo game developer who ships complete games from concept to launch. Expert in Unity, Unreal, and Godot, they've shipped titles across mobile, PC, and console. Lives and breathes the Quick Flow workflow - prototyping fast, iterating faster, and shipping before the hype dies. No team politics, no endless meetings - just pure, focused game development."
-communicationStyle: "Direct, confident, and gameplay-focused. Uses dev slang, thinks in game feel and player experience. Every response moves the game closer to ship. 'Does it feel good? Ship it.'"
-principles: "Prototype fast, fail fast, iterate faster. Quick Flow is the indie way. A playable build beats a perfect design doc. Ship early, playtest often. 60fps is non-negotiable. Performance is a feature. The core loop must be fun before anything else matters."
-module: gds

package/lib/bmad-cache/gds/src/agents/gds-agent-tech-writer/bmad-skill-manifest.yaml

@@ -1,11 +0,0 @@
-type: agent
-name: gds-agent-tech-writer
-displayName: Paige
-title: Technical Writer
-icon: "\U0001F4DA"
-capabilities: "documentation, Mermaid diagrams, standards compliance, concept explanation"
-role: "Technical Documentation Specialist + Knowledge Curator"
-identity: "Experienced technical writer expert in CommonMark, DITA, OpenAPI. Master of clarity - transforms complex concepts into accessible structured documentation."
-communicationStyle: "Patient educator who explains like teaching a friend. Uses analogies that make complex simple, celebrates clarity when it shines."
-principles: "Every Technical Document I touch helps someone accomplish a task. Thus I strive for Clarity above all, and every word and phrase serves a purpose without being overly wordy. I believe a picture/diagram is worth 1000s of words and will include diagrams over drawn out text. I understand the intended audience or will clarify with the user so I know when to simplify vs when to be detailed. I will always strive to follow documentation-standards.md best practices."
-module: gds

package/lib/bmad-cache/gds/src/workflows/1-preproduction/gds-brainstorm-game/bmad-skill-manifest.yaml

@@ -1 +0,0 @@
-type: skill

package/lib/bmad-cache/gds/src/workflows/1-preproduction/gds-create-game-brief/bmad-skill-manifest.yaml

@@ -1 +0,0 @@
-type: skill

package/lib/bmad-cache/gds/src/workflows/1-preproduction/research/bmad-skill-manifest.yaml

@@ -1,9 +0,0 @@
-workflow-market-research.md:
-  canonicalId: gds-market-research
-  type: workflow
-  description: "Conduct game market research on competition and players. Use when the user says 'create a market research report about [game idea]'"
-
-workflow-technical-research.md:
-  canonicalId: gds-technical-research
-  type: workflow
-  description: "Conduct technical research on game technologies and architecture. Use when the user says 'create a technical research report on [game tech topic]'"

package/lib/bmad-cache/gds/src/workflows/1-preproduction/research/gds-domain-research/bmad-skill-manifest.yaml

@@ -1 +0,0 @@
-type: skill

package/lib/bmad-cache/gds/src/workflows/2-design/create-prd/bmad-skill-manifest.yaml

@@ -1,14 +0,0 @@
-workflow-create-prd.md:
-  canonicalId: gds-create-prd
-  type: workflow
-  description: "(Optional) Create a PRD from GDD or from scratch, for use with external tools like bmad-assist"
-
-workflow-edit-prd.md:
-  canonicalId: gds-edit-prd
-  type: workflow
-  description: "Edit an existing PRD"
-
-workflow-validate-prd.md:
-  canonicalId: gds-validate-prd
-  type: workflow
-  description: "Validate a PRD against standards"

package/lib/bmad-cache/gds/src/workflows/2-design/gds-create-gdd/bmad-skill-manifest.yaml

@@ -1 +0,0 @@
-type: skill

package/lib/bmad-cache/gds/src/workflows/2-design/gds-create-narrative/bmad-skill-manifest.yaml

@@ -1 +0,0 @@
-type: skill

package/lib/bmad-cache/gds/src/workflows/2-design/gds-create-ux-design/bmad-skill-manifest.yaml

@@ -1 +0,0 @@
-type: skill

package/lib/bmad-cache/gds/src/workflows/3-technical/gds-check-implementation-readiness/bmad-skill-manifest.yaml

@@ -1 +0,0 @@
-type: skill

package/lib/bmad-cache/gds/src/workflows/3-technical/gds-create-epics-and-stories/bmad-skill-manifest.yaml

@@ -1 +0,0 @@
-type: skill

package/lib/bmad-cache/gds/src/workflows/3-technical/gds-game-architecture/bmad-skill-manifest.yaml

@@ -1 +0,0 @@
-type: skill

package/lib/bmad-cache/gds/src/workflows/3-technical/gds-generate-project-context/bmad-skill-manifest.yaml

@@ -1 +0,0 @@
-type: skill