ai-blueprint: Skill for Claude Code

implement - build the approved spec

Context reuse: Reuse any required file already loaded in project instructions or the current session. Read it again only if absent, changed, or exact current bytes or line references are needed.

The approved blueprint/context/current-feature.md is the authoritative feature packet. Implement it and stop before the work-level commit or merge.

Start

First action: Before project inspection, preflight, or any other tool call, publish the implement activity as running when blueprint/.state/ exists. Combine it with the first preflight tool batch when supported.

In one preflight batch, read:

• blueprint/config.json
• blueprint/context/current-feature.md
• the current branch, status, and recent relevant log
• the Commands section already loaded from AGENTS.md

Stop for /doctor on invalid config. Stop for /feature, /fix, or /rollback when the active spec is empty. Preserve unrelated worktree changes.

Do not reread the full project overview, coding standards, interaction guide, history, findings, or review ledger before coding. The approved spec already contains the product contract and applicable conventions. Read one targeted section only when the spec explicitly depends on a missing detail. Read findings and review state once at the final handoff.

Inspect the implementation surface in one targeted, batched read before editing. Use one additional read batch only when an exact dependency remains unknown and blocks the next change. Do not list or survey the repository, inspect unrelated examples, or run scratch environment probes. Follow the declared runtime and existing target-area patterns, then let the narrow check expose incompatibilities.

Resolve the work branch before editing. Use the exact **Branch:** value in the spec when present. For an older spec without it, combine the configured prefix for its type with the work title: lowercase ASCII letters and digits, replace each run of other characters with one hyphen, and trim edge hyphens. Feature titles come from the named build-plan item; fix and rollback titles come from their spec heading or target. Stop if the type or title is ambiguous. Create or switch to that exact branch and never implement on the default branch. On resume, start at the first unchecked build step and use git status plus the checked boxes to distinguish finished work from unfinished work.