agentic-engineering-implementation

What problem does it solve? Coordinating implementation work across local agents, Google Jules, and human contributors often leads to scope creep, unverified claims of completion, and lost provider records. This Skill enforces a gated implementation phase that only runs after specification, architecture, design, and planning approvals are satisfied. ## Core Features & Use Cases - Bounded Implementation: Produces scoped source code, tests, migrations, and documentation strictly against an approved plan, stopping before integration. - Provider Routing: Routes external work through delivery channels (e.g., Google Jules) while keeping sensitive, integration, and gatekeeping work local, with isolated parallel ownership. - Traceable Artifacts: Generates task-local verification records and provider artifacts, and refuses to self-certify completion. - Use Case: After planning gates pass, delegate a bounded feature task to Jules for a PR while implementing sensitive authentication changes locally, then collect verification evidence for review. ## Quick Start Use $agentic-engineering-implementation to implement this approved change with evidence.