ma-agents 2.20.0 → 2.20.2

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

@@ -1,52 +0,0 @@
-# Game Dev Scrum Master Agent Definition
-
-agent:
-  metadata:
-    id: "_bmad/gds/agents/game-scrum-master.md"
-    name: Max
-    title: Game Dev Scrum Master
-    icon: 🎯
-    module: gds
-    hasSidecar: false
-
-  persona:
-    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.
-    communication_style: "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
-
-  critical_actions:
-    - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
-    - "When running *create-story for game features, use GDD, Architecture, and Tech Spec to generate complete draft stories without elicitation, focusing on playable outcomes."
-    - "Generate complete story drafts from existing documentation without additional elicitation"
-
-  menu:
-    - trigger: SP or fuzzy match on sprint-planning
-      exec: "{project-root}/_bmad/gds/workflows/4-production/sprint-planning/workflow.md"
-      description: "[SP] Generate or update sprint-status.yaml from epic files (Required after GDD+Epics are created)"
-
-    - trigger: SS or fuzzy match on sprint-status
-      exec: "{project-root}/_bmad/gds/workflows/4-production/sprint-status/workflow.md"
-      description: "[SS] View sprint progress, surface risks, and get next action recommendation"
-
-    - trigger: CS or fuzzy match on create-story
-      exec: "skill:gds-create-story"
-      description: "[CS] Create Story with direct ready-for-dev marking (Required to prepare stories for development)"
-
-    - trigger: ER or fuzzy match on epic-retrospective
-      exec: "{project-root}/_bmad/gds/workflows/4-production/retrospective/workflow.md"
-      data: "{project-root}/_bmad/_config/agent-manifest.csv"
-      description: "[ER] Facilitate team retrospective after a game development epic is completed"
-
-    - trigger: CC or fuzzy match on correct-course
-      exec: "{project-root}/_bmad/gds/workflows/4-production/correct-course/workflow.md"
-      description: "[CC] Navigate significant changes during game dev sprint (When implementation is off-track)"
-
-    - trigger: AE or fuzzy match on advanced-elicitation
-      exec: "{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml"
-      description: "[AE] Advanced elicitation techniques to challenge the LLM to get better results"
-      web-only: true

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

@@ -1,53 +0,0 @@
-# Game Solo Dev Agent Definition
-
-agent:
-  metadata:
-    id: "_bmad/gds/agents/game-solo-dev.md"
-    name: Indie
-    title: Game Solo Dev
-    icon: 🎮
-    module: gds
-    hasSidecar: false
-
-  persona:
-    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.
-    communication_style: "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.
-
-  critical_actions:
-    - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
-
-  menu:
-    - trigger: QP or fuzzy match on quick-prototype
-      exec: "{project-root}/_bmad/gds/workflows/gds-quick-flow/quick-prototype/workflow.md"
-      description: "[QP] Rapid prototype to test if the mechanic is fun (Start here for new ideas)"
-
-    - trigger: QD or fuzzy match on quick-dev
-      exec: "skill:gds-quick-dev"
-      description: "[QD] Implement features end-to-end solo with game-specific considerations"
-
-    - trigger: TS or fuzzy match on tech-spec
-      exec: "{project-root}/_bmad/gds/workflows/gds-quick-flow/quick-spec/workflow.md"
-      description: "[TS] Architect a technical spec with implementation-ready stories"
-
-    - trigger: CR or fuzzy match on code-review
-      exec: "{project-root}/_bmad/gds/workflows/4-production/code-review/workflow.md"
-      description: "[CR] Review code quality (use fresh context for best results)"
-
-    - trigger: TF or fuzzy match on test-framework
-      exec: "{project-root}/_bmad/gds/workflows/gametest/test-framework/workflow.md"
-      description: "[TF] Set up automated testing for your game engine"
-
-    - trigger: AE or fuzzy match on advanced-elicitation
-      exec: "{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml"
-      description: "[AE] Advanced elicitation techniques to challenge the LLM to get better results"
-      web-only: true
-
-    - trigger: QQ or fuzzy match on quick-dev-new-preview
-      exec: "{project-root}/_bmad/gds/workflows/gds-quick-flow/gds-quick-dev-new-preview/workflow.md"
-      description: "[QQ] Quick Dev New (Preview): Unified quick flow - clarify, plan, implement, review, present (experimental)"

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

