implement-story

name	implement-story
description	Implement one story into a story branch and open a PR into the epic feature branch using the repository's story workflow.
triggers	["implement-story","story PR","story branch"]

Implement Story

Use this skill when the orchestrator asks you to implement a single story file.

Required Inputs

The prompt will provide:

• story file path,
• story id and title,
• target story branch,
• epic feature branch,
• target repository,
• required quality gates.

Workflow

1. Read AGENTS.md and all relevant repo instructions.
2. Read the story file completely.
3. Read every referenced ADR, design doc, traceability file, and test plan.
4. Search existing code before claiming a type, function, command, test, or generated file does not exist.
5. Produce an implementation plan.
6. Self-approve the plan only when there are no open questions and the plan identifies:
   • code areas to touch,
   • generated files that must not be edited,
   • shared files and conflict risk,
   • tests to add or run,
   • traceability updates,
   • PR template content.
7. Implement the story.
8. Run repo-appropriate checks.
9. Run local persona review using pr-persona-review.
10. Update the story doc status and traceability.
11. Commit, push, and open a draft PR into the epic feature branch.

When creating the PR, write the body to a local markdown file and use gh pr create --body-file <path>. Do not pass a long multiline body directly through --body; it is fragile in non-interactive terminal sessions.

Branch Rules

• Work only on the story branch supplied by the orchestrator.
• Base the story branch on the epic feature branch.
• Do not push to develop, main, or the epic feature branch except through a PR.
• Do not merge PRs.

Required PR Body

The PR body must include:

• story link/path,
• summary,
• acceptance criteria checklist,
• tests run,
• traceability updates,
• persona review result,
• known risks,
• human review request.

Stop Conditions

Stop and page the human through the orchestrator when:

• a requirement is ambiguous,
• a security or migration choice is required,
• a dependency addition is needed,
• a generated file must be changed but the generation command is unknown,
• the same quality gate fails after the retry budget.