execute-story

Implements a Ready story's acceptance criteria while filing ADRs and BUGs during execution.

Updated May 25, 2026
One-click install
npx skills add https://github.com/DATA-AI-XYZ/Tandem --skill execute-story-data-ai-xyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execute-story
Source: https://github.com/DATA-AI-XYZ/Tandem/tree/main/skills/execute-story
Command: npx skills add https://github.com/DATA-AI-XYZ/Tandem --skill execute-story-data-ai-xyz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns a Ready story file into disciplined implementation work by enforcing the Definition of Ready before coding, tracking acceptance criteria as they are completed, and capturing every decision and defect as versioned markdown artefacts instead of losing them in chat history. ## Core Features & Use Cases - DoR Gate Enforcement: Verifies the Definition of Ready checklist and refuses to start work on stories that are not actually ready. - AC-Driven Implementation: Works acceptance criteria one at a time, ticking each checkbox in the same edit as the code change, and wires the paired testplan's test cases. - Decision and Defect Capture: Files ADRs for non-obvious decisions and BUGs for observed defects on the spot, with a spec-error exception that routes wrong acceptance criteria to an ADR instead. - Use Case: A solo developer pulls STORY-03.1.02 from the stories folder; the skill flips its status to in-progress, implements each AC, records two ADRs and one BUG, and stops at in-review ready for the testplan run. ## Quick Start Ask the assistant to start work on a specific Ready story file, for example by saying to execute STORY-03.1.02 from the stories folder.

Frequently Asked Questions about execute-story

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

FAQPage Schema
How do I start working on a story with this skill?

Provide the story file path or ask it to list Ready stories. It resolves the stories folder via the path map, verifies the Definition of Ready, flips status to in-progress, and begins implementing acceptance criteria one at a time.

What happens if a story fails the Definition of Ready check?

Execution stops immediately. The skill lists the failing checklist items and asks the user how to proceed rather than starting work on an unprepared story.

Does execute-story run the testplan and close out the story automatically?

No. By default it stops at in-review so run-testplan and close-out-story remain deliberate user-invoked steps. A combined full cycle only happens on explicit user request or for paperwork-only ratification spikes.

How are decisions and bugs handled during story execution?

Non-obvious decisions trigger an immediate ADR with the next free ADR-NNNN ID, and observed defects trigger a BUG file. If a failure shows the acceptance criterion itself is wrong, an ADR documenting the spec correction is filed instead of a BUG.

What happens when the project kit is not wired up correctly?

A pre-flight doctor gate runs first and fails loudly on an unwired project, printing a message directing the user to run the install command. The skill refuses to proceed rather than silently no-oping.