Skills

aid-design-testing-strategy

Frontmatter

name — aid-design-testing-strategy
description — Develop the testing policy as a DESIGN SEED in .aid/design/testing-strategy.md — test levels, coverage expectations, which gates block a merge, and who may waive one. Use this skill when how the project should be tested is still being decided, rather than which tests to write. Grounded in the Knowledge Base (.aid/knowledge/) and the project source. It WRITES NO KB document and NO test code — realize the seed into the project’s C6 document(s) with /aid-create-testing-strategy once it is ready. To design a specific set of tests rather than the policy, use /aid-design-test; to RUN existing suites, use /aid-test. Produced by the aid-architect agent and independently verified by aid-reviewer (full verify). Allocates a work-NNN folder.
allowed-tools — Read, Glob, Grep, Bash, Write, Edit, Agent
argument-hint — <subject> — the testing policy to design (levels, coverage, merge-blocking gates, waivers)

Definition: canonical/skills/aid-design-testing-strategy/SKILL.md

Flow

flowchart TB
  classDef aidNode color:#fff
  classDef aidEntry fill:#166534,stroke:#14532d,color:#fff
  classDef aidExit fill:#991b1b,stroke:#7f1d1d,color:#fff
  classDef aidDecision fill:#92400e,stroke:#78350f,color:#fff
  classDef aidLoopBack fill:#1e3a8a,stroke:#1e3a8a,color:#fff
  classDef aidStep fill:#1a2035,stroke:#d4a853,color:#f1f5f9
  n1(["INTAKE"])
  n2["DESIGN"]
  n3["VERIFY"]
  n4["PRESENT<br/>hard stop -- the user decides"]
  n5(["DONE"])
  n1 --> n2
  n2 --> n3
  n3 -.-> n2
  n3 --> n4
  n4 --> n5
  class n1 aidEntry
  class n2 aidStep
  class n3 aidLoopBack
  class n4 aidStep
  class n5 aidExit
  class n1 aidNode
  class n2 aidNode
  class n3 aidNode
  class n4 aidNode
  class n5 aidNode

Source fragments

Every node in the chart above, in chart order, with the exact canonical/ text it was derived from.

1 · INTAKE · entry

## State: INTAKE

1. **Require a subject.** Empty argument -> ask one bootstrapping question ("What testing
   policy do you want to design -- its levels, coverage expectations, and merge-blocking
   gates?") and wait.
2. **Allocate** through the Work Initiation Gate exactly as the contract's Allocation rule
   requires (`canonical/skills/aid-design/SKILL.md` INTAKE step 4 is the shape), with
   `initiator: aid-design-testing-strategy`. `phase` is not driven.
3. **Acquire `.aid/design/`** per the contract, then read `.aid/design/testing-strategy.md`
   if a prior seed exists -- re-invocation iterates it rather than starting over.
4. **Classify complexity** for the `aid-architect` dispatch (verifier tier >= producer).

Source: canonical/skills/aid-design-testing-strategy/SKILL.md#L38-L48 · full step: canonical/skills/aid-design-testing-strategy/SKILL.md#L38-L50

2 · DESIGN · step

## State: DESIGN

Dispatch **`aid-architect`** (clean context, tiered) to write or iterate
`.aid/design/testing-strategy.md` in the seed shape the contract fixes (`design-seed.md`;
feature-002 §4), grounded in `.aid/knowledge/` and the project source plus any seed read
in INTAKE. What this artifact's seed must settle: **the test levels, coverage expectations,
which gates block a merge, and who may waive one**.

Source: canonical/skills/aid-design-testing-strategy/SKILL.md#L54-L60 · full step: canonical/skills/aid-design-testing-strategy/SKILL.md#L54-L76

3 · VERIFY · loop-back

## State: VERIFY

**Full verify**, as `design-lifecycle.md` defines it. Not clean -> loop to DESIGN; the
3-cycle circuit breaker there escalates to IMPEDIMENT + `lifecycle: Blocked`.

Source: canonical/skills/aid-design-testing-strategy/SKILL.md#L80-L83 · full step: canonical/skills/aid-design-testing-strategy/SKILL.md#L80-L85

4 · PRESENT — hard stop — the user decides · step

## State: PRESENT (hard stop -- the user decides)

Set `lifecycle: Paused-Awaiting-Input`. Present the seed clearly. Assert no resolution --
the user iterates (re-invoke this skill) or realizes it now
(`/aid-create-testing-strategy`).

Source: canonical/skills/aid-design-testing-strategy/SKILL.md#L89-L93 · full step: canonical/skills/aid-design-testing-strategy/SKILL.md#L89-L95

5 · DONE · exit · UNSPECIFIED

## State: DONE

Set `lifecycle: Completed`, `updated` now, append a `## Lifecycle History` row. The seed
persists at `.aid/design/testing-strategy.md`; consumption happens at
`/aid-create-testing-strategy`.

Source: canonical/skills/aid-design-testing-strategy/SKILL.md#L99-L103 · full step: canonical/skills/aid-design-testing-strategy/SKILL.md#L99-L103

Report an issue with this page →