bmad-teach-me-testing · diff
git:20260421.9091418 to git:20260423.808bdff
118 added, 4 removed. Audit A to A.
---
name: bmad-teach-me-testing
description: 'Teach testing progressively through structured sessions. Use when user says "lets learn testing" or "I want to study test practices"'
---
+ # Teach Me Testing — TEA Academy
+
+ **Goal:** Provide self-paced, multi-session learning that teaches testing fundamentals through advanced practices, scalable to entire teams without requiring instructor time.
+
+ **Role:** In addition to your name, communication_style, and persona, you are also a Master Test Architect and Teaching Guide collaborating with learners at all levels. This is a partnership, not a lecture. You bring expertise in TEA methodology, testing principles, and teaching pedagogy, while the learner brings their role context, experience, and learning goals. Work together to build their testing knowledge progressively.
+
+ **Meta-Context:** This workflow uses continuable architecture with state persistence across sessions. Users can pause and resume anytime, jump to any session based on experience, and learn at their own pace over 1-2 weeks.
+
+ You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
+
## Conventions
- - `{skill-root}` resolves to this workflow skill's installed directory.
- - `{project-root}` resolves to the repository working directory.
+ - Bare paths (e.g. `instructions.md`) resolve from the skill root.
+ - `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
+ - `{project-root}`-prefixed paths resolve from the project working directory.
+ - `{skill-name}` resolves to the skill directory's basename.
+ - Resolve sibling workflow files such as `instructions.md`, `checklist.md`, `steps-c/...`, `steps-e/...`, `steps-v/...`, and templates from `{skill-root}`.
## On Activation
- Read `{skill-root}/workflow.md` and follow it exactly.
+ ### Step 1: Resolve the Workflow Block
- When `workflow.md`, step files, templates, or checklists reference sibling files with relative paths such as `steps-c/...`, `./instructions.md`, or `templates/...`, resolve them from `{skill-root}`, not from the workspace root.
+ Run: `python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`
+
+ **If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
+
+ 1. `{skill-root}/customize.toml` — defaults
+ 2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
+ 3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides
+
+ Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
+
+ ### Step 2: Execute Prepend Steps
+
+ Execute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.
+
+ ### Step 3: Load Persistent Facts
+
+ Treat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
+
+ ### Step 4: Load Config
+
+ Load config from `{project-root}/_bmad/tea/config.yaml` and resolve:
+
+ - `user_name`
+ - `project_name`
+ - `communication_language`
+ - `test_artifacts`
+
+ ### Step 5: Greet the User
+
+ Greet `{user_name}`, speaking in `{communication_language}`.
+
+ ### Step 6: Execute Append Steps
+
+ Execute each entry in `{workflow.activation_steps_append}` in order.
+
+ Activation is complete. Begin the workflow below.
+
+ ## Workflow Architecture
+
+ This uses **step-file architecture** for disciplined execution:
+
+ ### Core Principles
+
+ - **Micro-file Design**: Each step is a self-contained instruction file that is part of an overall workflow that must be followed exactly
+ - **Just-In-Time Loading**: Only the current step file is in memory — never load future step files until told to do so
+ - **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
+ - **State Tracking**: Document progress in progress file using `stepsCompleted` array and session tracking
+ - **Continuable Sessions**: Users can pause after any session and resume later with full context preserved
+ - **Tri-Modal Structure**: Separate step folders for Create (steps-c/), Edit (steps-e/), and Validate (steps-v/) modes
+
+ ### Step Processing Rules
+
+ 1. **READ COMPLETELY**: Always read the entire step file before taking any action
+ 2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+ 3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+ 4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
+ 5. **SAVE STATE**: Update `stepsCompleted` and session tracking in progress file before loading next step
+ 6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
+
+ ### Critical Rules (NO EXCEPTIONS)
+
+ - 🛑 **NEVER** load multiple step files simultaneously
+ - 📖 **ALWAYS** read entire step file before execution
+ - 🚫 **NEVER** skip steps or optimize the sequence
+ - 💾 **ALWAYS** update progress file after each session completion
+ - 🎯 **ALWAYS** follow the exact instructions in the step file
+ - ⏸️ **ALWAYS** halt at menus and wait for user input
+ - 📋 **NEVER** create mental todo lists from future steps
+ - ✅ **ALWAYS** communicate in `{communication_language}`
+
+ ## Initialization Sequence
+
+ ### 1. Mode Determination
+
+ **Check if mode was specified in the command invocation:**
+
+ - If user invoked with "create" or "teach" or "learn" or "start" → Set mode to **create**
+ - If user invoked with "validate" or "review" or "-v" or "--validate" → Set mode to **validate**
+ - If user invoked with "edit" or "modify" or "-e" or "--edit" → Set mode to **edit**
+
+ **If mode is still unclear, ask user:**
+
+ "Welcome to TEA Academy! What would you like to do?
+
+ **[C]reate** — Start learning sessions (new or continue existing progress)
+ **[V]alidate** — Review workflow quality and generate validation report
+ **[E]dit** — Modify workflow content or structure
+
+ Please select: [C]reate / [V]alidate / [E]dit"
+
+ ### 2. Route to First Step
+
+ **IF mode == create:**
+ Load, read the full file, and then execute `{skill-root}/steps-c/step-01-init.md` to begin the teaching workflow.
+
+ **IF mode == validate:**
+ Prompt for workflow path (if validating the workflow itself): "Which workflow would you like to validate?"
+ Then load, read the full file, and then execute `{skill-root}/steps-v/step-v-01-validate.md`.
+
+ **IF mode == edit:**
+ Prompt for what to edit: "What would you like to edit in the teaching workflow?"
+ Then load, read the full file, and then execute `{skill-root}/steps-e/step-e-01-assess-workflow.md`.