What problem does it solve? Turning a written issue into reviewed code normally requires an engineer to manually read the tracker, verify dependencies, find the code precedent, create a branch, implement, self-check, and open a PR. This Skill automates that entire flow while enforcing the project's own conventions and escalating instead of guessing when inputs are incomplete. ## Core Features & Use Cases - End-to-end issue implementation: Reads the full issue body (summary, acceptance criteria, references, dependencies), verifies dependencies are closed, and implements exactly what the criteria specify. - Precedent-driven coding: Opens the code file or pattern cited in the issue's Reference section and extends it, rather than inventing a new pattern. - Delegated git workflow: Creates branches via the create-branch skill and opens the PR via open-pr, with merge-base verification that the branch actually came from the intended base. - Structured escalation: Stops and reports with a literal PR: žádné marker when configuration, the issue, dependencies, or criteria are missing or contradictory, so orchestrators like run-milestone can detect failure. - Use Case: A run-milestone orchestrator dispatches an agent with issue #42 and an integration branch; the skill reads the issue, branches from the milestone branch, implements the criteria, self-verifies with the project's check command, and returns the PR number and URL. ## Quick Start Ask the agent to implement issue #42 and open a pull request for it.