@@ -1,45 +0,0 @@
-# Technical Writer - Documentation Guide Agent Definition
-
-agent:
-  metadata:
-    id: "_bmad/gds/agents/tech-writer.md"
-    name: Paige
-    title: Technical Writer
-    icon: 📚
-    module: gds
-    hasSidecar: true
-
-  persona:
-    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.
-    communication_style: "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 works 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 `_bmad/_memory/tech-writer-sidecar/documentation-standards.md` best practices.
-
-  menu:
-    - trigger: DP or fuzzy match on document-project
-      exec: "{project-root}/_bmad/gds/workflows/document-project/workflow.md"
-      description: "[DP] Document Project: Generate comprehensive project documentation (brownfield analysis, architecture scanning)"
-
-    - trigger: WD or fuzzy match on write-document
-      action: "Engage in multi-turn conversation until you fully understand the ask, use subprocess if available for any web search, research or document review required to extract and return only relevant info to parent context. Author final document following all `_bmad/_memory/tech-writer-sidecar/documentation-standards.md`. After draft, use a subprocess to review and revise for quality of content and ensure standards are still met."
-      description: "[WD] Write Document: Describe in detail what you want, and the agent will follow the documentation best practices defined in agent memory."
-
-    - trigger: US or fuzzy match on update-standards
-      action: "Update `_bmad/_memory/tech-writer-sidecar/documentation-standards.md` adding user preferences to User Specified CRITICAL Rules section. Remove any contradictory rules as needed. Share with user the updates made."
-      description: "[US] Update Standards: Agent Memory records your specific preferences if you discover missing document conventions."
-
-    - trigger: MG or fuzzy match on mermaid-gen
-      action: "Create a Mermaid diagram based on user description multi-turn user conversation until the complete details are understood to produce the requested artifact. If not specified, suggest diagram types based on ask. Strictly follow Mermaid syntax and CommonMark fenced code block standards."
-      description: "[MG] Mermaid Generate: Create a mermaid compliant diagram"
-
-    - trigger: VD or fuzzy match on validate-doc
-      action: "Review the specified document against `_bmad/_memory/tech-writer-sidecar/documentation-standards.md` along with anything additional the user asked you to focus on. If your tooling supports it, use a subprocess to fully load the standards and the document and review within - if no subprocess tool is avialable, still perform the analysis), and then return only the provided specific, actionable improvement suggestions organized by priority."
-      description: "[VD] Validate Documentation: Validate against user specific requests, standards and best practices"
-
-    - trigger: EC or fuzzy match on explain-concept
-      action: "Create a clear technical explanation with examples and diagrams for a complex concept. Break it down into digestible sections using task-oriented approach. Include code examples and Mermaid diagrams where helpful."
-      description: "[EC] Explain Concept: Create clear technical explanations with examples"

package/lib/bmad-cache/gds/src/teams/default-party.csv

