Derives, groups, and refines user stories from exploration work, prototype behavior, and business context, with prioritization for the first implementation slice. Supports standard "As a / I want / So that" format and Gherkin "Given / When / Then" Acceptance Criteria format. Trigger with "generate user stories", "write acceptance criteria", "create Gherkin scenarios", "derive stories from requirements", or "create a backlog".
From exploration-cycle-pluginnpx claudepluginhub richfrem/agent-plugins-skills --plugin exploration-cycle-pluginThis skill is limited to using the following tools:
acceptance-criteria.mdevals/evals.jsonevals/results.tsvreferences/acceptance-criteria.mdreferences/architecture.mdscripts/execute.pyGuides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Configures Istio traffic management with VirtualServices, DestinationRules for routing, canary/blue-green deployments, circuit breakers, load balancing, and fault injection in service meshes.
Derive structured user stories and acceptance criteria from exploration session captures.
python3 ./scripts/execute.py \
--input <file> [<file2>...] \
--format <standard|gherkin> \
--output <output_file.md>
Formats:
standard (default): As a [user type], I want [goal], so that [benefit] — with priority table and gaps.gherkin: Standard + Given / When / Then Acceptance Criteria blocks per story.Flags:
--input PATH [PATH ...] : Session brief, BRD draft, prototype notes, or prior captures--output PATH : Destination file (default: exploration/captures/user-stories-draft.md)--format FORMAT : Output format (default: standard)When invoked interactively, follow this 3-stage pattern. Do not dump a full story list at once.
Ask all three questions in a single message before generating anything:
exploration/ — list what you find: session brief, BRD draft, prototype notes.) If no files exist, stop and ask for input before proceeding.As a / I want / So that) or Gherkin (Given / When / Then)? Default to standard unless Gherkin is requested.After the user responds: read each input file they identify.
Build the backlog in layers — do not jump straight to full Gherkin blocks.
Outline first: Based on the input files and primary actor, present a numbered list of lightweight story titles (one line each, no ACs yet). Ask: "Which of these should we keep, cut, or merge for the first slice?"
Curate: Apply changes. Mark any story derived from unclear or inferred source material as [UNCONFIRMED].
Draft approved stories: For each kept story, write the full format:
As a [actor], I want [goal], so that [benefit].Given / When / Then AC blocks after the story statement.Gherkin format rules:
Given = precondition or system state before the action (what is already true)When = the single action or event the actor performsThen = the observable, testable outcome (what changes or appears)When per scenario. Use And for additional Given or Then clauses.Present each story and ask: "Accurate? Anything to add or change?" Apply edits before the next story.
After all approved stories are drafted:
Given / When / Then blocks for the confirmed edge cases. Mark inferred edge cases [UNCONFIRMED] until the user confirms they are real scenarios.## Story Gaps section at the end.[UNCONFIRMED] — only promote to [CONFIRMED] after human sign-off.