create-story

Classify Momentum story tasks into change types and inject implementation guidance.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/iamsteveholmes/momentum --skill create-story-iamsteveholmes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-story
Source: https://github.com/iamsteveholmes/momentum/tree/main/skills/momentum/skills/create-story
Command: npx skills add https://github.com/iamsteveholmes/momentum --skill create-story-iamsteveholmes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill orchestrates Momentum story creation, including automatic change-type classification, injected implementation guidance, and AVFL validation.

Core Features & Use Cases

  • Automatic change-type classification for each story task
  • Injection of Momentum Implementation Guide into Dev Notes
  • AVFL checkpoint validation against epic intent
  • Metadata generation and integration with stories/index.json

Quick Start

Run the momentum create-story workflow to generate a Momentum story skeleton with AVFL validation.

Frequently Asked Questions about create-story

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

FAQPage Schema
How do I automate Momentum story creation with AVFL validation?

Momentum story creation is automated by classifying tasks into change types and injecting implementation guidance. It produces a story skeleton with Dev Notes, a Momentum Implementation Guide, and an AVFL checkpoint to validate epic intent alignment.

What is change-type classification in Momentum story tasks?

Change-type classification determines the specific implementation signals for each task within a Momentum story. It guides development by automatically categorizing tasks and injecting corresponding guidance into the Dev Notes section.

How does an AVFL checkpoint validate epic intent during story creation?

An AVFL checkpoint validates epic intent by verifying that the generated Momentum story aligns with the overarching epic goals. It is applied during story creation to ensure the injected implementation guide remains consistent with the intended scope.

Do I need Dev Notes in my Momentum story workflow?

Dev Notes are required in the Momentum story workflow to house the injected Momentum Implementation Guide. This ensures developers have direct access to change-type guidance and AVFL validation details within the story.

What's the best way to generate Momentum story metadata for index.json integration?

Generating Momentum story metadata for index.json is handled during the create-story workflow. It automatically classifies change types, injects guidance, and produces the necessary metadata to integrate the story skeleton seamlessly.