One-click install
npx skills add https://github.com/imclab/xrA1-swarm --skill create-stories-imclab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-stories
Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/create-stories
Command: npx skills add https://github.com/imclab/xrA1-swarm --skill create-stories-imclab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents brittle, untraceable development by breaking an epic and its governing specs into small stories that are directly linked to GDD requirements and ADR decisions.

Core Features & Use Cases

  • Traceable story decomposition: Converts GDD acceptance criteria into implementable story files that embed TR-IDs, ADR governance, and acceptance criteria.
  • Spec-driven implementation gates: Loads the epic’s GDD, governing ADRs, and control manifest, validates ADR existence, and runs the QA lead readiness gate to ensure testability.
  • Developer-ready outputs: Produces production/epics/[epic-slug]/story-NNN-[slug].md files in dependency order (foundation/core first, UI last), then routes Logic/Integration stories to concrete QA test-case specs.

Quick Start

Run create-stories for a chosen epic by calling /create-stories epic-slug (optionally adding --review lean, full, or solo).

Frequently Asked Questions about create-stories

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

FAQPage Schema
How do I decompose an epic into implementable stories with traceability?

Story decomposition converts an epic and its governing specs into implementable story files that embed TR-IDs, ADR governance, and acceptance criteria. It uses the GDD, governing ADRs, and control manifest as the source of truth to ensure full traceability.

What is the process for validating QA readiness before story implementation?

QA readiness gating loads the epic's control manifest, validates ADR existence, and runs the QA lead readiness gate to ensure testability. It then routes Logic and Integration stories to concrete QA test-case specs before development begins.

How do I structure story files in dependency order for project orchestration?

Dependency ordering writes production/epics/[epic-slug]/story-NNN-[slug].md files, placing foundation and core stories first, followed by UI stories last. This ensures development builds upon established dependencies.

Do I need ADR governance and a GDD before generating story files?

Yes, ADR governance and a GDD are required. The process uses the GDD, governing ADRs, and control manifest as the source of truth, validating ADR existence and converting GDD acceptance criteria into implementable story files.

What is the best way to convert GDD acceptance criteria into developer-ready markdown?

Converting GDD acceptance criteria into developer-ready markdown generates story files embedding TR-IDs and ADR governance using YAML-defined metadata. Execute by calling the create-stories command with the epic slug and optional review flags.

Can I use epic planning workflows for XR and spatial intelligence studio projects?

Yes, epic planning workflows apply to XR and spatial intelligence studio contexts where epics must be decomposed in dependency order before development begins. The process ensures stories are directly linked to GDD requirements and ADR decisions.