implement-story

Implement story files into tested code and update execution logs.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/jaisonerick/spec-plugin --skill implement-story
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-story
Source: https://github.com/jaisonerick/spec-plugin/tree/main/plugins/spec-plugin/skills/implement-story
Command: npx skills add https://github.com/jaisonerick/spec-plugin --skill implement-story

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the manual, error-prone work of turning a written development story into production-quality code, tests, and documentation so that features meet acceptance criteria and integrate cleanly with the existing architecture.

Core Features & Use Cases

  • End-to-end implementation: Read a story file, derive the plan and architecture context, create or modify the necessary source files, and wire integrations.
  • Test-driven delivery and verification: Write pragmatic automated tests alongside implementation, run verifications, and ensure acceptance criteria are satisfied before marking the story completed.
  • Preserve and integrate designs: Respect interface-design outputs and architecture artifacts, reuse produced files, and document any deviations in the execution log.
  • Use Case: Given a story created by a planning agent, implement the requested backend or UI behavior, add tests that assert acceptance criteria, run them until passing, and update the story execution log and plan status.

Quick Start

Run the implement-story skill with the path to the story file to produce code, tests, verification results, and an updated execution log.

Frequently Asked Questions about implement-story

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

FAQPage Schema
How do I automate turning a development story into working code and tests?

To automate turning a development story into working code, this Skill reads the story file, derives plan and architecture context, creates or modifies source files, wires integrations, and writes tests. It verifies acceptance criteria and updates the execution log.

How does automated story implementation handle existing architecture and interface designs?

Automated story implementation respects existing architecture artifacts and preserves interface-design outputs. It reuses produced files and wires integrations cleanly, documenting any necessary deviations in the execution log to maintain architectural integrity.

Can I use a story file to generate code and verify acceptance criteria automatically?

Yes, you can use a story file to generate code and verify acceptance criteria automatically. The Skill operates on story files produced by planning agents to implement feature code, write automated tests, and run verifications until passing.

What's the best way to implement backend or UI behavior from a plan while ensuring tests pass?

The best way to implement backend or UI behavior from a plan while ensuring tests pass is to execute the story file directly. The Skill derives context from the plan, implements the requested behavior, writes tests asserting acceptance criteria, and runs them until passing.

Do I need a planning agent to create story files before implementing code?

Yes, you need a planning agent like build-stories to create story files before implementing code. This Skill operates specifically on story files produced within a plan to derive architecture context, implement features, write tests, and update the execution log.