ready

Invoke the ready skill with your goal, notes, or existing documents as input. It interactively elicits the decisions only you can make, presents technical options with trade-offs, and writes a handoff, spec, and plan into .dryforge/ for the go skill to execute.

It accepts a natural-language goal, file paths to specs or brain-dumps, scattered notes, a mix of these, or nothing at all. Input is treated as challengeable material, not ground truth, and becomes settled only through dialogue and your approval.

Yes, git is required for both greenfield and existing projects. If the project is not a git repo, the skill offers to run git init with an initial commit; if git is not installed, it stops and tells you.

Every load-bearing decision must be grounded in what you said or explicitly asked. An independent intent-completeness subagent audits the dialogue for un-grounded guesses before the spec is frozen, and a final 3-doc gate reviews the finished documents.

The skill branches on whether .dryforge/status.json exists. First cycle runs a forced foundation design covering domain and technical decisions; delta mode loads the existing harness as context and applies full rigor only to the current task.

Skip it for trivial one-line changes where a full spec is overhead, though it still downshifts to a thinner valid 3-doc for low-blast goals. It also cannot run without git installed, and it never executes code — execution belongs to the go skill.