/**
 * `aidlc templates` — what phases a template runs, and what each one must produce.
 *
 * **Why this command exists.** The skills tell an agent to create an instance
 * directly when the CLI is not driving, including writing each `phase-<name>.yaml`
 * with the template's `required_artifacts`. Until this command, that data existed
 * only inside `node_modules/@rasensio/aidlc-content/templates/`: there was no
 * `templates` command, `aidlc init` wrote no `.aidlc/templates/`, and the
 * instruction itself said `- name: <artifact>.md` with no source for the real
 * names. The only behaviour that instruction could produce was guessing, and on
 * the first real-project run it produced exactly that — three artifacts written
 * into phase files that `quick-feature` does not require (first-run-gaps/AC-19…AC-25).
 *
 * Reads the content package and `.aidlc/templates/`, and nothing else: no
 * instance, no claim, no state (NFR-3). Asking what a template requires must work
 * before there is anything to ask about.
 *
 * Templates are printed RESOLVED, never as written on disk. A template with
 * `extends:` declares its differences from its parent, so the raw file for one
 * shows an empty phase list — which is precisely the wrong answer to "what must I
 * write".
 *
 * Requirements: first-run-gaps/AC-19, AC-20, AC-21, AC-22, AC-23, AC-24
 */
import type { Command } from 'commander';
export declare function registerTemplates(program: Command): void;
//# sourceMappingURL=templates.d.ts.map