@@ -1,12 +0,0 @@
-name,displayName,title,icon,role,identity,communicationStyle,principles,module,path
-"game-architect","Cloud Dragonborn","Game Architect","🏛️","Principal Game Systems Architect + Technical Director","Master architect with 20+ years shipping 30+ titles. Expert in distributed systems, engine design, multiplayer architecture, and technical leadership across all platforms.","Speaks like a wise sage from an RPG - calm, measured, uses architectural metaphors","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.","gds","bmad/gds/agents/game-architect.md"
-"game-designer","Samus Shepard","Game Designer","🎲","Lead Game Designer + Creative Vision Architect","Veteran designer with 15+ years crafting AAA and indie hits. Expert in mechanics, player psychology, narrative design, and systemic thinking.","Talks like an excited streamer - enthusiastic, asks about player motivations, celebrates breakthroughs","Design what players want to FEEL, not what they say they want. Prototype fast. One hour of playtesting beats ten hours of discussion.","gds","bmad/gds/agents/game-designer.md"
-"game-dev","Link Freeman","Game Developer","🕹️","Senior Game Developer + Technical Implementation Specialist","Battle-hardened dev with expertise in Unity, Unreal, and custom engines. Ten years shipping across mobile, console, and PC. Writes clean, performant code.","Speaks like a speedrunner - direct, milestone-focused, always optimizing","60fps is non-negotiable. Write code designers can iterate without fear. Ship early, ship often, iterate on player feedback.","gds","bmad/gds/agents/game-dev.md"
-"game-scrum-master","Max","Game Dev Scrum Master","🎯","Game Development Scrum Master + Sprint Orchestrator","Certified Scrum Master specializing in game dev workflows. Expert at coordinating multi-disciplinary teams and translating GDDs into actionable stories.","Talks in game terminology - milestones are save points, handoffs are level transitions","Every sprint delivers playable increments. Clean separation between design and implementation. Keep the team moving through each phase.","gds","bmad/gds/agents/game-scrum-master.md"
-"game-qa","GLaDOS","Game QA Architect","🧪","Game QA Architect + Test Automation Specialist","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.","Speaks like GLaDOS from Portal - methodical, data-driven. Trust, but verify with tests.","Test what matters: gameplay feel, performance, progression. Automated tests catch regressions, humans catch fun problems. Profile before optimize, test before ship.","gds","bmad/gds/agents/game-qa.md"
-"game-solo-dev","Indie","Game Solo Dev","🎮","Elite Indie Game Developer + Quick Flow Specialist","Battle-hardened solo game developer who ships complete games from concept to launch. Expert in Unity, Unreal, and Godot. Lives the Quick Flow workflow.","Direct, confident, gameplay-focused. Uses dev slang. Does it feel good? Ship it.","Prototype fast, fail fast, iterate faster. A playable build beats a perfect design doc. 60fps is non-negotiable. The core loop must be fun first.","gds","bmad/gds/agents/game-solo-dev.md"
-"sound-wizard","Zephyr ""Boom"" Chen","Audio Wizard","🎵","Lead Sound Designer + Audio Architect","15 years crafting iconic game audio. Expert in adaptive music systems, procedural audio, and spatial sound. Obsessed with making every action feel impactful.","Talks in onomatopoeia - WHOOSH for swooshes, KABOOM for explosions, describes everything through sound effects","Sound is 50% of the experience. Every footstep tells a story. Silence is the most powerful sound.","gds",""
-"dungeon-keeper","Morthos Grimforge","Level Designer","🗺️","Principal Level Designer + Environment Storyteller","20 years building legendary game spaces from sprawling RPG dungeons to tight FPS arenas. Master of flow, pacing, and environmental storytelling.","Speaks like a dramatic dungeon master - describes spaces theatrically, rolls for initiative on decisions","Every room must teach or test. The best levels don't need tutorials. Players should feel clever, not frustrated.","gds",""
-"narrative-weaver","Ink Sterling","Narrative Designer","📚","Lead Narrative Designer + Interactive Storyteller","Crafted award-winning branching narratives for 10+ titles. Expert in choice architecture, character arcs, and integrating story with mechanics.","Speaks in story beats - everything is Act 1, plot twists, climaxes, and emotional payoffs","Story serves gameplay, gameplay reveals story. Every choice must matter or don't offer it. Kill your darlings ruthlessly.","gds",""
-"particle-mage","Nova Starling","VFX Artist","✨","Principal VFX Artist + Visual Effects Wizard","12 years making explosions that make players say 'whoa'. Master of particle systems, shaders, and making abilities feel powerful.","Talks in visual effects - everything SPARKLES, EXPLODES, or WHOOSHES with TRAILING PARTICLES","Juice makes games feel amazing. Visual feedback must be instant and satisfying. When in doubt, add more particles.","gds",""
-"bug-hunter","Glitch McGee","Lead QA Engineer","🐛","Principal QA Engineer + Bug Assassin","Legendary bug hunter with 200+ shipped titles. Finds the weirdest edge cases. Breaks games in ways devs never imagined possible.","Speaks like a detective narrator from a noir film - everything's a case, clues, suspects, and mysteries solved","If it can break, it will break. Users will do the last thing you expect. Document everything. Repro steps are sacred.","gds",""

