story-extract

Extract story specifications and acceptance criteria from code implementations.

2|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/telum-ai/speck --skill story-extract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-extract
Source: https://github.com/telum-ai/speck/tree/main/.cursor/skills/story-extract
Command: npx skills add https://github.com/telum-ai/speck --skill story-extract

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of creating detailed documentation for implemented features by extracting story specifications directly from existing code, bridging the gap between implementation and documentation.

Core Features & Use Cases

  • Code Analysis: Analyzes code to identify story boundaries, assess scope, and extract key components.
  • Specification Generation: Creates user stories, acceptance criteria, and technical details using defined templates.
  • Use Case: After a developer implements a new feature, this Skill can scan the relevant code files, identify the user stories and acceptance criteria that were implemented, and generate spec.md and codebase-scan-extracted.md files for documentation.

Quick Start

Extract story specifications from the current codebase.

Frequently Asked Questions about story-extract

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

FAQPage Schema
How do I generate documentation from existing code?

To generate documentation from existing code, this Skill analyzes your codebase to identify story boundaries and extracts user stories, acceptance criteria, and technical details into structured spec files.

Can I extract user stories and acceptance criteria from code automatically?

You can extract user stories and acceptance criteria automatically by scanning implemented features, using predefined templates to assess scope and generate detailed story-level specifications.

What is the best way to document implemented features for agile teams?

Documenting implemented features for agile teams involves scanning code to extract story specifications, bridging the gap between implementation and documentation by outputting detailed spec and codebase scan reports.

Does story extraction support bulk processing of multiple code files?

Bulk extraction is supported, allowing you to scan multiple code files to identify story boundaries and generate an extraction report containing status updates and next steps.

What files are generated when extracting story specifications?

Extracting story specifications generates spec.md and codebase-scan-extracted.md files, containing the extracted user stories, acceptance criteria, and technical details from the analyzed codebase.