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.docs}/architecture/intake.md{context.paths.docs}/testing/<feature>/strategy.md- Project root files (package.json, pyproject.toml, go.mod, …)
Outputs
{context.paths.docs}/testing/<feature>/framework.md{context.paths.docs}/testing/<feature>/framework.extract
Context Update
Does not mutate .kiss/context.yml.
Handoffs
kiss-unit-tests reads the unit framework choice.kiss-test-cases reads the e2e framework choice.kiss-cicd reads framework commands when drafting the pipeline.
AI authoring scope
Does: detect language(s) and framework signals, propose 2–3
candidates per level (unit / integration / e2e), draft the folder
layout, list required dev-dependencies.
Does not: install packages, edit package.json/equivalent,
commit the team to a framework without confirmation.
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/….
bash <SKILL_DIR>/kiss-test-framework/scripts/bash/draft-framework.sh --auto
Answer keys
| Key |
Meaning |
Default |
TF_UNIT_FRAMEWORK |
override detected unit framework |
auto |
TF_INTEGRATION_FRAMEWORK |
override integration framework |
same as unit |
TF_E2E_FRAMEWORK |
e2e framework |
playwright (web) / none |
References
references/framework-matrix.md — per-language recommended
defaults.
1---2name: kiss-test-framework3description: Recommends unit + integration + e2e frameworks that fit the project's language + architecture, drafts the folder layout, and lists the tooling versions. Use when choosing a test framework, setting up testing infrastructure, or defining the test toolchain for a new project or language stack.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.docs}/architecture/intake.md`50- `{context.paths.docs}/testing/<feature>/strategy.md`51- Project root files (package.json, pyproject.toml, go.mod, …)5253## Outputs5455- `{context.paths.docs}/testing/<feature>/framework.md`56- `{context.paths.docs}/testing/<feature>/framework.extract`5758## Context Update5960Does not mutate `.kiss/context.yml`.6162## Handoffs6364- `kiss-unit-tests` reads the unit framework choice.65- `kiss-test-cases` reads the e2e framework choice.66- `kiss-cicd` reads framework commands when drafting the pipeline.6768## AI authoring scope6970**Does:** detect language(s) and framework signals, propose 2–371candidates per level (unit / integration / e2e), draft the folder72layout, list required dev-dependencies.7374**Does not:** install packages, edit `package.json`/equivalent,75commit the team to a framework without confirmation.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```bash85bash <SKILL_DIR>/kiss-test-framework/scripts/bash/draft-framework.sh --auto86```8788### Answer keys8990| Key | Meaning | Default |91|---|---|---|92| `TF_UNIT_FRAMEWORK` | override detected unit framework | auto |93| `TF_INTEGRATION_FRAMEWORK` | override integration framework | same as unit |94| `TF_E2E_FRAMEWORK` | e2e framework | `playwright` (web) / `none` |9596## References9798- `references/framework-matrix.md` — per-language recommended99 defaults.
dauquangthanh