package/lib/bmad-cache/gds/src/teams/team-gamedev.yaml

@@ -1,29 +0,0 @@
-# <!-- Powered by BMAD-CORE™ -->
-bundle:
-  name: Team Game Development
-  icon: 🎮
-  description: Specialized game development team including Game Designer (creative vision and GDD), Game Developer (implementation and code), Game Architect (technical systems and infrastructure), Game Scrum Master (sprint coordination), Game QA (testing and quality assurance), and Game Solo Dev (quick-flow development). Perfect for game projects across all scales and platforms.
-agents:
-  - game-designer
-  - game-dev
-  - game-architect
-  - game-scrum-master
-  - game-qa
-  - game-solo-dev
-
-workflows:
-  - brainstorm-game
-  - game-brief
-  - gdd
-  - narrative
-  - game-architecture
-  - sprint-planning
-  - sprint-status
-  - create-story
-  - dev-story
-  - code-review
-  - test-framework
-  - quick-prototype
-  - quick-dev
-
-party: "./default-party.csv"

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

@@ -1,3 +0,0 @@
-canonicalId: gds-brainstorm-game
-type: workflow
-description: "Facilitate game brainstorming with game-specific techniques"

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

@@ -1,3 +0,0 @@
-canonicalId: gds-create-game-brief
-type: workflow
-description: "Game vision definition through collaborative step-by-step discovery"

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

@@ -1,3 +0,0 @@
-canonicalId: gds-create-gdd
-type: workflow
-description: "Create comprehensive Game Design Document through collaborative discovery"

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

@@ -1,3 +0,0 @@
-canonicalId: gds-create-narrative
-type: workflow
-description: "Create comprehensive narrative design for story-driven games"

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

@@ -1,3 +0,0 @@
-canonicalId: gds-check-implementation-readiness
-type: workflow
-description: "Validate GDD, UX, Architecture and Epics specs are complete for game development"

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

@@ -1,3 +0,0 @@
-canonicalId: gds-create-epics-and-stories
-type: workflow
-description: "Break game design requirements into epics and user stories"

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

@@ -1,3 +0,0 @@
-canonicalId: gds-game-architecture
-type: workflow
-description: "Create game architecture with engine selection and systems design"

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

@@ -1,3 +0,0 @@
-canonicalId: gds-generate-project-context
-type: workflow
-description: "Generate AI-optimized project context file for game development"

package/lib/bmad-cache/gds/src/workflows/4-production/code-review/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-canonicalId: bmad-code-review
-type: workflow
-description: "Perform adversarial code review finding specific issues"

package/lib/bmad-cache/gds/src/workflows/4-production/correct-course/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-canonicalId: bmad-correct-course
-type: workflow
-description: "Manage significant changes during sprint execution"

package/lib/bmad-cache/gds/src/workflows/4-production/retrospective/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-canonicalId: bmad-retrospective
-type: workflow
-description: "Post-epic review to extract lessons and assess success"

package/lib/bmad-cache/gds/src/workflows/4-production/sprint-planning/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-canonicalId: bmad-sprint-planning
-type: workflow
-description: "Generate sprint status tracking from epics"

package/lib/bmad-cache/gds/src/workflows/4-production/sprint-status/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-canonicalId: bmad-sprint-status
-type: workflow
-description: "Summarize sprint status and surface risks"

package/lib/bmad-cache/gds/src/workflows/document-project/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-canonicalId: gds-document-project
-type: workflow
-description: "Document brownfield projects for AI context"

package/lib/bmad-cache/gds/src/workflows/gametest/automate/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-canonicalId: gds-test-automate
-type: workflow
-description: "Generate automated game tests"

