etc

Autonomous harness-cleanup orchestrator (Boy Scout rule + broken-windows). Surveys the repo, selects flawless-only cleanup, performs it in an ISOLATED git worktree cut from main, verifies the harness gates green, runs a mechanical pre-PR boundary check, and opens a pull request — never touching the operator's working tree or build. Two modes: interactive `/janitor` and hands-off `/janitor --autonomous` (ZERO prompts, for an operator-supplied scheduler). Janitor submits; a human merges. It never pushes origin/main, never self-merges, never bypasses git hooks (`--no-verify`), and never sets dangerouslyDisableSandbox.

Socratic architecture-design loop that turns a finalized spec.md into an implementation-ready design.md plus 1-N ADRs through questioning, codebase research, gray-area resolution, and iterative section drafting. Runs after /spec, before /build.

Full pipeline conductor — validate, decompose recursively, plan waves, dispatch each wave via Agent-tool subagent calls, verify. The single entry point for building any feature from spec to working code.

Bootstrap any repository into a state where the ETC harness can operate on it. Orchestrates technical scaffolding (via project-bootstrapper), interactive DOMAIN.md creation, tiered docs skeleton, and starter role manifests.

In-flight architecture-rule capture and sweep. A human states a rule mid-build; the rule lands in the machine baseline, the repo is swept for violations and fixed via file-isolated agents, and the rule joins the conformance checker so it is enforced going forward. Use when you notice an architectural rule the codebase should follow but does not yet enforce.

Socratic specification loop that generates implementation-ready PRDs through questioning, research, and iterative refinement. Output is ready for /implement.

Strategic roadmap planning agent that demands crystal-clear target state before planning. Works with Discovery skill. Refuses to proceed with vague PRDs. Use for migrations, platform changes, or any journey from current state to well-defined target state.

Socratic design phase wrapping impeccable (Apache 2.0). Dispatches /impeccable init via the Skill tool for Socratic capture of PRODUCT.md + DESIGN.md, then post-processes the result to write etc-native artifacts — gray-areas-design.md, design-tokens.json, component-specs.md, and the state.yaml.design_phase block. Runs on the design side of the (design | strategy) mid-funnel branch, before /spec. First phase to allocate features/F<NNN>; /spec and /architect inherit feature_id from state.yaml.

User-invokable cross-project lesson capture. Records process failures (wasted time, manual workarounds, missing standards) that should propagate back to the etc harness as new rules, hooks, skill steps, or standards. Emits a structured `📬 Harness feedback` block; routes directly to /spec when invoked inside the etc repo. Distinct from /postmortem, which handles per-project shipped bugs.

Trace escaped bugs to root cause and append prevention rules to the antipatterns learning loop. Typically invoked after /hotfix to retrospect on an incident, but also runs standalone on any escaped bug.

Archaeological research agent for deep system discovery. Investigates codebases, Salesforce orgs, documentation, and data exports to understand what's ACTUALLY happening vs what's documented. Identifies missing dependencies and access needed for deeper investigation. Use for migrations, due diligence, system understanding, or when documentation doesn't match reality.

Non-interactive three-layer metrics report. Reads git tags (process), value-hypothesis.yaml files (outcome), and .etc_sdlc/telemetry.db (cost), then emits a markdown report to stdout with the headline "% hypothesis-validated" broken down by author role.

Recursively decompose complex tasks into implementable subtasks. Reads a PRD or task, scores complexity, and breaks down anything too large for a single agent session.

Save current session state to disk before compaction or session end. Ensures continuity across context resets.

Chief Efficiency Officer operator commands. Review proposals queued by the Stop-hook reflection layer (F019), read today's efficiency report, query operator velocity baseline, mute threshold-push interrupts. All observations are evidence-based — every proposal cites data points and operator baseline; no hallucinated narrative.

Incident response lane — file an incident, dispatch a constrained subagent, suggest postmortem afterward. Use when production is broken and normal /spec→/build ceremony is too slow.

SME-facing skill for capturing customer journeys. Walks a domain expert through 6 plain-English Socratic questions (plus one optional emotion question), refines their answers, and writes a structured journey artifact to docs/mvp/journeys/J-NNN-<slug>.md. Pairs with /spec via journey_refs. Designed for non-technical experts who LIVE the journey they're describing.

Personal engineering coach and strategic learning agent. Analyze development sessions to extract workflow improvements, identify software engineering principles (missed or applied well), and surface advanced architectural insights. Builds a personal engineering playbook over time.

Pull tickets from Linear, generate PRDs, run through SDLC pipeline, create PRs or reject back to source with questions.

View and manage task status, find next ready task, show dependency tree. Native replacement for Taskmaster.

Spec-based implementation workflow with scale-adaptive planning. Takes a PRD, validates it, decomposes into tasks, dispatches to subagents, and orchestrates the build.