story-decomposition

Decompose large tasks into independent stories with acceptance criteria and verification commands.

2|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/thesyntaxninja/syntaxninja-dojo --skill story-decomposition-thesyntaxninja
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-decomposition
Source: https://github.com/thesyntaxninja/syntaxninja-dojo/tree/main/skills/story-decomposition
Command: npx skills add https://github.com/thesyntaxninja/syntaxninja-dojo --skill story-decomposition-thesyntaxninja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break large tasks into independent, verifiable stories to enable focused work and measurable progress.

Core Features & Use Cases

  • Independent, verifiable stories that fit within a single context window.
  • A clear template for each story including goals, dependencies, files, and acceptance criteria.
  • Chaining into Ralph loop and PRD generation to align planning with execution.

Quick Start

Decompose a large task into a set of independent, verifiable stories following the provided template.

Frequently Asked Questions about story-decomposition

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

FAQPage Schema
How do I break down a large coding task that exceeds a single context window?

Story decomposition is the process of breaking large tasks into independent, verifiable stories to enable focused work. Each story follows a defined template including goals, dependencies, files, and acceptance criteria to ensure measurable progress across multiple stories.

What is the best way to structure task decomposition for incremental validation?

Task decomposition for incremental validation requires splitting work into independent stories using a defined template. Each story must include specific goals, dependencies, files, and acceptance criteria to enable focused work and measurable progress across multiple context windows.

How do I write acceptance criteria for decomposed stories?

Writing acceptance criteria for decomposed stories involves applying a defined template that includes goals, dependencies, files, and a verification command. This ensures each independent story is verifiable and enables measurable progress when tasks exceed a single context window.

When do I need to decompose a task into multiple independent stories?

Task decomposition into multiple independent stories is needed when a task exceeds a single context window or requires incremental validation. This process breaks large tasks into verifiable stories with defined goals, dependencies, files, and acceptance criteria.

Can I chain decomposed stories into PRD generation and execution loops?

Chaining decomposed stories into PRD generation and Ralph loops aligns planning with execution. This integration allows independent, verifiable stories with defined acceptance criteria to flow seamlessly into downstream generation and execution workflows for focused work.

Does each decomposed story require a verification command?

Each decomposed story requires a verification command as part of its defined story format. This ensures the independent stories are verifiable, enabling focused work and measurable progress when tasks exceed a single context window or require incremental validation.