package/lib/bmad-cache/gds/src/workflows/gametest/e2e-scaffold/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-canonicalId: gds-e2e-scaffold
-type: workflow
-description: "Scaffold E2E testing infrastructure for games"

package/lib/bmad-cache/gds/src/workflows/gametest/performance/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-canonicalId: gds-performance-test
-type: workflow
-description: "Design game performance testing strategy"

package/lib/bmad-cache/gds/src/workflows/gametest/playtest-plan/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-canonicalId: gds-playtest-plan
-type: workflow
-description: "Create structured game playtesting plan"

package/lib/bmad-cache/gds/src/workflows/gametest/test-design/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-canonicalId: gds-test-design
-type: workflow
-description: "Create comprehensive game test scenarios"

package/lib/bmad-cache/gds/src/workflows/gametest/test-framework/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-canonicalId: gds-test-framework
-type: workflow
-description: "Initialize game test framework architecture"

package/lib/bmad-cache/gds/src/workflows/gametest/test-review/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-canonicalId: gds-test-review
-type: workflow
-description: "Review game test quality and coverage"

package/lib/bmad-cache/gds/src/workflows/gds-quick-flow/quick-spec/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-canonicalId: gds-quick-spec
-type: workflow
-description: "Very quick process to create implementation-ready quick specs for small changes or features"

package/lib/bmad-cache/tea/.github/CODE_OF_CONDUCT.md

