AlperenEvci

audit

Audit a repository's Claude Code development harness, including optional Codex plugin/CLI transport, AGENTS.md, CLAUDE.md, skills, subagents, permissions, context strategy, artifacts, routing, and verification gates. Read-only and explicitly invoked.

session

Dispatch, list, inspect, and tear down harness agent sessions. Turns a capability tier into the exact launch command that enforces it, reads the .ai/bus/ return channel, and sweeps background sessions the repository left running. Requires a Standard or Fleet harness. Explicitly invoked.

setup

Create, adopt, or upgrade a project-specific Claude Code development harness in either a blank project folder or an existing repository. Greenfield mode interviews the operator about product intent, scope, stack, architecture, and safety before generating durable project context. Existing-project mode uses evidence-based inspection. Both modes support official Codex plugin, direct Codex CLI, or Claude-only execution, deterministic staging, validation, and conflict-aware installation. Writes project files and must be invoked explicitly.

agent

Synthesize a bounded agent for a need the harness did not foresee. Turns a stated need into a capability-tiered agent definition, emits it inline for one-off use, and can promote it into .claude/agents/ as a separate reviewed step. Authority comes from the tier, never from the request. Requires a Standard or Fleet harness. Explicitly invoked.

spec

Turn an accepted decision into a self-contained implementation contract under .ai/specs/. The contract carries goal, scope, out-of-scope, constraints, acceptance criteria, and the project's exact verification commands, so a delegate can execute it without the conversation that produced it. Writes a project file and must be invoked explicitly.

Testing & QA Listed

harness-fixture-smoke-test

Exercise the setup pipeline end to end against a disposable fixture repository outside this project, to prove that inspection, rendering, validation, and dry-run installation still work together. Invoke explicitly after changing templates, the renderer, the validator, or the installer.

harness-release-bump

Perform a coordinated version bump of the development-harness plugin across the manifest, changelog, and any version-bearing documentation, then run the full gate. Invoke explicitly when cutting a new plugin release.