tasks

MDT Task Breakdown Workflow (v11)

Generate tasks from architecture + tests + bdd. Tasks include constraints (scope boundaries, exclusions, anti-duplication), not just actions.

Decision Tree

Input: /mdt:tasks {CR-KEY} [--prep] [--part X.Y]

Prerequisites exist?
├─ No architecture.md → ERROR: Run /mdt:architecture first
├─ No tests.md → ERROR: Run /mdt:tests first
│
├─ bdd.md exists? → Load as supplementary input (for E2E-only files)
│
└─ Yes → What mode?
    ├─ --prep → Read prep/architecture.md + prep/tests.md [+ prep/bdd.md]
    │   └─ Output: prep/tasks.md
    │
    └─ Feature → Read architecture.md + [part-X.Y/]tests.md [+ bdd.md]
        ├─ Multi-part? Prompt for part selection
        └─ Output: [part-X.Y/]tasks.md

Skill Discovery (MANDATORY)

Before generating tasks, discover project-required skills:

1. Find all AGENTS.md files in the project (root + subdirectories, exclude .git/).
2. Parse skill requirements: look for "Required Skills" tables, "MUST use skill" directives, or "load skill:" instructions.
3. Map skills to directories: each skill applies to a package or directory scope (e.g., svelte5-best-practices → packages/frontend/).
4. Assign skills to tasks: when a task's Creates/Modifies files fall within a skill's directory scope, add that skill to the task's **Skills** field.

If no AGENTS.md files exist, skip this step — no **Skills** field is written.

Task Template (Essential)

### Task {N}: {Brief description}

**Skills**: {skill-1}, {skill-2}  ← omit if no skills required for this task

**Milestone**: M{X} — {milestone name} (BR-X.Y)  ← omit if no bdd.md

**Structure**: `{path from architecture}`

**Makes GREEN (unit)**: *(from tests.md)*
- `test_file`: `test name`

**Makes GREEN (BDD)**: *(only on milestone's final task)*
- `scenario_name` → `e2e_test_file` (BR-X.Y)

**Enables (BDD)**: *(tasks that contribute to a future milestone)*
- `scenario_name` (BR-X.Y) — needs Task {M} to complete

**Scope**: {what this task owns}
**Boundary**: {what it must not touch}

**Creates**:
- {new file/module}

**Modifies**:
- {existing file/module}

**Must Not Touch**:
- {module/file outside task ownership}

**Create/Move**:
- {specific item 1}
- {specific item 2}

**Exclude**: {what NOT to include}

**Anti-duplication**: Import `{X}` from `{path}` — do NOT copy

**Duplication Guard**:
- Check owner module for target behavior before coding
- If logic exists elsewhere, add explicit merge/refactor task immediately (no parallel path)
- Verify no second runtime owner was introduced

**Verify**:
```bash
{test_command} --filter="..."   # unit tests GREEN
{e2e_command} --grep="..."      # BDD GREEN (only if Makes GREEN (BDD) present)

Done when:

• Unit tests GREEN (were RED)
• BDD scenarios GREEN (if Makes GREEN (BDD) listed)
• No duplicated logic
• Smoke test passes (feature works with real execution)
• Fallback/absence paths match requirements (if applicable)