User Input
$ARGUMENTS
Audience and tone (interactive mode)
When KISS_AGENT_MODE=interactive (the default), assume the user
has limited technical background and limited domain knowledge
— they may know basics but lack deep expertise in this skill's
area. Run this skill as a guided questionnaire:
- One question at a time. No walls of questions.
- Yes / no first. Phrase so
yes, no, not sure, or skip
is a valid answer.
- Translate jargon, don't strip it. Use the technical term but
always pair it with a plain-English gloss the first time it
appears.
- Choices, not blank fields. When yes/no isn't enough, offer
2-4 lettered options (A/B/C/D) with one-line plain-language
descriptions of the trade-off. Always include "Not sure — pick
a sensible default".
- Always recommend. State the option you would pick and why in
one sentence so the user can reply "yes" / "ok" to accept. Pull
defaults from upstream artefacts (spec, architecture, ADRs,
standards) before asking blank.
- Show, don't ask. When upstream artefacts already imply an
answer, propose it as a pre-filled finding and ask for a
yes / no confirmation rather than asking the user to fill in a
blank.
not sure / skip triggers a sensible default, marked
"(default applied — confirm later)" in the artefact, and a debt
entry in this skill's debt file.
When KISS_AGENT_MODE=auto (or --auto), skip the questionnaire
entirely: apply sensible defaults from upstream artefacts and log
decisions to the parent agent's decision log.
Inputs
.kiss/context.yml{context.paths.specs}/<feature>/spec.md{context.paths.docs}/architecture/intake.md{context.paths.docs}/project/risk-register.md
Outputs
{context.paths.docs}/testing/<feature>/strategy.md{context.paths.docs}/testing/<feature>/strategy.extract
Context Update
Does not mutate .kiss/context.yml.
Handoffs
kiss-test-framework consumes the strategy's tooling section.kiss-test-cases consumes levels + risk tiers.kiss-quality-gates consumes entry/exit criteria.
AI authoring scope
Does: draft levels (unit / integration / e2e / contract /
performance / security), risk-tiered priorities, test environments
needed, entry/exit criteria.
Does not: choose the framework yet (that's kiss-test-framework),
commit the team to coverage percentages they haven't agreed.
Usage
<SKILL_DIR> = the integration's skills root (e.g. .claude/skills/
for Claude Code, .agents/skills/ for Antigravity / Codex,
.cursor/skills/ for Cursor, .windsurf/workflows/ for Windsurf).
Scripts live at <SKILL_DIR>/<skill-name>/scripts/….
TS_RISK_TIERS=high,medium,low TS_LEVELS=unit,integration,e2e \
bash <SKILL_DIR>/kiss-test-strategy/scripts/bash/draft-strategy.sh --auto
Answer keys
| Key |
Default |
TS_RISK_TIERS |
high,medium,low |
TS_LEVELS |
unit,integration,e2e |
TS_ENVIRONMENTS |
dev,staging,prod |
TS_COVERAGE_TARGET |
80 |
1---2name: kiss-test-strategy3description: Drafts the feature-scoped test strategy — scope, risk-based test priorities, levels of testing, entry/exit criteria, environments, and tooling expectations. Produces a reviewable document the test-architect and PM anchor on. Use when planning a testing approach, defining test coverage strategy, or setting entry/exit criteria for a feature.4---567## User Input89```text10$ARGUMENTS11```1213## Audience and tone (interactive mode)1415When `KISS_AGENT_MODE=interactive` (the default), assume the user16has **limited technical background and limited domain knowledge**17— they may know basics but lack deep expertise in this skill's18area. Run this skill as a guided questionnaire:1920- **One question at a time.** No walls of questions.21- **Yes / no first.** Phrase so `yes`, `no`, `not sure`, or `skip`22 is a valid answer.23- **Translate jargon, don't strip it.** Use the technical term but24 always pair it with a plain-English gloss the first time it25 appears.26- **Choices, not blank fields.** When yes/no isn't enough, offer27 2-4 lettered options (A/B/C/D) with one-line plain-language28 descriptions of the trade-off. Always include "Not sure — pick29 a sensible default".30- **Always recommend.** State the option you would pick and why in31 one sentence so the user can reply "yes" / "ok" to accept. Pull32 defaults from upstream artefacts (spec, architecture, ADRs,33 standards) before asking blank.34- **Show, don't ask.** When upstream artefacts already imply an35 answer, propose it as a pre-filled finding and ask for a36 yes / no confirmation rather than asking the user to fill in a37 blank.38- **`not sure` / `skip` triggers a sensible default**, marked39 "(default applied — confirm later)" in the artefact, and a debt40 entry in this skill's debt file.4142When `KISS_AGENT_MODE=auto` (or `--auto`), skip the questionnaire43entirely: apply sensible defaults from upstream artefacts and log44decisions to the parent agent's decision log.4546## Inputs4748- `.kiss/context.yml`49- `{context.paths.specs}/<feature>/spec.md`50- `{context.paths.docs}/architecture/intake.md`51- `{context.paths.docs}/project/risk-register.md`5253## Outputs5455- `{context.paths.docs}/testing/<feature>/strategy.md`56- `{context.paths.docs}/testing/<feature>/strategy.extract`5758## Context Update5960Does not mutate `.kiss/context.yml`.6162## Handoffs6364- `kiss-test-framework` consumes the strategy's tooling section.65- `kiss-test-cases` consumes levels + risk tiers.66- `kiss-quality-gates` consumes entry/exit criteria.6768## AI authoring scope6970**Does:** draft levels (unit / integration / e2e / contract /71performance / security), risk-tiered priorities, test environments72needed, entry/exit criteria.7374**Does not:** choose the framework yet (that's `kiss-test-framework`),75commit the team to coverage percentages they haven't agreed.7677## Usage7879> `<SKILL_DIR>` = the integration's skills root (e.g. `.claude/skills/`80> for Claude Code, `.agents/skills/` for Antigravity / Codex,81> `.cursor/skills/` for Cursor, `.windsurf/workflows/` for Windsurf).82> Scripts live at `<SKILL_DIR>/<skill-name>/scripts/…`.8384```bash85TS_RISK_TIERS=high,medium,low TS_LEVELS=unit,integration,e2e \86 bash <SKILL_DIR>/kiss-test-strategy/scripts/bash/draft-strategy.sh --auto87```8889### Answer keys9091| Key | Default |92|---|---|93| `TS_RISK_TIERS` | `high,medium,low` |94| `TS_LEVELS` | `unit,integration,e2e` |95| `TS_ENVIRONMENTS` | `dev,staging,prod` |96| `TS_COVERAGE_TARGET` | `80` |
dauquangthanh