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}/operations/cicd.md{context.paths.docs}/operations/infra.md{context.paths.docs}/operations/monitoring.md{context.paths.docs}/bugs/change-register.md (for release
notes)
Outputs
{context.paths.docs}/operations/deployment.md{context.paths.docs}/operations/release-notes-<date>.md (on
each release)
Context Update
Does not mutate .kiss/context.yml.
Handoffs
kiss-project-planning references the release model in milestones.kiss-status-report references the most recent release.kiss-monitoring is consulted for canary bake thresholds.
AI authoring scope
Does: pick a release model (canary / blue-green / rolling),
draft the promotion flow across environments, specify rollback
criteria + commands, propose feature-flag usage, seed release
notes from the change register.
Does not: deploy; run kubectl / terraform / any cloud CLI;
toggle feature flags.
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/….
DP_MODEL=canary DP_CANARY_BAKE_MIN=30 bash <SKILL_DIR>/kiss-deployment-strategy/scripts/bash/draft-deployment.sh --auto
Answer keys
| Key |
Default |
DP_MODEL (canary/blue-green/rolling/recreate) |
canary |
DP_CANARY_BAKE_MIN |
30 |
DP_ENVIRONMENTS |
dev,staging,prod |
1---2name: kiss-deployment-strategy3description: Drafts the deployment strategy + release runbook — canary / blue-green / rolling, promotion flow, rollback, feature flags, release-notes seed. Produces a runbook the on-call team uses. Does not deploy. Use when planning a deployment strategy, defining a release process, or choosing between canary, blue-green, or rolling deployment patterns.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}/operations/cicd.md`50- `{context.paths.docs}/operations/infra.md`51- `{context.paths.docs}/operations/monitoring.md`52- `{context.paths.docs}/bugs/change-register.md` (for release53 notes)5455## Outputs5657- `{context.paths.docs}/operations/deployment.md`58- `{context.paths.docs}/operations/release-notes-<date>.md` (on59 each release)6061## Context Update6263Does not mutate `.kiss/context.yml`.6465## Handoffs6667- `kiss-project-planning` references the release model in milestones.68- `kiss-status-report` references the most recent release.69- `kiss-monitoring` is consulted for canary bake thresholds.7071## AI authoring scope7273**Does:** pick a release model (canary / blue-green / rolling),74draft the promotion flow across environments, specify rollback75criteria + commands, propose feature-flag usage, seed release76notes from the change register.7778**Does not:** deploy; run kubectl / terraform / any cloud CLI;79toggle feature flags.8081## Usage8283> `<SKILL_DIR>` = the integration's skills root (e.g. `.claude/skills/`84> for Claude Code, `.agents/skills/` for Antigravity / Codex,85> `.cursor/skills/` for Cursor, `.windsurf/workflows/` for Windsurf).86> Scripts live at `<SKILL_DIR>/<skill-name>/scripts/…`.8788```bash89DP_MODEL=canary DP_CANARY_BAKE_MIN=30 bash <SKILL_DIR>/kiss-deployment-strategy/scripts/bash/draft-deployment.sh --auto90```9192### Answer keys9394| Key | Default |95|---|---|96| `DP_MODEL` (`canary`/`blue-green`/`rolling`/`recreate`) | `canary` |97| `DP_CANARY_BAKE_MIN` | `30` |98| `DP_ENVIRONMENTS` | `dev,staging,prod` |
dauquangthanh