orobsonn

creating-plans

INTERNAL to the planner agent — NOT a main-loop skill. Do NOT invoke this directly from the orchestrator or main loop; instead dispatch the `planner` agent (always Opus), which runs this skill in isolation. Describes how the planner decomposes an approved spec/PRD into a validated execution-plan.json (atomic tasks, locked tests, severity tiers, adversarial flags, scope_paths) consumed by orchestrating-delivery.

API & Backend Listed

authoring-rules

Meta-skill para criar e editar rules do Claude Code (.claude/rules/*.md). Use quando for criar uma nova rule no projeto, adicionar pattern/gotcha/convention a uma rule existente, ou revisar rules.

canonical-critical-classes

Load when ATTACKING (adversary) or VERIFYING (compliance) an implementation. Carries the canonical taxonomy of critical failure classes — the known killers from the operator's systems-primitives model — plus the irreversibility-first criticality ranking. Use it to hunt the bug that makes the system UNVIABLE, never to fill a finding quota. Role-neutral: HOW each role acts lives in that agent's prompt.

Code & Development Listed

committing-changes

Analisa mudancas, cria commit semantico (Conventional Commits) e faz push. Para commit avulso fora do pipeline /ship — quando voce so quer commitar uma mudanca sem PR/review/docs.

distilling-learnings

Reads the transient findings.md, applies the durability test, then routes each durable insight by blast-radius to the right repo-committed destination — project pattern → repo memory (.claude/memory/<name>.md + .claude/memory/MEMORY.md index), law of one folder → that folder's nested CLAUDE.md + root router row, global convention → .claude/kaizen.md proposal. No learnings.md is written. Use when the harvester runs after recording-findings completes; never during active implementation.

Code & Development Listed

initializing-projects

Installs (vendors) the Claude Harness core into a project's .claude/ so the pipeline works locally and in cloud routines. Resolves the source portably (local path or git URL), copies agents/skills/rules/CLAUDE.md/settings.json, seeds repo-relative memory, stamps .harness-version, and merges idempotently so re-running updates without clobbering project content. Use to onboard a project or to update its vendored harness.

Data & Documents Listed

measuring-cost

Use at the end of a delivery (invoked by the harvester) to report the API-equivalent cost of the session plus the weekly Claude Code consumption trend. Wraps the `ccusage` tool over the local transcript JSONL; fail-soft when ccusage is unreachable (offline / cloud headless).

orchestrating-delivery

Conducts the LIGHT and FULL delivery loop of the Claude Harness — runs spec, plan, the per-task executor/compliance/adversary/sniper/gates cycle, final dual review, demo, and harvest. Dispatches a fresh subagent per role and curates layered ICM context for each; never writes code itself. Invoked by triaging-requests for LIGHT/FULL (QUICK runs inline and never reaches this skill).

proposing-improvements

Scans the transient findings.md for systemic patterns that indicate an agent or skill in the harness could be improved, and appends proposals (never auto-applies them) to kaizen.md. Because findings.md is deleted at harvest end, kaizen.md is the durable cross-run signal — check it for precedent. Use when the harvester runs after distilling-learnings completes.

recording-findings

Consolidates executor, compliance, adversary, and sniper finding blocks from a completed feature run into the transient findings.md buffer at the project root. findings.md is ephemeral — the input to distilling-learnings, deleted by the harvester at the end of the run; durable audit lives in git. Use when the harvester agent runs after final dual review — never during active implementation.

releasing-versions

Pipeline de release versionado via PR — abre PR chore/release-X.Y.Z (bump + CHANGELOG), aguarda merge, e ai cria tag + GitHub Release. Use quando voce tem mudancas merged em main prontas pra virar versao.

surveying-codebase

Surveys an onboarded project's codebase for durable, reusable knowledge (existing helpers to reuse, implicit conventions, architectural patterns, anti-patterns/gotchas), applies the durability test, and routes each insight by blast-radius to the right repo-committed destination — the same routing as distilling-learnings, but sourced from the code itself, not a run's findings.md. Use when a legacy/existing project enters the harness with empty memory (.claude/memory/MEMORY.md + unfilled nested CLAUDE.md), via /surveying-codebase or when orchestrating-delivery Phase 0 finds the memory cold; one-time / on-demand, re-run when the codebase changes substantially. No learnings.md is written.

triaging-requests

Classifies the operator's request into QUICK, LIGHT, or FULL delivery mode — or no ceremony at all — and dispatches accordingly. Runs on the first interaction of every session before any implementation begins.

updating-harness

Use to install or update the Claude Harness in the CURRENT project from its source repo — the source URL is baked in, the operator never pastes it. Detects install-vs-update, pins to the latest GitHub release tag, reports what changed, and re-vendors via vendor-core without clobbering project memory/kaizen/settings. Call it in any repo to onboard or sync the harness after a new release.