dev-story

Orchestrates end-to-end story implementation with context loading, agent routing, and test generation.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/solace-ill/vector-flow --skill dev-story-solace-ill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-story
Source: https://github.com/solace-ill/vector-flow/tree/main/.claude/skills/dev-story
Command: npx skills add https://github.com/solace-ill/vector-flow --skill dev-story-solace-ill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates complex end-to-end feature stories by loading full context, routing to the appropriate programmer agents, implementing code, and generating tests, all from a single story file.

Core Features & Use Cases

  • Context loading: Reads ADRs, manifests, TR data and dependency status to form a complete execution context.
  • Agent routing: Routes to the correct specialists (e.g., engine, UI, gameplay programmers) based on story layer and type.
  • Implementation & testing: Drives code changes and creates tests per acceptance criteria and test standards.
  • Governance: Enforces ADR guidelines, manifest compatibility, and session-state rules throughout the workflow.

Quick Start

Provide a story path to start; the system will load full context, route to the right programmer, implement the story, and generate tests.

Frequently Asked Questions about dev-story

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

FAQPage Schema
How do I orchestrate end-to-end story implementation from a single file?

End-to-end story implementation is orchestrated by loading full context from a story path, routing to appropriate programmer agents, and producing code and tests while validating ADR and manifest requirements.

What is the best way to ensure ADR guidelines are followed during feature development?

ADR guideline adherence is enforced during story implementation by validating architecture decision records and control-manifest rules before coding begins, ensuring compliance throughout the agent routing workflow.

Can I route feature implementation to specific programmer agents based on story type?

Feature implementation can be routed to specific programmer agents like engine, UI, or gameplay specialists based on the story layer and type defined in the loaded context.

How do I manage session state and blockers during complex code orchestration?

Session state and blockers are managed throughout the story implementation workflow, which enforces control-manifest rules and testing requirements while maintaining execution context across development phases.

Does story implementation work for both Logic and Integration development phases?

Story implementation applies to both Logic and Integration stories across development phases, ensuring dependency requirements and test standards are validated before generating code and tests.