메뉴
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.