Menu
Implement an apply-ready OpenSpec change with verification and optional review handoff before explicit archive.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Reviews implementation architecture with firm, evidence-based judgment: separation of concerns, maintainability, ownership, dependency direction, stability/change boundaries, validation, persistence/state ownership, runtime coordination, Conway fit, evolution strategy, and refactoring discipline. Use when asked for architecture review of module/package boundaries, cross-capability dependencies, shared code, abstraction drift, validation placement, service boundaries, strangler work, branch-by-abstraction changes, or refactoring claims.
Reviews data movement and structural resource costs: filtering, pagination, streaming, materialization, copying/cloning, allocation, serialization/parsing, batching, N+1 I/O, backpressure, lock contention, and APIs that force callers to pay unnecessary costs. Use when asked for data-flow or performance review of data-heavy paths, persistence/search/streaming APIs, parsers, async workflows, hot paths, batch jobs, CLI pipelines, or hidden memory/throughput risks.
Review delivered code, CI, config, and generated assets. Use when explicit implementation review is requested; OpenSpec artifacts are optional context.
Reviews implementation security by tracing assets, actors, attacker-controlled input, trust boundaries, enforcement points, and sinks across auth, authorization, injection, command/path/URL handling, deserialization, secrets, logs, resource exhaustion, races, supply-chain, and crypto surfaces. Use when asked for security review of external inputs, auth flows, APIs, CLI commands, file/network/subprocess access, stored payloads, dependency scripts, tenant isolation, privilege boundaries, or security-sensitive assumptions.
Reviews implementation test quality by judging whether tests prove required behavior, invariants, failure modes, and realistic regressions across the relevant codebase. Use when asked for test review of meaningful coverage, public APIs, CLIs, generated outputs, validators, parsers, persistence, mocks, snapshots, property tests, fuzzing, or regression gaps.
Explain Caveman token-stats support in Pi. Upstream Caveman stats are powered by Claude Code hooks and session logs; this Pi package does not fake token savings. Triggers on /skill:caveman-stats or "caveman stats".
| name | implement |
| description | Implement an apply-ready OpenSpec change with verification and optional review handoff before explicit archive. |
| disable-model-invocation | true |
Implement an apply-ready OpenSpec change. Run implementation, verify it, and stop before archive unless a separate review is explicitly requested.
openspec status --change <name> --json and stop if the change is not apply-ready.openspec instructions apply --change <name> --json./skill:review-implementation <change-name>
Review findings are separate from apply completion and may be returned inline or saved only if the caller explicitly asks.
Implementation is complete when:
Return: