User Input
$ARGUMENTS
Audience and tone (interactive mode)
When KISS_AGENT_MODE=interactive (the default), assume the user
has no technical or business-domain 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 domain terms into everyday words with
concrete examples (avoid MoSCoW, WSJF, RICE, INVEST, story
points, T-shirt, velocity, MVP). Use plain alternatives:
"must-have / nice-to-have / maybe-later" for priority,
"Small / Medium / Large / Extra-Large" for size.
- 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.
not sure / skip triggers a sensible default, marked
"(default applied — confirm later)" in the backlog row, and a
PODEBT- entry in product-debts.md.
When KISS_AGENT_MODE=auto (or --auto), skip the questionnaire
entirely: apply sensible defaults and log decisions to the
product-owner agent's decision log.
Inputs
.kiss/context.yml → paths.docs, paths.specs, current.feature{context.paths.specs}/**/spec.md — user stories source{context.paths.docs}/product/acceptance.md — ties items to criteria
Outputs
{context.paths.docs}/product/backlog.md — the ordered backlog.{context.paths.docs}/product/backlog.extract — summary counts.
Context Update
Does not mutate .kiss/context.yml.
Handoffs
kiss-roadmap reads the backlog to propose release windows.kiss-taskify converts prioritised items into tasks.kiss-tasks-to-issues emits GitHub issues once the PO approves.kiss-sprint-planning pulls top-N items into a sprint plan.
AI authoring scope
This skill does: append backlog items, re-order by priority the
user provides, estimate T-shirt sizes the user confirms, link each
item to its spec + acceptance criteria.
This skill does not: decide which items to promote / demote,
commit a team to deliver anything, negotiate with stakeholders.
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/….
# Add a new item.
BL_TITLE="Forgot-password flow" BL_PRIORITY=2 BL_SIZE=M BL_STORY_REF="specs/user-auth/spec.md#us-04" \
bash <SKILL_DIR>/kiss-backlog/scripts/bash/add-item.sh --auto
# Reorder (interactive).
bash <SKILL_DIR>/kiss-backlog/scripts/bash/add-item.sh
Answer keys
| Key |
Meaning |
Default |
BL_TITLE |
Item title (user story summary) |
(required) |
BL_PRIORITY |
1 = highest; integer |
99 |
BL_SIZE |
XS / S / M / L / XL |
M |
BL_STATUS |
New / Ready / In progress / Done / Cut |
New |
BL_STORY_REF |
Path or anchor into the spec |
empty |
Interactive flow
For each item: title → priority (1 = highest) → size (XS–XL) → spec
reference → status. Loop with "add another? (y/n)".
Debt register
File {context.paths.docs}/product/product-debts.md, prefix
PODEBT-. Log when an item has no priority, no acceptance-criteria
link, or an ambiguous size.
References
references/prioritization-frames.md — MoSCoW, WSJF, RICE quick
reference.references/estimation-t-shirt.md — T-shirt sizing anchors.
1---2name: kiss-backlog3description: Maintains the product backlog — an ordered markdown list of user stories / items keyed by priority, with lightweight estimates, acceptance-criteria pointers, and status. Drafts and re-orders the list from priorities the user states; does not decide priority or commit a team to deliver. Use when managing a product backlog, adding user stories, reprioritising features, or preparing for sprint planning.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 business-domain background**. Run this skill17as a guided 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 domain terms into everyday words with23 concrete examples (avoid MoSCoW, WSJF, RICE, INVEST, story24 points, T-shirt, velocity, MVP). Use plain alternatives:25 "must-have / nice-to-have / maybe-later" for priority,26 "Small / Medium / Large / Extra-Large" for size.27- **Choices, not blank fields.** When yes/no isn't enough, offer28 2-4 lettered options (A/B/C/D) with one-line everyday29 descriptions. Always include "Not sure — pick 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.32- **`not sure` / `skip` triggers a sensible default**, marked33 "(default applied — confirm later)" in the backlog row, and a34 `PODEBT-` entry in `product-debts.md`.3536When `KISS_AGENT_MODE=auto` (or `--auto`), skip the questionnaire37entirely: apply sensible defaults and log decisions to the38product-owner agent's decision log.3940## Inputs4142- `.kiss/context.yml` → `paths.docs`, `paths.specs`, `current.feature`43- `{context.paths.specs}/**/spec.md` — user stories source44- `{context.paths.docs}/product/acceptance.md` — ties items to criteria4546## Outputs4748- `{context.paths.docs}/product/backlog.md` — the ordered backlog.49- `{context.paths.docs}/product/backlog.extract` — summary counts.5051## Context Update5253Does not mutate `.kiss/context.yml`.5455## Handoffs5657- `kiss-roadmap` reads the backlog to propose release windows.58- `kiss-taskify` converts prioritised items into tasks.59- `kiss-tasks-to-issues` emits GitHub issues once the PO approves.60- `kiss-sprint-planning` pulls top-N items into a sprint plan.6162## AI authoring scope6364This skill **does**: append backlog items, re-order by priority the65user provides, estimate T-shirt sizes the user confirms, link each66item to its spec + acceptance criteria.6768This skill **does not**: decide which items to promote / demote,69commit a team to deliver anything, negotiate with stakeholders.7071## Usage7273> `<SKILL_DIR>` = the integration's skills root (e.g. `.claude/skills/`74> for Claude Code, `.agents/skills/` for Antigravity / Codex,75> `.cursor/skills/` for Cursor, `.windsurf/workflows/` for Windsurf).76> Scripts live at `<SKILL_DIR>/<skill-name>/scripts/…`.7778```bash79# Add a new item.80BL_TITLE="Forgot-password flow" BL_PRIORITY=2 BL_SIZE=M BL_STORY_REF="specs/user-auth/spec.md#us-04" \81 bash <SKILL_DIR>/kiss-backlog/scripts/bash/add-item.sh --auto8283# Reorder (interactive).84bash <SKILL_DIR>/kiss-backlog/scripts/bash/add-item.sh85```8687### Answer keys8889| Key | Meaning | Default |90|---|---|---|91| `BL_TITLE` | Item title (user story summary) | *(required)* |92| `BL_PRIORITY` | 1 = highest; integer | `99` |93| `BL_SIZE` | XS / S / M / L / XL | `M` |94| `BL_STATUS` | New / Ready / In progress / Done / Cut | `New` |95| `BL_STORY_REF` | Path or anchor into the spec | empty |9697## Interactive flow9899For each item: title → priority (1 = highest) → size (XS–XL) → spec100reference → status. Loop with "add another? (y/n)".101102## Debt register103104File `{context.paths.docs}/product/product-debts.md`, prefix105`PODEBT-`. Log when an item has no priority, no acceptance-criteria106link, or an ambiguous size.107108## References109110- `references/prioritization-frames.md` — MoSCoW, WSJF, RICE quick111 reference.112- `references/estimation-t-shirt.md` — T-shirt sizing anchors.
dauquangthanh