user-story

Decompose wiki feature scopes into user stories with Gherkin acceptance criteria.

5|1|Updated May 3, 2026
One-click install
npx skills add https://github.com/cooperacode/forge --skill user-story-cooperacode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: user-story
Source: https://github.com/cooperacode/forge/tree/main/.forge/skills/user-story
Command: npx skills add https://github.com/cooperacode/forge --skill user-story-cooperacode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decomposing strategic items into actionable tactical user stories directly from the active wiki reduces planning latency and ensures traceability by tying each story to a source document and a defined feature.

Core Features & Use Cases

  • Feature-driven decomposition: detect whether the active item is standalone, part of a feature, or part of an epic, and produce a set of candidate user stories for the Tactical level.
  • Gherkin-based acceptance criteria and Definition of Done: generate Given/When/Then scenarios and a clear DoD for each story to support testable requirements.
  • Traceability and sources: attach each story to source wiki pages, preserving links back to original documents.
  • Output structure: save one file per story under artifacts/user-stories with consistent naming and organization.

Quick Start

Provide the active wiki context and language, then run the skill to generate one file per story.

Frequently Asked Questions about user-story

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decompose a feature into user stories with Gherkin acceptance criteria?

User story decomposition from wiki context generates executable tactical work items with Gherkin Given/When/Then scenarios and Definition of Done. Each story maps to a single behavior with a defined persona, action, and benefit, outputting one markdown file per story.

What is the best way to generate Gherkin acceptance criteria from wiki pages?

Generating Gherkin acceptance criteria from wiki pages involves ingesting source documents to detect feature scope, producing candidate stories with traceability links back to the original pages. This ensures requirements remain testable and tied to source context.

Can I create tactical user stories from an epic without losing traceability to source documents?

Yes, you can create tactical user stories from an epic while maintaining traceability. The skill supports epic-derived contexts, attaching each generated story to its source wiki pages to preserve links back to original documents.

How do I structure user stories with a Definition of Done and open questions?

To structure user stories with a Definition of Done and open questions, the skill outputs one markdown file per story under artifacts/user-stories. Each file contains Gherkin scenarios, a clear DoD, and highlights open questions for identified requirement gaps.

Does wiki ingestion support standalone feature decomposition into single-behavior user stories?

Yes, wiki ingestion supports standalone feature decomposition into single-behavior user stories. The skill detects whether the active item is standalone, feature-derived, or epic-derived, ensuring each story defines a single persona, action, and benefit.