agentic-implementation-orchestrationlisted

Orchestrate an approved Issue-backed implementation with a strongest-capability parent and bounded implementer agents. Use when decomposing an authorized feature or phase; mapping work packets to Issue acceptance criteria; deciding what the parent retains versus delegates; assigning exclusive files or modules; preserving unrelated work in a shared workspace; integrating changes into coherent commits; opening or updating a draft PR after local gates; or independently accepting delegated work before cold review. Covers dependency graphs, capability routing, ownership, concurrency, compact and full work packets, structured returns, escalation, integration, tracking impact, and parent-side verification. Do not use to decide product scope, treat Issue ratification as implementation authority, run cold review, or perform ordinary Issue/PR administration.
gidde032/agentic-workflow · ★ 0 · AI & Automation · score 63

Install: claude install-skill gidde032/agentic-workflow

# Agentic Implementation Orchestration The operating model is simple: > The strongest available capability owns interpretation, decomposition, risk, > integration, and acceptance. Other agents implement bounded work packets. Delegation does not transfer accountability. An implementer's report is a lead; the orchestrator verifies the actual workspace before accepting it. Worked examples and provenance: `examples.md`. --- ## 1. Boundaries with the sibling skills This skill owns the implementation manager layer: - dependency-aware decomposition; - retain-versus-delegate decisions; - implementation work packets; - exclusive file or module ownership; - safe concurrency and integration order; - structured implementer returns; - parent-side acceptance of delegated work; - mapping packets to the owning Issue and acceptance criteria; - preserving the Issue/branch/PR relationship during implementation; - parent-owned coherent commits and draft-PR updates; and - preventing implementers from making unauthorized external GitHub changes. Route adjacent mechanics to their owners: | Need | Owning skill | |---|---| | Cheaper-model failure modes, brief hardening, escalation triggers | `agentic-driving-weaker-models` | | Capability tiers, cost posture, session lifecycle | `agentic-session-economics` | | Cold independent review after implementation is integrated | `agentic-review-orchestration` | | Tests, quality gates, regression contracts, and repository-owned Actions evidence | `age