ln-400-story-executor

Name: ln-400-story-executor
Availability: InStock
Author: dorrio

Execute Story tasks sequentially with test-driven development and verification.

Updated Dec 11, 2025

Search Tags:#code review #task management #workflow automation #test-driven development #agile development #story execution

Ready to run

npx skills add https://github.com/dorrio/sorteo-app-generator --skill ln-400-story-executor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ln-400-story-executor
Source: https://github.com/dorrio/sorteo-app-generator/tree/main/.agent/skills/ln-400-story-executor
Command: npx skills add https://github.com/dorrio/sorteo-app-generator --skill ln-400-story-executor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the development process by guiding the sequential execution of tasks within a software Story, ensuring adherence to a test-driven development approach and maintaining code quality.

Core Features & Use Cases

Sequential Task Execution: Guides the implementation of Story tasks one by one.
Contextual Code Review: Prompts for code review before implementation to understand changes.
Test-Driven Development: Enforces writing tests to meet acceptance criteria.
Verification: Executes predefined verification methods for each task.
Self-Review & Commit: Facilitates code self-review and user-approved commits.
Status Updates: Updates Story status to "To Review" upon completion.
Use Case: A developer can use this Skill to systematically implement all planned features for a new user authentication module, ensuring each step is tested and reviewed before moving to the next.

Quick Start

Use the ln-400-story-executor skill to begin implementing the tasks for the current Story.

Frequently Asked Questions about ln-400-story-executor

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

FAQPage Schema

How do I execute development tasks sequentially within a single Story?▼

Sequential task execution is performed by guiding the implementation of Story tasks one by one, enforcing context reviews and test-driven development practices before moving to the next. It manages task execution, verification, and commits within a feature branch.

What is test-driven development enforcement in story execution?▼

Test-driven development enforcement in story execution requires writing tests to meet predefined acceptance criteria before implementation. It ensures code quality by verifying each task against its acceptance criteria using predefined verification methods during sequential execution.

How do I manage task verification and commits in a feature branch?▼

Task verification and commits in a feature branch are managed by executing predefined verification methods, facilitating code self-review, and prompting for user-approved commits. Upon completion, the Story status updates to 'To Review'.

Do I need a kanban board and active feature branch for story execution?▼

Yes, story execution requires a Story with tasks defined in 'docs/tasks/kanban_board.md' and an active feature branch. These prerequisites ensure context reviews and test-driven development practices operate within the correct version control environment.

Why does my story execution prompt for a contextual code review?▼

Contextual code review is prompted before implementation to help developers understand existing changes and maintain code quality. This step ensures sequential task execution aligns with the current state of the feature branch and project requirements.