implement-code

Orchestrates execution of approved specification work items through delegated coding, review, and completion sync.

4|1|Updated Jul 31, 2025
One-click install
npx skills add https://github.com/alvis/.agents --skill implement-code-alvis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-code
Source: https://github.com/alvis/.agents/tree/main/plugins/specification/skills/implement-code
Command: npx skills add https://github.com/alvis/.agents --skill implement-code-alvis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-running implementation work drifts from its approved specification: plans go stale, completed tasks get silently invalidated, and publication happens before review. This Skill executes one approved specification work item end to end while keeping contract, plan, code, review, and publication strictly separated and evidence-bound. ## Core Features & Use Cases - Contract-first execution: Materializes and verifies the authoritative specification (local, inline, or Notion-backed) against provenance before any coding begins, returning ready_for_specification on drift. - Delegated task dispatch: Reads state.md as the canonical plan, schedules only runnable leaf tasks, and dispatches coding children with deferred publication and a parent-owned review capsule. - Gated review and publication: Runs alignment review, a usage-trace gate, source completion sync, and scoped-save commit/finalization/PR handoffs only after all semantic gates pass. - Use Case: After a plan is approved with plan-code, run this Skill to implement each ticket, collect per-task evidence, revalidate against spec changes, and produce a clean reviewed commit chain ready for PR creation. ## Quick Start Ask the agent to implement the approved specification at a given path or reference, optionally passing a work id, and let it orchestrate coding, review, and completion. ## Quick Start Use implement-code to execute the approved specification at specs/feature-x.md with work id feature-x and defer publication.

Frequently Asked Questions about implement-code

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement an approved specification plan with an AI agent?

Invoke implement-code with the authoritative specification path or reference after plan approval. It reads state.md as the canonical plan, dispatches runnable leaf tasks to coding skills, runs review and usage tracing, and returns completion status with evidence.

What happens when the specification changes during implementation?

The run stops with needs_revalidation instead of continuing from stale intent. Affected non-done tasks become blocked, done tasks gain stale validity with remediation tasks, and the plan must be reapproved against the new content before work resumes.

Does implement-code support Notion-backed specifications?

Yes, it materializes Notion sources through sync-spec using an explicit transport profile with exact-byte SHA-256 verification. Completion requires a verified round trip via sync-spec in complete mode before any code publication.

Can implement-code commit and push code directly?

No, it never performs history or publication mutations itself. It delegates saves to coding:commit with a checksum-bound scoped manifest, finalization to coding:finalize-commits, and PR creation to coding:pr create, or defers publication entirely.

When should I not use implement-code?

Do not use it for unticketed feature work, drafting specifications, or direct contract authoring. Draft-required, mismatch, and refusal modes route back to specification:plan-code or report the blocking condition without dispatching coding work.