Skip to content

tibursocampos/agent-dev-toolkit / core/skills/refine-story

refine-story

Verified

Refine a Bug, User Story, or Technical Story into structured markdown with BDD acceptance and a quality scorecard. Use when refining backlog or invoking /refine-story.

references/guardrails.md

View on GitHub
## Guardrails (before marking output final)

**Universal:**

- [ ] No empty or placeholder sections
- [ ] No vague phrases: "works correctly", "as expected", "properly"
- [ ] BDD uses **Given / When / Then / And**
- [ ] AC budget: at least **happy + rule/edge + failure**, each with observable Then (`gherkin-budget.md`)
- [ ] Scorecard includes **Product depth**; Evidence omit is OK (`product-evidence-lite.md`)
- [ ] No unit-test scenarios in acceptance criteria
- [ ] No "verify environment variable X" as acceptance criteria
- [ ] Section icons/headings match the type template when saving chat form
- [ ] Titles/objectives outcome-shaped — not verb+file/class/script (`anti-task-shatter.md`)

**Technical Story / User Story:**

- [ ] Steps ordered by layer when applicable
- [ ] Step titles name **behavior**, not file/class/layer only (`story-sizing.md`)
- [ ] Story represents one verifiable outcome (not a file or layer checklist)
- [ ] Dependencies section omitted when none (not "N/A" filler)
- [ ] Each step has explicit `Depends on:` for topological breakdown

**User Story:**

- [ ] Business AC without implementation jargon
- [ ] Technical AC as checkboxes, not BDD

**Bug:**

- [ ] Reproduction steps are actionable
- [ ] Expected result describes positive behavior

If guardrails fail, ask for missing detail - do not publish incomplete docs.

**Clarification readiness (REQ-004–006):** open questions carry **B** \| **I** \| **MINOR** (`clarify-depth.md` / `readiness-severity.md`). Status follows `readiness-severity.md`; do not hand off as ready-for-PRD while any question is unanswered. Presence ≠ READY (**RN02**). Dual plane: readiness ≠ `step_confirmed` / PLAN Complete (REQ-006).

**Mode isolation (REQ-004):** only the active mode playbook loaded; envelope `mode` matches (`mode-isolation.md`).

**Envelope + Q&A (REQ-005):** interaction envelope refreshed; Q&A history path portable and consultable when persisted (`interaction-envelope.md`, `qa-history.md`).

**Handoffs:** portable paths only — no OS absolute / InstallRoot embeds (RNF-002).

**Selective retrieval:** do not dump entire `memory-bank/` or paste full PRD into refine chat/handoffs (`SELECTIVE-RETRIEVAL.md` / `SR-NO-FULL-DUMP`).

---
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall