spec-converge

# /spec-converge **Audience:** the instar-developing agent. End users do not invoke this. Throughout this document, "the agent" refers to the instar-developing agent running the skill. --- ## What this skill does Takes a spec file, runs multiple parallel reviewers against it, updates the spec to address their findings, runs another round, and repeats until convergence. Produces a final converged spec and a comprehensive human-readable report. The purpose is to catch architectural, security, adversarial, scalability, and integration issues BEFORE code is written, not after. The single-reviewer pattern used by `/instar-dev`'s existing second-pass step has proven too narrow in practice — a four-reviewer parallel audit on the integrated-being ledger PR surfaced 14 serious issues that a single reviewer had missed. This skill bakes that multi-angle pattern in as the structural default for any substantive instar-dev work. ## When it runs Before `/instar-dev` touches any instar source, the change's spec must pass through this skill. `/instar-dev`'s pre-commit hook refuses work unless: 1. The spec file has a `review-convergence: <timestamp>` entry in its frontmatter, written by this skill on successful convergence. 2. The spec file has an `approved: true` entry in its frontmatter, written by the user after reading the convergence report. Both tags must be present. Without them, `/instar-dev` is blocked. ## Input One argument: the path to the spec file, relative to the insta...