القائمة
Plan and execute implementation against Cavekit SPEC.md. Use when users invoke /ck:build, ask to build from SPEC.md, implement Cavekit tasks, build the next task, or run a selected §T task.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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 | cavekit-build |
| description | Plan and execute implementation against Cavekit SPEC.md. Use when users invoke /ck:build, ask to build from SPEC.md, implement Cavekit tasks, build the next task, or run a selected §T task. |
Single-thread plan-then-execute against project-root SPEC.md. No swarm, hooks, or runtime orchestration.
Read bundled ../../FORMAT.md before parsing task status or spec references. The bundled file defines format; project-root SPEC.md is the working artifact.
SPEC.md from project root. If missing, tell the user to invoke /ck:spec first and stop.§T.n or Tn → that task only--next → lowest-numbered row with status . or ~--all or no args → every . row in §T orderFor the chosen task(s), produce a concise plan before editing:
Wait for user approval unless the user explicitly asked for autonomous execution.
Per task in order:
. to ~ in SPEC.md.~ to x.On test/build failure:
cavekit-backprop and cavekit-spec to update §B/§V/§T before resuming.Never silently fix a root cause that should become spec memory.
cavekit-build may flip §T status cells for chosen tasks.SPEC.md edits belong to cavekit-spec.A task can be marked x only when:
SPEC.md.