Commander Adapter Cockpit

Mirror rule: use this page to choose and review adapters. If this file conflicts with the command-adapter registry, the operating model, a draft adapter doc, installed skills, repo instructions, or Kalen's current direction, those sources win.

Active Adapter Directory

Every useful candidate is now an active command-layer route. Some routes defer operational behavior to installed skills, but they are still available from the command adapter front door.

Theme	Adapter / Alias	Use It When	Authority / Stop Rule
Framing And Source Truth
Framing	`/grill` Alias: grill-me, grilling	Pressure-test an idea, plan, design, roadmap, or adapter candidate before action.	Doc-only adapter. Stop before implementation, durable artifacts, publishing, or connector writes unless approved.
Framing	`/grill-source` Alias: grill-with-docs	Challenge a plan against repo docs, source truth, domain language, code, and durable decisions.	CKF, repo rules, and source files outrank the adapter. Stop before edits or accepting unsupported claims.
Framing	`/zoom-out`	You are stuck in local details and need the system one level up plus the next best question.	Use for orientation. Stop before architecture commitment or implementation without reviewed plan.
Framing	`/map-reduce`	A broad repo, corpus, stale guidance set, or source-fidelity surface needs explicit coverage.	Active route; operational authority belongs to the installed `map-reduce` skill and Safe Lane rules.
Framing	`/wayfinder`	Work is too large for one session and needs a shared map, frontier, and next safe move.	Active route in `active-adapter-routes.md`. Do not create or mutate trackers without approval.
Setup, Handoff, And Governance
Setup	`/project-profile` Alias: setup-matt-pocock-skills, triage	A repo needs startup docs, source truth, validation, safe writes, install state, and host boundaries captured.	Reuse existing `AGENTS.md`, README, and startup docs first. Do not create duplicate profiles without approval.
Handoff	`/delegation-brief`	A subagent, Linear issue, or future agent needs a durable instruction packet.	Read-only drafting unless writing handoff files, Linear issues, or connector updates is approved.
Handoff	`/handoff`	Current work needs restartable state, source refs, decisions, remaining work, and stop rules.	Ask before writing durable handoff files or updating trackers. Use closeout skills when they trigger.
Governance	`/skill-lifecycle` Alias: general/personal skill triage	A behavior may need to be kept, merged, promoted, retired, rejected, or archived.	Recommend freely. Ask before registry edits, archives, installs, or promotion.
Planning, Translation, And Execution
Planning	`/spec-prd` Alias: to-spec	Approved context needs to become a scoped PRD, product spec, or work spec.	Ask before creating durable PRD files, Notion pages, or Linear issues.
Planning	`/slice-to-linear` Alias: to-tickets, to-issues	An approved plan needs vertical issue slices, blockers, and acceptance criteria.	Drafts are read-only. Ask before creating, updating, or linking live Linear issues.
Planning	`/decision-tree`	A real choice under uncertainty needs alternatives, thresholds, outcomes, and next learning action.	Do not commit to a decision, create tasks, or record decisions without approval.
Execution	`context-first-engineering` Alias: implement	The work should move from plan to implementation with orientation, review, and validation gates.	Active route through the installed lifecycle skill, not a standalone command adapter.
Execution	`/prototype-decision` Alias: prototype	The smallest prototype can answer a decision question faster than discussion.	Ask before code edits, app creation, commits, or publishing.
Execution	`/diagnose` Alias: diagnosing-bugs	A failure needs reproduction, hypotheses, and repair.	Active route; operational authority belongs to installed debugging and failure-loop skills.
Execution	`/tdd`	A behavior slice should be built test-first.	Active route; operational authority belongs to installed TDD and repo test guidance.
Analysis, Modeling, And Communication
Analysis	`/induce`	Messy evidence, notes, interviews, or research need pattern finding, caveats, and next learning actions.	Do not convert weak associations into claims. Use `/grill-source` when trust matters.
Analysis	`/deduce`	A conclusion must be tested against premises, rules, definitions, exceptions, or governance claims.	Stop before editing policy, recording exceptions, approving controls, or changing code.
Analysis	`/architecture-review` Alias: improve-codebase-architecture	An evidence-backed architecture candidate report is needed before building or refactoring.	Read-only unless writing review artifacts, code, or decision records is approved.
Analysis	`review` / Safe Lane Review Alias: code-review	A trusted PR-style, source-fidelity, regression, or release review is needed.	Active route through installed review skills; findings must be verified before changes.
Research	`/research`	A question needs primary-source discipline, contradiction handling, and decision relevance.	Use current external research only when needed. Cite sources when external sources shape the answer.
Modeling	`/domain-model` Alias: domain-modeling, codebase-design	Domain vocabulary, entities, workflows, or codebase design language need clarification.	Do not rename code, rewrite docs, or assert domain authority without source evidence and approval.
Communication	`/pyramid`	Formed analysis needs answer-first executive communication.	Ask before sending, publishing, creating files, or recording recommendations.
Routing And Intake
Routing	`command-adapter-operator` Alias: ask-matt	You know the work but do not know which adapter route fits.	The operator reads the registry and selected docs on demand. It is the only live skill for the adapter layer.
Intake	`command adapter intake`	A new external, custom, general, or personal skill pattern may be worth adapting.	Use intake first. Do not inflate the live skill set or write registry changes without approval.

Recommended Flows

Use flows when the work spans more than one adapter. Stop before writes or publication unless the user explicitly approves the action.

Thinking To Recommendation

/induce for messy evidence.
/deduce to test rule-based claims.
/decision-tree for the choice.
/pyramid for executive communication.

Plan To Execution

/grill to pressure-test intent.
/grill-source to check source truth.
context-first-engineering for Mini or Full ExecPlan.
/slice-to-linear only after the plan is approved.

Broad Review

/zoom-out for system framing.
/grill-source for authority and source conflicts.
map-reduce live skill for explicit coverage.
/handoff when restartability matters.

Source Truth And Safety

The cockpit is intentionally lower authority than source-managed Markdown and live skills.

Authority Order

Kalen's current instruction.
Nearest AGENTS.md and repo-specific rules.
CKF routing, owning repo docs, and canonical Markdown.
Installed live skills and reviewed runtime docs for operational behavior.
Active command adapter docs.
This HTML mirror.

Do Not Do From This Page

Install or promote skills.
Change runtime configuration.
Create live Linear issues.
Publish to Quantum Web.
Write registry/docs changes.
Treat source skill patterns as Codex policy.

Canonical Local Sources

command-adapters/command-adapter-registry.md
command-adapters/drafts/*.md
command-adapters/README.md
knowledge-vault/20-evergreen/agent-systems/command-adapter-operating-model.md

Next Maintenance Improvement

Generate this page from the registry and adapter docs.
Stamp registry commit, upstream release, and source file checksums.
Add a smoke check for every local source link and anchor.
Keep Quantum Web as internal-only until a redaction checklist passes.

Upstream Matt Pocock Skills Snapshot

Latest checked release: mattpocock/skills v1.1.0, published 2026-07-08. Every upstream behavior below has an active route, stronger local skill route, or explicit operator/intake path.

Skill	Disposition For Command Layer	Why
`ask-matt`	`command-adapter-operator`	Router pattern is useful, but the local operator owns routing.
`grill-me`, `grilling`	`/grill`	Core pressure-test behavior is active.
`grill-with-docs`	`/grill-source`	Source-fidelity challenge maps directly to local CKF/repo rules.
`wayfinder`	`/wayfinder`	Now active for huge cross-session planning, map/frontier capture, and next safe move.
`to-spec`	`/spec-prd`	Spec language is active inside one stronger PRD/spec route.
`to-tickets`	`/slice-to-linear`	Tracer-bullet tickets and blockers are the same operational lane.
`implement`	`context-first-engineering`	Implementation routes through orientation, plan, review, and validation gates.
`code-review`	`review` / Safe Lane Review	Two-axis review is useful, but live review skills own trusted behavior.
`research`	`/research`	Primary-source discipline is active with local fallback design.
`prototype`	`/prototype-decision`	Active when prototype answers a decision rather than becomes product code.
`diagnosing-bugs`	`/diagnose`	Active route; installed debugging and failure-loop skills own operational behavior.
`tdd`	`/tdd`	Active route; repo test rules and installed TDD skills own operational behavior.
`domain-modeling`, `codebase-design`	`/domain-model`	Active vocabulary and source-heavy design review route.
`improve-codebase-architecture`	`/architecture-review`	Architecture candidate report is active; avoid automatic refactor shopping lists.
`resolving-merge-conflicts`	`/diagnose`, `/project-profile`	Available through reproduce-first repair plus repo Git rules and validation.
`triage`, `setup-matt-pocock-skills`	`/project-profile`, `/skill-lifecycle`	Setup and governance contracts are active while Codex authority still comes from AGENTS, CKF, and repo rules.
`handoff`, `claude-handoff`	`/handoff`	Active restart-context route; Claude-specific behavior is reference only unless requested.
`teach`	`/pyramid` or intake	Explanation and teaching briefs use existing communication routes before a new adapter.
`writing-great-skills`	`/skill-lifecycle`, `codex-skill-author`	Active for skill-quality review; live skill authoring rules outrank upstream wording.
`loop-me`	`/diagnose` or review loop	Iteration behavior is available through failure-loop, diagnose, and review workflows.
`wizard`	Command adapter intake	In-progress upstream pattern; intake first, then promote only with local evidence.
`writing-beats`, `writing-fragments`, `writing-shape`	`house-style-system`, writing intake	Writing patterns route through local writing skills, not command adapter defaults.
`git-guardrails-claude-code`	`/project-profile` and repo Git rules	Setup/governance reference; local Git policy and approvals remain authoritative.
`migrate-to-shoehorn`, `scaffold-exercises`, `setup-pre-commit`	Intake or `/project-profile`	Setup utilities are available by request; no default mutation without approval.
`edit-article`, `obsidian-vault`	Local writing and CKF routing skills	Personal upstream patterns route through Kalen's local writing and knowledge systems.
Deprecated upstream skills: `design-an-interface`, `qa`, `request-refactor-plan`, `ubiquitous-language`	`/prototype-decision`, `/domain-model`, `/architecture-review`, review	Kept as reference only; use stronger active routes instead of reviving old names.
General/personal skills	Command adapter intake or `/skill-lifecycle`	Available for triage, merge, rejection, or future active route creation.

Production Notes

This cockpit is prepared for internal Quantum Web publishing through the managed artifact workflow after hosted upsert validation. The page remains a mirror of source-managed Markdown.

Acceptance Criteria

The first section is a compact, theme-grouped active adapter directory.
Former candidates and overlap routes are listed as active command-layer routes.
Upstream Matt Pocock dispositions map to active routes or explicit operator/intake handling.
Internal-only and mirror-only boundaries are visible in the first viewport.

Publish Gate

Use the Quantum Web managed artifact upsert path.
Preserve a stable slug while storing a versioned artifact file.
Validate the hosted file separately from local browser review.
Commit and push source changes after local and live validation pass.

Built as a single-file internal HTML artifact in command-adapters/visuals/commander-adapter-cockpit.html. Canonical operating content remains in Markdown.