#!/usr/bin/env node
/**
 * @docsbook/specify — CLI entry point
 *
 * The CLI is the DETERMINISTIC half of spec-driven development. The four
 * generative entry points — code→spec, spec→code, spec-driven reflexion, and
 * conformance judgment — are AI tasks; they live in the `specify` skill, which
 * an agent (Claude Code, Cursor, Codex) runs. The CLI does what does NOT need a
 * model: validate spec structure, build the trigger↔code-graph coverage map,
 * and print the dossier/guide the skill reasons over.
 *
 * Subcommands:
 *   specify new "<idea>"             scaffold a brand-new spec from an idea (greenfield)
 *   specify spec validate <dir>      validate spec structure (deterministic)
 *   specify verify <spec> [--graph]  coverage map: spec triggers ↔ graphify nodes
 *   specify reverse <code-dir>       print the code→spec dossier for the AI skill
 *   specify build <spec-dir>         print the spec→code dossier for the AI skill
 *   specify reflect                  print the spec-driven reflexion guide
 *   specify install [dir]            install skills + commands into an AI tool
 *
 * All commands output JSON to stdout.
 */
export {};
//# sourceMappingURL=cli.d.ts.map