What problem does it solve? Teams often write vague user stories with untestable acceptance criteria, leading to rework, missed requirements, and unclear handoffs between business analysts, architects, and QA. This Skill structures functional story refinement so every story reaches a verifiable Ready state before technical work begins. ## Core Features & Use Cases - Discovery Probes: Systematically surfaces hidden requirements by questioning persona, scope, triggers, data, and dependencies before any acceptance criteria are written. - Acceptance Criteria Quality Framework: Enforces INVEST principles and testable Gherkin (Given/When/Then) criteria, rejecting vague statements and requiring Privacy ACs for PII-touching stories. - Local Backlog Persistence: Records refined stories to the repo-resident backlog via sf setup-agents task create, keeping git as the source of truth instead of an external tracker. - Use Case: A business analyst receives a rough feature request, runs the discovery probes to clarify scope and edge cases, writes Gherkin acceptance criteria, and persists a Ready story that the technical architect can pick up for impact analysis. ## Quick Start Ask the assistant to refine a story functionally by running discovery probes and writing testable Gherkin acceptance criteria, then save it to the local backlog.
