implementlisted

Execute a prepared plan or subtask file with quality gates. Reads the plan, builds a verbatim step ledger, implements each step with real-time deviation tracking, routes every finding (adapt / fix-and-log / file-as-card / STOP), spawns an audit subagent (counter-bias), runs tests, drives its slice of the epic's E2E block, and ends with a MANDATORY formatted report (Changes, Architecture Audit, Deviation Report, Cross-Session / Out-of-Scope Findings, Test Results, Commit Message). TRIGGER when: the user wants to carry out an existing plan or subtask file. DO NOT TRIGGER when: there is no plan yet — route to /prepare (to write one) or /analyst (to investigate) first; or the work is a new module/component/command modelled on an existing one that must be registered in an extension point — route to /scaffold.
mik2win/foureyes · ★ 2 · AI & Automation · score 79

Install: claude install-skill mik2win/foureyes

# Implement Plan: $ARGUMENTS This skill carries ONLY invariant workflow logic. Every project-specific fact (commands, paths, architecture, integrations, deploy mapping) is read at runtime from `.claude/PROJECT.md`. --- ## Phase 0 — Load profile **Tooling preflight — one call, before anything else.** Some tools this skill relies on are **deferred** by the harness: the session lists them by name only and loads their schemas on demand, so calling one before it is fetched fails. Listing a tool in `allowed-tools` does **not** un-defer it. Issue a single `ToolSearch` up front covering the whole run — `select:SendMessage,TaskOutput` (continuing the *same* auditor in the Architecture Audit, collecting a backgrounded drive) — instead of one round-trip per discovery. A name already loaded costs nothing to include; a schema discovered missing mid-run costs a turn. Then load context: 1. Read `.claude/PROJECT.md`. If it is missing, or still contains TEMPLATE / placeholder markers, fall back to the root `CLAUDE.md` (always in context) when it carries the commands/architecture/integrations below — proceed on it, noting you're running without a kit profile. Only if *neither* has those facts, **STOP** and tell the user: "Profile not configured — run `/bootstrap` to generate `.claude/PROJECT.md`, then re-run `/implement`." 2. Read the plan / subtask file passed as `$ARGUMENTS`. If `$ARGUMENTS` is a free-text description with no file, note that there is no plan file (the