菜单
Use when starting a WCBS-enabled session or before any project action, including questions, exploration, planning, edits, tests, reviews, or release work. Routes work to the smallest applicable WCBS skill before acting.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/wfprieto/wcbs-build-kit --skill using-wcbs命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when a WCBS plan, remediation backlog, migration, release, or multi-slice engineering objective has dependent work that requires requirement-to-node traceability, topology validation, READY-frontier scheduling, or evidence-backed node locking. Also activate when the user explicitly requests /graph execution.
Use when the task involves any build, fix, audit, debug, optimization, release, verification, prompt, skill, or agent-design task. Activates the APIVR lifecycle and Elite Build Goals guardrails from this repository before task-specific work.
Use when a build, fix, plan, audit, skill, agent, or pipeline has more than one viable design and the agent must choose the simplest safe option or challenge unjustified complexity.
基于 SOC 职业分类
正在显示 SKILL.md
| name | using-wcbs |
| description | Use when starting a WCBS-enabled session or before any project action, including questions, exploration, planning, edits, tests, reviews, or release work. Routes work to the smallest applicable WCBS skill before acting. |
| activation | session bootstrap and any task where a WCBS skill may apply. |
| required_inputs | User request, active runtime identity, skill catalog, and relevant project context. |
| required_outputs | Selected skill route or evidence-first fallback, evidence state, and next action. |
| authority_dependencies | 00_start_here/SOURCE_OF_TRUTH.md; 10_governance/APIVR_EXECUTION_LIFECYCLE.md; runtime_adapters/adapter-registry.yaml. |
| evidence_requirements | A loaded skill, an executed verification, or an honest Verified, Likely, Suspected, Unknown, Not Run, or Blocked state for every material claim. |
WCBS is an on-demand operating system, not a document dump. Select the smallest skill that changes the decision or the evidence standard before you act.
Before a project action, do one of these explicitly:
User instructions win. Never invent a tool that is absent from the active
runtime map. If the catalog or map is unreadable, stop with Blocked.
| Request signal | First skill | Next mandatory skill when code changes |
|---|---|---|
| New behavior, feature, workflow, or product idea | brainstorming | writing-plans, then test-driven-development |
| Plan, audit remediation, or multi-step change | writing-plans | test-driven-development |
| Bug, regression, flaky test, crash, or unknown failure | systematic-debugging | test-driven-development |
| Implementation request with approved plan | executing-plans | test-driven-development |
| Independent implementation and review | subagent-driven-development | requesting-code-review |
| Review request or received feedback | requesting-code-review / receiving-code-review | verification-before-completion |
| Branch, PR, merge, or cleanup | finishing-a-development-branch | verification-before-completion |
| New or revised skill, prompt, runbook, or agent | writing-skills | 20-pass-protocol |
Add APIVR and the 16 Elite Goals at the tier that matches risk. Installation, runtime adapters, external tools, security, or release artifacts are Comprehensive unless evidence supports a narrower tier.
Use only when no listed skill applies:
1. Inspect the smallest relevant source or system state.
2. State the evidence state: Verified, Likely, Suspected, Unknown, Not Run, or Blocked.
3. Make the smallest reversible action, if authorized.
4. Run the direct verification before making a completion claim.
User: “The installer corrupted a project. Fix it quickly.”
systematic-debugging; do not patch from the symptom.test-driven-development, write the regression first, observe Red,
implement the smallest transaction fix, and verify Green.verification-before-completion before reporting it fixed.If a requested route needs credentials, a clean runtime session, a paid model
run, or a provider account that is unavailable, do not replace it with a
fixture and call it proven. Record Blocked, preserve the deterministic proof
that exists, and name the exact next runtime action.