dev-story

Coordinate story implementation across PRD, ADR, and control manifests.

39|6|Updated May 3, 2026
One-click install
npx skills add https://github.com/cenconq25/claude-code-app-studio --skill dev-story-cenconq25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-story
Source: https://github.com/cenconq25/claude-code-app-studio/tree/main/.claude/skills/dev-story
Command: npx skills add https://github.com/cenconq25/claude-code-app-studio --skill dev-story-cenconq25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reads and orchestrates all required story context (PRD, ADR, and control manifest) and routes end-to-end implementation to the correct mobile framework specialist, ensuring a testable, trackable delivery.

Core Features & Use Cases

  • End-to-end story implementation coordination across PRD, ADR, and manifest.
  • Framework-specific routing to React Native, Flutter, iOS, or Android specialists with supervision.
  • Phase-accurate execution: plan, implement, test, and summarize with artifacts.

Quick Start

Provide a story path to begin the orchestration.

Frequently Asked Questions about dev-story

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

FAQPage Schema
How do I coordinate end-to-end mobile story implementation across PRD and ADR requirements?

Mobile story implementation routes to framework-specific specialists for React Native, Flutter, iOS, or Android, supervising delivery across phases to produce a complete implementation plan and summary with trackable artifacts.

Can I use this story orchestration workflow for React Native, Flutter, iOS, and Android?

Story orchestration applies to stories that have passed a story-readiness gate, require cross-team context, and will be implemented within src/ with tests under tests/.

What is the story-readiness gate before starting mobile code orchestration?

Story orchestration enforces Phase 1 through Phase 6 workflows, reads TR registry data, validates ADR, and outputs a complete implementation plan and summary with artifacts.

How do I enforce phase workflows when shipping mobile code from a planned story?

Provide a story path to begin the orchestration. The workflow then reads the required story context, including PRD, ADR, and control manifest, to route implementation to the correct mobile framework specialist.

Does mobile story orchestration require a control manifest and TR registry data?

Limitations include that stories must have passed the story-readiness gate and require cross-team context. Implementation must occur within src/ with tests under tests/.