story-craft

Generate user stories with acceptance criteria using Example Mapping and INVEST scoring.

Updated May 10, 2026
One-click install
npx skills add https://github.com/rob-broadley/ai-airbase --skill story-craft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-craft
Source: https://github.com/rob-broadley/ai-airbase/tree/main/cadre/skills/story-craft
Command: npx skills add https://github.com/rob-broadley/ai-airbase --skill story-craft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Story-craft helps teams turn vague ideas into actionable engineering stories by structuring discovery, scoring readiness, and splitting oversized work so it can be delivered safely.

Core Features & Use Cases

  • Example Mapping to uncover rules, examples, and unresolved questions before writing acceptance criteria.
  • INVEST scoring to determine whether a story is independent, negotiable, valuable, estimable, small, and testable.
  • Story splitting patterns (SPIDR + Elephant Carpaccio) to break large stories into thin vertical slices that independently deliver user value.
  • User Story Mapping to organize stories along a user journey and choose a walking skeleton for the first release.
  • Acceptance criteria patterns (Scenario/Gherkin, Rule-based, Checklist) designed to be observable, implementation-independent, and binary.
  • Story dependency mapping to capture dependencies as a DAG for better planning.

Quick Start

Ask the user-story-writer agent to prepare a ready-to-implement user story by running Example Mapping, scoring with INVEST, and producing split options plus binary acceptance criteria.

Frequently Asked Questions about story-craft

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

FAQPage Schema
How do I write acceptance criteria that are clear and testable?

Clear acceptance criteria use observable, implementation-independent, and binary patterns like Scenario/Gherkin, Rule-based, or Checklist formats to ensure user stories are testable and unambiguous.

What is the best way to split large epics into shippable user stories?

The best way to split large epics is applying SPIDR and Elephant Carpaccio patterns to break oversized work into thin vertical slices that independently deliver user value for safe delivery.

How does INVEST scoring validate user story readiness?

INVEST scoring validates user story readiness by checking if a story is Independent, Negotiable, Valuable, Estimable, Small, and Testable, ensuring the product backlog contains actionable engineering tasks.

When should I use Example Mapping for product backlog refinement?

Use Example Mapping for product backlog refinement when you need to uncover business rules, concrete examples, and unresolved questions before generating final acceptance criteria for a feature.

How do I organize user stories along a user journey for release planning?

Organize user stories along a user journey using User Story Mapping to select a walking skeleton for your first release and map story dependencies as a DAG for better planning.