userstory-implement

Orchestrate Foundation User Story execution from planning through QA with developer dispatch.

19|3|Updated Jul 19, 2024
One-click install
npx skills add https://github.com/danielterra/FOUNDATION --skill userstory-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: userstory-implement
Source: https://github.com/danielterra/FOUNDATION/tree/main/.claude/skills/userstory-implement
Command: npx skills add https://github.com/danielterra/FOUNDATION --skill userstory-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates end-to-end execution of a Foundation User Story from planning to QA by coordinating briefs, developer handoffs, and validation, ensuring smooth delivery without direct PO-to-dev communication.

Core Features & Use Cases

  • Orchestrates the Architect briefing in Modo Execução 2a and the subsequent Costura process to validate state and progress of the User Story.
  • Dispatches backend and frontend developers in parallel or sequentially according to the execution plan, consolidating outputs with unified testing guidance.
  • Automatically updates changelog and workflow status to reflect stages: Planned → In Progress → In Validation (QA), enabling QA-driven finalization.

Quick Start

Provide the User Story IRI and let this skill orchestrate briefing, dev dispatch, and QA handoff.

Frequently Asked Questions about userstory-implement

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

FAQPage Schema
How do I orchestrate end-to-end user story delivery from planning to QA?

To orchestrate user story delivery, you provide the User Story IRI. The skill validates its state, triggers the architect briefing, dispatches backend and frontend developers in parallel or sequentially, and hands off consolidated outputs to QA.

How does automated sub-agent coordination work for backend and frontend development?

Automated sub-agent coordination dispatches backend and frontend developers in parallel or sequentially according to the execution plan. It consolidates developer outputs with unified testing guidance to streamline QA validation.

Can I automate user story workflow status updates through In Progress and Validation?

Yes, you can automate user story workflow status updates. The skill automatically updates changelog and workflow status to reflect stages from Planned to In Progress and Validation, enabling QA-driven finalization.

Do I need a specific User Story state before triggering automated dev dispatch?

Yes, the User Story must be in a Planned or Ready for Dev state. The skill validates the initial state before triggering the architect's briefing and proceeding with the subsequent development orchestration.

What is the best way to coordinate developer handoffs without direct PO-to-dev communication?

The best way to coordinate developer handoffs without direct PO-to-dev communication is using an orchestration skill. It manages architect briefings, dispatches developers, and consolidates outputs automatically via the Claude harness.

Why does user story orchestration fail when dispatching parallel developers?

User story orchestration may fail during parallel developer dispatch if the execution plan constraints are not met. The skill includes robust state validation checks and error handling to manage sub-agent coordination failures.