user-story-delivery
User Story Delivery
You are acting as the coordinator for one complete user story delivery cycle. Your job is to compose two specialist workflows:
user-story-implementer: implements exactly one story, verifies it, commits, pushes, and creates or updates a PR.user-story-reviewer: reviews the PR against the original issue and either requests changes, fixes a small issue, approves, comments, or merges according to its own workflow.
Keep implementation and review responsibilities separate. Do not duplicate either specialist skill's detailed workflow here. The value of this skill is orchestration: clear handoffs, bounded review-fix loops, and a final delivery status the user can trust.
PREREQUISITE: The GitHub CLI (gh) MUST be installed and fully authenticated (gh auth login) because the specialist skills rely on it.
Delegation Requirement
This workflow is designed to use subagents so implementation and review remain independent. If the current runtime requires explicit user permission before starting subagents, and the user's request did not clearly ask for subagents, delegation, or the full implement-review workflow, ask for confirmation before starting. A request such as "use the user-story-delivery skill to run the full workflow" is enough to proceed because this skill's purpose is delegation.
Workflow
- Identify the Target Story
- Prefer the specific story ID or issue number supplied by the user.
More from eho/agent-skills
user-story-implementer
Implement a single user story or task from a GitHub Issue backlog. Executes a single iteration by fetching the next open issue, assigning it, implementing the code, creating a branch and PR, and moving on. You MUST use this skill when asked to "implement a user story", "run one iteration", "do the next task", or "complete a task from the backlog".
39user-story-reviewer
Review an implemented user story or task (via GitHub Pull Request) for completeness, test coverage, and code quality. Use this when asked to QA, review a PR, verify implementation, or as a follow-up to the user-story-implementer skill.
32prd
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
26prd-to-github-milestone
Parses a Product Requirements Document (PRD) to extract User Stories and creates corresponding GitHub Issues. It can optionally link them to a GitHub Milestone. This skill acts as a setup phase for GitHub-native issue tracking. Make sure to use this skill whenever the user asks to "send the PRD to GitHub", "create issues from the PRD", "setup the milestone", or mentions turning requirements into actionable GitHub issues.
18public-repo-explorer
Instructs the agent on how to efficiently browse public GitHub repositories using a local shallow clone. You MUST use this skill whenever the user asks you to scan, examine, clone, or extract information from a public Git repository, or whenever they provide a GitHub URL to explore.
14design-doc-reviewer
Review a design document for completeness, clarity, and quality — including user story readiness for agent implementation. Produces structured feedback with specific gaps, strengths, and a prioritized improvement checklist. Use when asked to review a design doc, critique a design, check a spec, review the PRD, or audit the requirements.
13