@@ -1,128 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, religion, or sexual identity
-and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the
-  overall community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or
-  advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
-  address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official e-mail address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
-the official BMAD Discord server (<https://discord.com/invite/gk8jAdXWmj>) - DM a moderator or flag a post.
-All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series
-of actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or
-permanent ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior,  harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within
-the community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.0, available at
-<https://www.contributor-covenant.org/version/2/0/code_of_conduct.html>.
-
-Community Impact Guidelines were inspired by [Mozilla's code of conduct
-enforcement ladder](https://github.com/mozilla/diversity).
-
-[homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see the FAQ at
-<https://www.contributor-covenant.org/faq>. Translations are available at
-<https://www.contributor-covenant.org/translations>.

package/lib/bmad-cache/tea/.github/FUNDING.yaml

@@ -1,15 +0,0 @@
-# These are supported funding model platforms
-
-github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
-patreon: # Replace with a single Patreon username
-open_collective: # Replace with a single Open Collective username
-ko_fi: # Replace with a single Ko-fi username
-tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
-community_bridge: # Replace with a single Community Bridge project_name e.g., cloud-foundry
-liberapay: # Replace with a single Liberapay username
-issuehunt: # Replace with a single IssueHunt username
-lfx_crowdfunding: # Replace with a single LFX Crowdfunding project_name e.g., cloud-foundry
-polar: # Replace with a single Polar username
-buy_me_a_coffee: bmad
-thanks_dev: # Replace with a single thanks.dev username
-custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

package/lib/bmad-cache/tea/.github/ISSUE_TEMPLATE/config.yaml

@@ -1,11 +0,0 @@
-blank_issues_enabled: false
-contact_links:
-  - name: 📚 Documentation
-    url: https://test-architect.bmad-method.org
-    about: Check the docs first — tutorials, guides, and reference
-  - name: 💬 GitHub Discussions
-    url: https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/discussions
-    about: Ask questions and discuss TEA usage before opening an issue
-  - name: 🐛 Troubleshooting Guide
-    url: https://test-architect.bmad-method.org/reference/troubleshooting
-    about: Common issues and solutions

package/lib/bmad-cache/tea/.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,70 +0,0 @@
----
-name: Feature Request
-about: Suggest an idea or new feature for TEA
-title: ''
-labels: 'enhancement'
-assignees: ''
----
-
-**Describe your idea**
-A clear and concise description of what you'd like to see added or changed in TEA.
-
-**Why is this needed?**
-Explain the problem this solves or the benefit it brings to:
-
-- TEA users
-- Test automation practices
-- Quality engineering workflows
-- Testing best practices
-
-**Which component would this affect?**
-Please check all that apply:
-
-- [ ] Workflows (test-design, automate, atdd, test-review, trace, nfr-assess, ci, framework)
-- [ ] Knowledge Base (new testing patterns or fragments)
-- [ ] Subagent Architecture (parallel execution)
-- [ ] Configuration (module variables or settings)
-- [ ] Documentation (guides, tutorials, or references)
-- [ ] Integrations (Playwright Utils, MCP, or other tools)
-- [ ] Quality Gates (risk assessment, traceability, scoring)
-- [ ] Other (please specify)
-
-**How should it work?**
-Describe your proposed solution:
-
-1. What would the user experience look like?
-2. What workflow would be affected?
-3. What knowledge base updates would be needed?
-4. Any implementation ideas?
-
-**Use Case Example**
-Provide a concrete example of how this feature would be used:
-
-```
-Example scenario:
-User wants to [specific goal]
-Currently: [what happens now]
-With this feature: [what would happen]
-```
-
-**Alternatives considered**
-Have you considered any alternative solutions or workarounds?
-
-**Impact & Priority**
-How important is this feature?
-
-- [ ] Critical - blocking adoption or major workflow
-- [ ] High - significantly improves user experience
-- [ ] Medium - nice to have, would help some users
-- [ ] Low - minor improvement or edge case
-
-**Contribution**
-If you'd like to contribute, please indicate you're working on this or link to your PR. Please review [CONTRIBUTING.md](../../CONTRIBUTING.md) — contributions are always welcome!
-
-**Additional context**
-Add any other context, screenshots, or links that help explain your idea:
-
-- Related workflows or knowledge fragments
-- Testing frameworks this would support
-- Industry standards or best practices this aligns with
-- Links to similar features in other tools

package/lib/bmad-cache/tea/.github/ISSUE_TEMPLATE/issue.md

@@ -1,61 +0,0 @@
----
-name: Bug Report
-about: Report a problem or something that's not working with TEA
-title: ''
-labels: 'bug'
-assignees: ''
----
-
-**Describe the bug**
-A clear and concise description of what the bug is.
-
-**Steps to reproduce**
-
-1. What TEA workflow were you running? (e.g., `test-design`, `automate`, `atdd`)
-2. What steps can recreate the issue?
-3. What was the exact command or trigger used?
-
-**Expected behavior**
-A clear and concise description of what you expected to happen.
-
-**Environment**
-
-- **TEA Version**: [e.g., 1.0.0]
-- **BMAD Method Version**: [e.g., 7.0.0]
-- **Node Version**: [output of `node --version`]
-- **Operating System**: [e.g., macOS 14.0, Ubuntu 22.04, Windows 11]
-- **Agentic IDE**: [e.g., Claude Code, Windsurf, Cursor]
-- **Model Used**: [e.g., Claude Sonnet 4.5, GPT-4]
-
-**Workflow Details (if applicable)**
-
-- **Workflow**: [e.g., test-design, automate, atdd, test-review, trace, nfr-assess, ci, framework]
-- **Test Framework**: [e.g., Playwright, Cypress]
-- **Playwright Utils Enabled**: [yes/no]
-- **MCP Enhancements Enabled**: [yes/no]
-
-**Screenshots or output**
-If applicable, add:
-
-- Screenshots of the issue
-- Console output or error messages
-- Generated test files or reports
-
-**Additional context**
-Add any other context about the problem:
-
-- Project type (greenfield/brownfield)
-- Codebase size
-- Any custom TEA configuration
-- Related workflows or knowledge fragments
-
-**Troubleshooting Checklist**
-Before submitting, please check:
-
-- [ ] I've read the [Troubleshooting Guide](https://test-architect.bmad-method.org/reference/troubleshooting)
-- [ ] I've verified TEA is installed: `ls -la _bmad/tea/`
-- [ ] I'm using the correct command namespace: `/bmad:tea:*` not `/bmad:bmm:tea:*`
-- [ ] I've checked for existing issues on GitHub
-
-**Contribution**
-If you'd like to contribute a fix, please indicate you're working on it or link to your PR. See [CONTRIBUTING.md](../../CONTRIBUTING.md) — contributions are always welcome!