main

Install Valence — Spec-driven Claude Code workflow with adversarial review, QA agents, and orchestrated builds

Opus-orchestrated adversarial review with cost/benefit analysis. Launches ar-o, ar-k, ar-glm5 in parallel, synthesizes findings. Use for validating design docs before /breakdown.

Global architecture spec. Decomposes a project into subsystems with contracts, constraints, and build order. Produces a living spec that tracks project state. Use after /arm or with a clear brief for greenfield projects.

Crystallize fuzzy thoughts into a solid brief. Extracts requirements, constraints, style, key concepts. Use before /design when starting from vague ideas.

Debugging protocol. Triage, root-cause, and fix bugs. Creates tickets in PROCESS_DOCS/tickets/ with YAML manifest tracker. Use for known bugs, regressions, or unexpected behavior.

Implementation workflow. Orchestrates an agent team to implement execution breakdowns. Use after /breakdown and /pmatch validation.

Post-implementation cleanup using the code-simplifier plugin.

Pattern matching validation. Compares source-of-truth against target to check alignment. Lighter than /ar. Use to validate plans against designs, or implementations against plans.

Backend QA audit. Audits against backend_styleguide.md (API routes, data access, security). Migrates __tests__ to tests_[module].

Documentation QA audit. Checks for stale docs and code/doc drift.

Frontend QA audit against frontend_styleguide.md. Migrates __tests__ to tests_[module]. Checks Tailwind compliance, component patterns, resource cleanup, security, accessibility.

Solution design for features, subsystems, or complex changes. First principles analysis, research, iterative discussion, formal design document. Use after /arm or /arch, or standalone with a clear brief.

Use when submitting a skillset to skillsets.cc. Qualitative review of primitives, safety scan, and workflow artifact verification. Run from the reference repo where the skillset was used in production.

Walk through the full skillsets.cc submission process. Guides scaffold, validation, and submission of a new skillset.

Use when submitting a skillset to skillsets.cc. Qualitative review of primitives, safety scan, and workflow artifact verification. Run from the reference repo where the skillset was used in production.

Execution breakdown workflow. Transforms approved designs into detailed task breakdowns for build agents. Use after /ar approval.