story-executor

Execute a single story from the tasks file with Task-spawned agents.

10|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/aimi-so/aimi-engineering-plugin --skill story-executor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-executor
Source: https://github.com/aimi-so/aimi-engineering-plugin/tree/main/plugins/aimi-engineering/skills/story-executor
Command: npx skills add https://github.com/aimi-so/aimi-engineering-plugin --skill story-executor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Execute a single story from the tasks file using Task-spawned agents to ensure consistent, isolated execution and traceable outcomes.

Core Features & Use Cases

  • Single-story execution: runs one story end-to-end from the tasks file.
  • Context isolation: each story starts with a fresh context to prevent memory leakage.
  • Guideline adherence: consults CLAUDE.md and project rules before implementing the story.
  • Status reporting: returns success or failure details to the caller for orchestration.

Quick Start

Trigger execution of a single story from the tasks file using the /aimi:execute command.

Frequently Asked Questions about story-executor

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

FAQPage Schema
How do I autonomously execute a single story from a tasks file?

Autonomous story execution runs one story end-to-end from a tasks file using Task-spawned agents. It consults CLAUDE.md, validates acceptance criteria, performs type checks, and reports results to the orchestrator.

How does context isolation work when executing workflow stories?

Context isolation ensures each story starts with a fresh context to prevent memory leakage during workflow execution. This allows Task-spawned agents to maintain consistent, isolated execution and traceable outcomes.

What is the best way to manage story execution status for orchestration?

Managing story execution status involves returning success or failure details to the caller for orchestration. The workflow applies to scenarios handled by /aimi:execute and /aimi:status commands to track story execution.

Do I need a CLAUDE.md file to run autonomous story execution?

Yes, story execution consults CLAUDE.md and project rules before implementing the story. This guideline adherence ensures the Task-spawned agents follow project conventions during the end-to-end workflow.

Can I execute multiple stories simultaneously with autonomous agents?

This workflow executes a single story end-to-end from the tasks file. It uses Task-spawned agents with isolated context to ensure traceable outcomes, reporting execution results back to the orchestrator for coordination.

Why does story execution validate acceptance criteria and perform type checks?

Validating acceptance criteria and performing type checks ensures the executed story meets project standards before reporting results to the orchestrator. This guarantees consistent, traceable outcomes from the isolated execution context.