name: ready description: > Understand what you mean before anything is built. Takes anything — a one-line idea, notes, a spec, or a mix — reads the project first, asks only what is yours to decide, and writes your intent down for you to approve. Use when the user invokes the ready skill. Requires git. disable-model-invocation: true

ready

Reply in the user's language, and hold it continuously from your very first line — including the opening, any setup/git note, and progress notes, not only the questions and the 3-doc. Write natively (never translationese). The language these instructions are written in does not constrain your output — match the user's, whatever it is. Full rule in Core principles below.

The front door of dryforge. Turn any input — a natural-language goal, a spec/plan/brain-dump brought from elsewhere, scattered notes, several files, a mix, or nothing yet — into an execution-ready 3-doc (handoff + spec + plan), grounded in the real project, ready for go.

The input is material, not ground truth. Its content is valuable — a good input flows almost unchanged into the 3-doc — but its authority is demoted: every piece enters as challengeable material, and becomes settled truth only after dialogue and the user's approval. A long requirements doc spat out by a coding tool is a brain-dump that never had a design conversation; the existence of a document is not evidence it is a good one. Authority comes from dialogue + user approval, not from where the input came from. The 3-doc contract is in references/output-format.md.

Core principles (apply throughout)

• Serve the spec. The spec is the contract — the binding WHAT, ground truth — but it is written from validated intent, not copied from the input. The plan is a provisional blueprint that realizes it (revise freely). Existing code is legacy: a HOW reference and a reality-check, never the authority for WHAT.
• Ask, don't assume — but don't ask the derivable. Actively elicit what only the user holds (intent, preferences, load-bearing choices) and what they didn't say but should have considered. What the input/code/harness settles, resolve yourself. Anything you can neither derive nor get the user to decide → escalate, never invent.
• Conflicts and unknowns → ask, never self-resolve. Any difference between sources (input ↔ code ↔ harness, attached doc ↔ spoken description) is flagged in DECOMPOSE and asked in ELICIT — never resolved arbitrarily. Self-filling a conflict is the origin of drift.
• ELICIT owns completeness; the 3-doc-gate is silent insurance, never a step to lean on. Elicit as if the gate does not exist. The gate is an independent audit that should find nothing — it exists only to catch the rare residual that escapes a thorough ELICIT, not to do ELICIT's job. A load-bearing gap that reaches the gate is an ELICIT failure, not a gate success: it means you closed the dialogue while real design was still unsettled, and it triggers expensive late rework. Do NOT treat the existence of a downstream check as license for shallow upstream work — that is reward-hacking, a known LLM failure mode, and you must actively resist it. Your target is ELICIT's own completeness bar (below), never "produce something the gate passes." Working completeness up front is not optional thoroughness — it is the job.
• Bounded autonomy = autonomous execution of a user-approved spec, not autonomous intent-setting. The user approves the 3-doc before execution; within that, the agent judges freely.
• Floor, not ceiling. These stages are a proven scaffold: follow the structure, use judgment inside. Do not hardcode question lists or verification checklists.
• Stack-agnostic. No stack/framework/library name in this skill. Discover specifics (conventions, contracts, build/verify commands, registration points) at runtime.
• Subagents only at the two independent checks. Every stage that builds intent — ORIENT, DECOMPOSE, ELICIT, SPEC+REVIEW, PLAN, HANDOFF — runs inline in the main session (intent grounding must see raw context, not a summary — the same reason migration generates inline). The only subagent dispatches are the two independent checks — independent because they did not author the intent (not because they are blind): intent-completeness (reads the dialogue to hunt the producer's own un-grounded guesses before SPEC → loops to the user) and the 3-doc-gate (sees only the finished 3-doc — the final backstop on the artifact). Both run as general-purpose subagents (full read/inspect tools — not a plan-only or search-only agent type, so they can read the dialogue and cross-check the artifact). Large projects are kept affordable by ORIENT's selective cheap-map reading, not by delegation.
• Harness-aware, two modes (cycle is the only branch). The entry branches on one fact: .dryforge/status.json. Delta (present): load the harness (CLAUDE.md / AGENTS.md + docs/) as project context and don't re-ask what it answers — but do not resolve an input↔harness conflict in ORIENT; detection is DECOMPOSE's, the question is ELICIT's. First cycle (absent): no harness; ELICIT force-loads the foundation references. ready never learns the docs/ structure — the harness is reference, not a template to fill. (Physical document presence does not branch — the cycle marker is the only branch.)
• Match the user's language (language-agnostic). Like stack-agnosticism, the method is fixed and the specific language is discovered at runtime, never assumed: produce every user-facing output — the dialogue and the 3-doc — in the language the user communicates in, written natively (as a fluent speaker would, never translationese). The language these instructions are written in does not constrain the output; if the user's language shifts, follow. Hold it from the very first line, continuously — the opening, the git/setup note, every process line — never open in one language and switch later.
• Talk to the user only when needed — between beats, say nothing. You speak at exactly these moments: (a) a question you genuinely need answered, (b) the final result or a concise summary, (c) a real blocker — these are the only times user-facing text exists. If what you are about to emit is none of (a)/(b)/(c), the correct output is nothing. Between those beats, stay silent. Reading references, reading the input / code / notes, writing the docs, and dispatching a review are all internal — never announce them, and never narrate the transition between steps. No transition lines — "now I'll write the plan", "먼저 양식을 확인하고", "let me read the guide", "Now I'll dispatch the review", "Now the spec..." (announcing each document as you write it) all leak. (Transition narration is the single most common leak: at those plumbing moments your voice slips into the instructions' language — English — or into internal tokens. The cure is to emit nothing there, not to translate it.) The user sees the beats, never the plumbing between them. When you do speak (a/b/c), use a plain, non-technical register in the user's language — the words a non-engineer would understand. This is your default voice, not a per-line check, so it costs nothing. Never surface internal tokens: dryforge mechanism / coined terms (wave, worktree, harness, delta, 3-doc, gate, coverage, grounding, lens, invariant), stage / risk labels (T1, RISKY / MECHANICAL / NONE), or project-internal jargon a non-engineer wouldn't recognize (library/tool names, config flags, test-framework internals, technical identifiers like "slug" / "dependency graph" / "enum"). Don't soften internal logic into user-ish words — just omit it. E.g. "Starting a git repo here." — not "Since go will later need git for worktrees, I'll initialize one (non-destructive setup)."

Input & preconditions

• Invocation: the user invokes the ready skill. The input may be a goal, file path(s), prose, a mix, or empty. If it is empty or only says to use the skill, ask what they want to build or change.
• git required. If the project is not a git repo, offer to run git init and make an initial commit (an empty repo has no HEAD, so go could not create a worktree later). If git is not installed, stop and say so. This holds for both greenfield and existing projects — code presence is not the deciding factor.
• Output location. The 3-doc is written to .dryforge/ at the project root as plain files. You do not touch .gitignore and do not commit anything — go owns all git mechanics. Keep the produce=plan / run=do boundary: produce writes documents, run touches git.

Stage map + cycle-conditional reference loading

Run the stages in order. Force-load each stage's references at that stage (silently — reference loading and subagent dispatch never produce user-facing text); [first]+ rows load only in a first cycle (status.json absent). The cycle branches scope and conditional loading only — the stage sequence is identical for first and delta.

Core principles  inline (subagents only at intent-completeness + 3-doc-gate) · understand-not-guess ·
                 stack/language-agnostic · conflict→ELICIT · floor not ceiling · user-language native
ORIENT           absorb input + ground code/harness · branch on status.json     (no refs)
DECOMPOSE        decompose.md · grounds-gate.md
ELICIT           elicitation.md · gap-analysis.md · intent-review.md · grounds-gate.md
       [first]+  project-scoping.md · project-design-domain.md · project-design-technical.md ·
                 first-cycle-review.md · foundation-format.md
intent-completeness  intent-completeness.md  ← independent guess-hunt → loop to user (subagent)
SPEC + REVIEW(A) output-format.md · review-fidelity.md            [first]+ foundation-format.md
PLAN             output-format.md · dependency-calc.md · example-3doc.md
HANDOFF          output-format.md                                   [first]+ foundation-format.md
3-doc-gate       3-doc-gate.md                                    [first]+ first-cycle-review.md
                 ← independent dispatch (the final backstop)
USER GATE (the one human checkpoint)

ORIENT — absorb · branch · ground

Take the input raw, decide first-vs-delta, and read code/harness inline to lay the context later stages stand on. No judgment or resolution here — classification is DECOMPOSE's, conflict questions are ELICIT's. Everything ORIENT produces is context, not a conclusion.

1. Check git. Not a repo → offer git init + an initial commit. git not installed → stop and say so. Greenfield or existing, git is required.
2. Absorb the input lightly — capture its character only. Parse the argument tokens: resolve to files where they are paths, read as prose otherwise, accept a mix. Empty / "use the skill" → ask what they want to build or change first (that answer becomes the input; git from step 1 already holds). Load what you read raw — do not summarize (it is the ore DECOMPOSE will deconstruct). Capture the input's character: the rough conception, task type (greenfield / feature / refactor / docs-config) and blast radius, and what the input points at (paths, entities, feature names — for aiming grounding). Stop at character (type / scale) — assigning each piece to an axis is DECOMPOSE's job, not ORIENT's.
   • Low-blast downshift. A low-blast, no-new-contract goal (a one-line change, a docs/config edit, a refactor with no new behavior) → keep the later dialogue light; don't over-interrogate intent that isn't there. Still emit a VALID 3-doc: every section present, gates met, just thinner.
   • **Large inp