build 是做什么的？
根据 SPEC.md 规划并执行实现。原生单线程循环，无需子代理。测试或构建失败时，自动调用反向传播技能再重试 —— 失败的验证始终考虑是否应添加新的 §V 不变量来防止复发。当用户请求构建、实现、执行规范或处理特定 §T 任务时触发（例如 build §T.3、build --next、implement next task、run the build）。要求存在 SPEC.md；若缺少，则交由 spec 技能处理。
根据 SPEC.md 规划并执行实现。原生单线程循环，无需子代理。测试或构建失败时，自动调用反向传播技能再重试 —— 失败的验证始终考虑是否应添加新的 §V 不变量来防止复发。
该技能（juliusbrussee/build）是一个基于 SPEC.md 的“规划-执行”实现工具。它采用原生单线程循环设计，无需依赖子代理。当用户请求构建、实现、执行规范或处理特定 §T 任务（例如 `build §T.3`、`build --next`、`implement next task`、`run the build`）时触发。该技能要求当前工作目录中存在 `SPEC.md` 文件，如果缺失，则会交由 spec 技能处理。在测试或构建失败后，技能会自动调用反向传播技能并对失败进行分析，确保任何失败的验证都会考虑是否需要新增一个 §V 不变量以防止相同错误再次发生。该技能适用于开发者和 AI 代理用户，在持续开发或测试循环中提供高效的自动回退和修复机制。
npx skills add https://github.com/juliusbrussee/cavekit/tree/main/skills/buildInstalled? Explore more 生产力与协作 skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →
根据 SPEC.md 规划并执行实现。原生单线程循环，无需子代理。测试或构建失败时，自动调用反向传播技能再重试 —— 失败的验证始终考虑是否应添加新的 §V 不变量来防止复发。当用户请求构建、实现、执行规范或处理特定 §T 任务时触发（例如 build §T.3、build --next、implement next task、run the build）。要求存在 SPEC.md；若缺少，则交由 spec 技能处理。
This repo contains 4 individual skills — each has its own dedicated page.
Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.
Caveman encoding for SPEC.md and spec-adjacent writes. Loaded by /spec, /build, /check. Cuts tokens ~75% vs prose while staying precise. Triggers on any write to SPEC.md or when user says "caveman", "compress this", "be brief".
Read-only drift detector. Diffs SPEC.md against current code and reports violations grouped by severity. Writes nothing — suggests remedies via the spec or build skills but never invokes them. Triggers when the user asks to check drift, audit the spec, verify invariants, or ask whether code still matches the spec. Phrasings: "check drift", "audit the spec", "does the code still match §V", "check invariants", "spec vs code".
Create, amend, or backprop bugs into SPEC.md at repo root. Sole mutator of the project spec. Triggers when the user asks to write a spec, start a new spec, distill a spec from existing code, add invariants, amend sections (§G, §C, §I, §V, §T, §B), or record a bug via backprop. Common phrasings: "write the spec for...", "new spec", "bug: ...", "amend §V.3", "distill spec from code", "spec this idea". Reads and follows FORMAT.md for the caveman encoding rules and pipe-table shape of §T and §B.
Gemini CLI one-shot prompts, summaries, generation, skills, hooks, MCP, or Gemma routing.
Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.
Create, edit, audit, tidy, validate, or restructure AgentSkills and SKILL.md files.
Search, install, update, sync, or publish agent skills with the ClawHub CLI and registry.
Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.
List, configure, authenticate, call, and inspect MCP servers/tools with mcporter over HTTP or stdio.