adr-writing
01Skill Claude CodeCodex
Part of orc
Author and update Architecture Decision Records (ADRs) — the durable record of a decision and its trade-offs, in docs/adr/NNNN-.md. Use to lock in an architectural decision or to supersede an ADR.
Skill Claude CodeCodex
Part of orc
Author and update Architecture Decision Records (ADRs) — the durable record of a decision and its trade-offs, in docs/adr/NNNN-.md. Use to lock in an architectural decision or to supersede an ADR.
Skill Claude CodeCodex
Part of orc
Browser automation CLI for AI agents; use for web tasks - navigate, click, fill forms, screenshot, scrape, test web/Electron apps.
Skill Claude CodeCodex
Part of orc
Implement Clean, Hexagonal (Ports & Adapters), and Domain-Driven architecture patterns. Use when designing service layers, refactoring monoliths into bounded contexts, or fixing layer dependency cycles.
Skill Claude CodeCodex
Part of orc
The canonical browser-QA protocol for web changes — env attach, the driver gate (agent-browser headless vs Claude-in-Chrome live), the validator dispatch contract, and the chrome-mode evidence packet. Use when running browser QA on a web change; /orc:qa Phase 4 and /orc:flow Phase 6 delegate here.
Skill Claude CodeCodex
Part of orc
The orc callout palette — emoji-header blockquotes in conversation, GitHub-flavored [!TYPE] form for GitHub-bound output. Use when about to add an insight, caution, gate, preview, or danger block to the conversation or to a PR/doc.
Skill Claude CodeCodex
Part of orc
Ultra-compressed, signal-only pull request descriptions. Use when opening a PR or when the user says "write a PR description", "PR body", "draft the PR", or invokes /caveman-pr.
Skill Claude CodeCodex
Part of orc
Ultra-compressed code review comments — one line per finding: location, problem, fix. Use when the user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review.
Skill Claude CodeCodex
Part of orc
The canonical route-on-verdict protocol for a red CI diagnosis — fixable/flake/infra/needs-debug handling, the single-render rule, and the fix-then-re-watch loop. Use after orc-ci-investigator returns; /orc:ci Phase 3 and /orc:flow's post-open CI gate delegate here.
Skill Claude CodeCodex
Part of orc
Use when discovering or navigating a codebase before planning, implementing, debugging, or refactoring — prefer a Graphify code-graph query over broad Glob/Grep/Read to cut token cost, with automatic fallback to grep when Graphify is absent, stale, or unhealthy.
Skill Claude CodeCodex
Part of orc
Shared vocabulary for designing deep modules — seam, adapter, depth, leverage, locality. Use when designing or reshaping a module's interface, deciding where a seam goes, making code more testable or AI-navigable, or when another orc skill or agent needs the deep-module vocabulary.
Skill Claude CodeCodex
Part of orc
Audit, survey, and upgrade project dependencies safely — majors escalated, never auto-applied. Use when auditing dependencies for vulnerabilities, checking outdated packages, bumping a dependency, or when /orc:deps is invoked.
Skill Claude CodeCodex
Part of orc
Dispatch parallel subagents with focused, self-contained briefs — each gets exactly the context it needs, never your session history. Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.
Skill Claude CodeCodex
Part of orc
Shared scaffolding for numbered design/spec docs — outline, NNNN- numbering, review gates, doc-type map (PRD/TRD/RFC/ADR/postmortem). Referenced by orc:prd/trd/rfc/adr-writing + postmortem.
Skill Claude CodeCodex
Docker expert — image optimization, security hardening, multi-stage builds, orchestration, production deployment. Use when writing or reviewing Dockerfiles, Compose, or container deploys.
Skill Claude CodeCodex
Diátaxis documentation expert. Use when writing high-quality software documentation guided by the Diátaxis framework — tutorials, how-tos, reference, and explanation.
Skill Claude CodeCodex
Maintain a project's ubiquitous language and decision record against CONTEXT.md. Use when defining or disputing domain terminology, when a design session resolves a term that belongs in CONTEXT.md, or when a decision made mid-session passes the ADR gate.
Skill Claude CodeCodex
Provision a fast, reproducible dev environment for QA or standalone use — healthcheck-gated boot, reuse/teardown rules, host-mode fallback. Protocol for /orc:env, /orc:qa Phase 4, /orc:flow Phase 6, and the orc-env-provisioner agent.
Skill Claude CodeCodex
Error handling patterns across languages — exceptions, Result types, propagation, graceful degradation. Use when implementing error handling, designing APIs, or improving reliability.
Skill Claude CodeCodex
Deliver a QA/evidence packet to a tracker or keep it local, behind an always-ask preview gate. Protocol for /orc:qa Phase 6, /orc:evidence, and any evidence-delivery step.
Skill Claude CodeCodex
Execute a written implementation plan batch-by-batch — load it, review critically, implement task by task, and stop for review between batches. Use when you have a written implementation plan to execute in a separate session with review checkpoints.
Skill Claude CodeCodex
Guide the completion of a development branch by presenting structured options for merge, PR, or cleanup. Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
Skill Claude CodeCodex
Per-phase playbooks for /orc:flow Phases 2–9, loaded one at a time as the flow reaches each phase. Use only from /orc:flow — Read the single references/PHASE-N-.md for the phase being entered, never all of them.
Skill Claude CodeCodex
GitHub CLI (gh) reference for repos, issues, PRs, Actions, releases, gists, projects, codespaces, and the API. Use for any gh command or GitHub operation from the terminal.
Skill Claude CodeCodex
Advanced Git workflows - rebase, cherry-pick, bisect, worktrees, reflog - for clean history and recovery. Use when managing complex histories, collaborating on branches, or troubleshooting a repo.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: