← ClaudeAtlas

implement-itlisted

Implementation-stage skill in the Agentic Engineering pipeline. Takes any approved GitHub issue satisfying its entry contract — whether `plan-it` drafted it or it already existed some other way — and carries it through working-branch readiness, the implementation itself, verification, semantic commits, issue closure, and dependency-ready recalculation for the next issue. Use when implementing, committing, verifying, or closing an approved issue, checking what's next in a milestone, or performing a human-authorized delivery correction handed back from `ship-it`. Performs the approved implementation itself, consulting the applicable stack companion for implementation knowledge and conventions — it does not own framework-specific conventions, decide what work should exist, or handle milestone PR readiness, PR creation, or release.
elieandraos/agentic-engineering · ★ 0 · Code & Development · score 70
Install: claude install-skill elieandraos/agentic-engineering
# implement-it ## What this skill is `implement-it` is the implementation stage of the Agentic Engineering pipeline. It starts from any approved, implementation-ready GitHub issue — whether `plan-it` drafted it or it already existed some other way — and carries that single issue's work through verified Git/GitHub implementation, ending at issue closure and the next-issue recommendation. It also accepts an explicitly human-authorized delivery correction handed to it directly by `ship-it`, which requires no issue to exist at all (see "Delivery corrections" below). ## Pipeline position `lab-it → plan-it → implement-it → ship-it` This skill intentionally begins only once an issue is approved, or a delivery correction is explicitly authorized — it never decides what work should exist. It hands off to `ship-it` once a milestone genuinely has zero open issues remaining, not merely an empty dependency-ready set (open issues can all be blocked without the milestone being done — `rules/sequencing.md`'s "When the ready set is empty"), or once it has performed a correction `ship-it` hands back. ## What it owns - Working-branch readiness: the Backlog/hotfix-vs-milestone-branch decision, before implementation starts. - Companion activation: determining which available stack, implementation, testing, and tooling skills apply before implementation begins, and activating all applicable companions rather than treating the first matching skill as sufficient. - Performing the approved i