skills.rest
cyberAlchemyAI
cyberAlchemyAIOFFICIAL
Explore all skills by this author →
GitHub

sync-user-stories

Generate Classic and BDD user stories from DomainSpec aspect docs with a Story Coverage Matrix.

20|3|Updated May 14, 2026
Search Tags:#traceability#bdd#user-stories#derive#coverage-matrix#domain-spec#concept-registry
One-click install
npx skills add https://github.com/cyberAlchemyAI/Arcanum --skill sync-user-stories
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync-user-stories
Source: https://github.com/cyberAlchemyAI/Arcanum/tree/main/arcana/sync-user-stories
Command: npx skills add https://github.com/cyberAlchemyAI/Arcanum --skill sync-user-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate story-driven STORIES from DomainSpec aspect docs with mandatory slice coverage and a concept-coverage matrix. This Skill enables teams to derive both Classic and BDD-style user stories directly from DomainSpec aspects, ensuring every concept is covered by at least one story and that coverage is auditable. It produces a structured plan that ties stories to domain concepts and aspect anchors, and surfaces any coverage gaps.

Core Features & Use Cases

  • Derive Classic ("As a … I want … so that …") and BDD (Given/When/Then) stories for each capability.
  • Enforce the mandatory slice taxonomy (public, admin, integration, error) with explicit N/A reasons when not applicable.
  • Link each story's acceptance checks to concept IDs and aspect anchors for traceability.
  • Build a Story Coverage Matrix mapping concepts to stories and flag unmapped concepts as gaps.
  • Emit STORIES.md plus the coverage matrix aligned to the Concept Registry.

Quick Start

Apply the workflow to a feature having SPEC.md and domain/aspect docs to generate STORIES.md and the coverage matrix.

Frequently Asked Questions about sync-user-stories

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

FAQPage Schema
How do I derive BDD user stories from domain specification documents?▼

A coverage matrix maps domain concepts to generated user stories, ensuring every concept is covered by at least one story and flagging any unmapped concepts as coverage gaps aligned to the Concept Registry.

What is a story coverage matrix and how does it ensure traceability?▼

A coverage matrix maps domain concepts to generated user stories, ensuring every concept is covered by at least one story and flagging any unmapped concepts as coverage gaps aligned to the Concept Registry.

Can I generate both classic and BDD user stories from the same SPEC.md file?▼

Yes, you can generate both classic 'As a... I want... so that...' and BDD 'Given/When/Then' user stories from the same SPEC.md file and domain aspect docs in a single pass.

Do I need existing aspect docs and a Concept Registry to generate auditable user stories?▼

You need existing SPEC.md and domain aspect docs to generate auditable user stories, as the Skill links acceptance checks to concept IDs and does not create concepts not already present in the specification.

How to handle user story slice taxonomy when generating stories from domain specs?▼

When generating stories from domain specs, the Skill enforces a mandatory slice taxonomy across public, admin, integration, and error categories, requiring explicit N/A reasons when a slice is not applicable to a capability.

Related Skills

Explore More Product & Management Skills→
cyberAlchemyAIcyberAlchemyAI
20

test-derivation

Derive a TEST-SPEC.md from DomainSpec states.md without an LLM.

Official
Advanced
CarlosQ96CarlosQ96

story-done

Verify acceptance criteria, design compliance, and test coverage for game development sprint stories.

Community
Advanced
miko06miko06

health

Compute code quality scores from type checkers, linters, tests, and dead code detectors.

Community
Intermediate
dinoudondinoudon

sdlc-requirements-engineering

Clarify software requirements using structured practices like user-story mapping and BDD/Gherkin.

Community
Advanced