ISA

Scaffold an ISA from your prompt: it preserves your stated goal verbatim, derives Vision, Out of Scope, and Constraints, then decomposes the work into atomic claims where each claim names exactly one binary probe such as a bash command, test, or curl check.

An Ideal State Artifact is a single Markdown document with seventeen fixed sections that pins what finished means for a task or project. It combines the goal, falsifiable claims, a test strategy table, and decision and learning logs so completion is proven by probes rather than asserted.

Use the Seed workflow on the repo path. It reads the README, package.json, configs, recent commits, and any PRD-shaped files to draft a substantial-grade project ISA, marking it review-required rather than inventing content the sources do not support.

Yes. Scaffold can extract a feature slice as an ephemeral file containing the relevant claims with stable IDs, and Reconcile later merges checkmarks, verification stubs, decisions, and learning entries back into the master ISA deterministically, aborting on unknown IDs.

Use Grill when the idea is too unformed to draft a spec; it discovers structure through checkpointed questions and a pre-mortem. Use Interview when an ISA already exists but has thin sections that need deepening with targeted questions.

Common hard failures include missing required sections for the work's substance level, zero anti-claims, leaf claims with no Test Strategy probe row, non-empty fog sections at close, claim ID renumbering, or a narrative changelog section, which is banned because git is the change record.