User Input
$ARGUMENTS
Audience and tone (interactive mode)
When KISS_AGENT_MODE=interactive (the default), assume the user
has no technical or Scrum background. 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.
- No jargon. Translate to everyday words: "How long is one
sprint?" (A) 1 week, B) 2 weeks, C) 3 weeks, D) 4 weeks);
"How many things does the team usually finish in that time?" not
"What's your velocity?"; "What should we deliver this sprint?"
not "What's the sprint goal?"; avoid "WIP / capacity points /
refinement".
- Choices, not blank fields. When yes/no isn't enough, offer
2-4 lettered options (A/B/C/D) with one-line everyday
descriptions. 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. For
velocity, use the previous sprint's number when available.
not sure / skip triggers a sensible default sprint plan
field (recommended velocity from history; sprint goal proposed
from the top backlog item), marked "(default applied — confirm
later)" in sprint-NN-plan.md, and a SMDEBT- entry in
agile-debts.md.
When KISS_AGENT_MODE=auto (or --auto), skip the questionnaire
entirely: pull top backlog items, propose a goal, and log decisions
to the scrum-master agent's decision log.
Inputs
.kiss/context.yml → paths.docs{context.paths.docs}/product/backlog.md — prioritised items{context.paths.docs}/product/acceptance.md — for DoD context- Previous sprint's retro (
docs/agile/retro-sprint-*.md) when
present
Outputs
{context.paths.docs}/agile/sprint-NN-plan.md{context.paths.docs}/agile/sprint-NN-plan.extract
Context Update
Does not mutate .kiss/context.yml.
Handoffs
kiss-standup references the current sprint plan when logging
daily notes.kiss-retrospective compares planned vs. delivered at end-of-sprint.
AI authoring scope
Does: draft sprint goal, propose candidate backlog items that
fit a capacity estimate, flag stories without acceptance criteria,
carry over unfinished items from previous sprint.
Does not: commit the team to a sprint, hold a planning meeting,
assign tasks to individuals, decide sprint goal without user input.
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/….
SP_SPRINT_NUMBER=7 SP_GOAL="Ship SSO PoC" SP_VELOCITY=24 SP_CAPACITY=26 \
bash <SKILL_DIR>/kiss-sprint-planning/scripts/bash/draft-sprint.sh --auto
Answer keys
| Key |
Meaning |
Default |
SP_SPRINT_NUMBER |
Sprint sequence number |
auto-increment from existing |
SP_GOAL |
Sprint goal statement |
(required) |
SP_VELOCITY |
Team's recent velocity (points / items) |
(required) |
SP_CAPACITY |
Capacity for this sprint (factor in leave / holidays) |
= velocity |
SP_START_DATE |
Sprint start (YYYY-MM-DD) |
today |
SP_END_DATE |
Sprint end |
start + 14 days |
1---2name: kiss-sprint-planning3description: Drafts a sprint plan — sprint goal, candidate backlog items, capacity arithmetic, and risk flags — from the backlog + a user-provided velocity. Prepares the artefact; the team owns the commitment. Does not facilitate a planning meeting. Use when planning a sprint, selecting backlog items for a sprint, or calculating team capacity.4---567## User Input89```text10$ARGUMENTS11```1213## Audience and tone (interactive mode)1415When `KISS_AGENT_MODE=interactive` (the default), assume the user16has **no technical or Scrum background**. Run this skill as a17guided questionnaire:1819- **One question at a time.** No walls of questions.20- **Yes / no first.** Phrase so `yes`, `no`, `not sure`, or `skip`21 is a valid answer.22- **No jargon.** Translate to everyday words: "How long is one23 sprint?" *(A) 1 week, B) 2 weeks, C) 3 weeks, D) 4 weeks)*;24 "How many things does the team usually finish in that time?" not25 "What's your velocity?"; "What should we deliver this sprint?"26 not "What's the sprint goal?"; avoid "WIP / capacity points /27 refinement".28- **Choices, not blank fields.** When yes/no isn't enough, offer29 2-4 lettered options (A/B/C/D) with one-line everyday30 descriptions. Always include "Not sure — pick a sensible default".31- **Always recommend.** State the option you would pick and why in32 one sentence so the user can reply "yes" / "ok" to accept. For33 velocity, use the previous sprint's number when available.34- **`not sure` / `skip` triggers a sensible default** sprint plan35 field (recommended velocity from history; sprint goal proposed36 from the top backlog item), marked "(default applied — confirm37 later)" in `sprint-NN-plan.md`, and a `SMDEBT-` entry in38 `agile-debts.md`.3940When `KISS_AGENT_MODE=auto` (or `--auto`), skip the questionnaire41entirely: pull top backlog items, propose a goal, and log decisions42to the scrum-master agent's decision log.4344## Inputs4546- `.kiss/context.yml` → `paths.docs`47- `{context.paths.docs}/product/backlog.md` — prioritised items48- `{context.paths.docs}/product/acceptance.md` — for DoD context49- Previous sprint's retro (`docs/agile/retro-sprint-*.md`) when50 present5152## Outputs5354- `{context.paths.docs}/agile/sprint-NN-plan.md`55- `{context.paths.docs}/agile/sprint-NN-plan.extract`5657## Context Update5859Does not mutate `.kiss/context.yml`.6061## Handoffs6263- `kiss-standup` references the current sprint plan when logging64 daily notes.65- `kiss-retrospective` compares planned vs. delivered at end-of-sprint.6667## AI authoring scope6869**Does:** draft sprint goal, propose candidate backlog items that70fit a capacity estimate, flag stories without acceptance criteria,71carry over unfinished items from previous sprint.7273**Does not:** commit the team to a sprint, hold a planning meeting,74assign tasks to individuals, decide sprint goal without user input.7576## Usage7778> `<SKILL_DIR>` = the integration's skills root (e.g. `.claude/skills/`79> for Claude Code, `.agents/skills/` for Antigravity / Codex,80> `.cursor/skills/` for Cursor, `.windsurf/workflows/` for Windsurf).81> Scripts live at `<SKILL_DIR>/<skill-name>/scripts/…`.8283```bash84SP_SPRINT_NUMBER=7 SP_GOAL="Ship SSO PoC" SP_VELOCITY=24 SP_CAPACITY=26 \85 bash <SKILL_DIR>/kiss-sprint-planning/scripts/bash/draft-sprint.sh --auto86```8788### Answer keys8990| Key | Meaning | Default |91|---|---|---|92| `SP_SPRINT_NUMBER` | Sprint sequence number | auto-increment from existing |93| `SP_GOAL` | Sprint goal statement | *(required)* |94| `SP_VELOCITY` | Team's recent velocity (points / items) | *(required)* |95| `SP_CAPACITY` | Capacity for this sprint (factor in leave / holidays) | = velocity |96| `SP_START_DATE` | Sprint start (`YYYY-MM-DD`) | today |97| `SP_END_DATE` | Sprint end | start + 14 days |
dauquangthanh