implement

implement — spec-driven implementation

Methodology for implementing against written specs, leaving a case behind each rule, and closing the loop with review. Opened by the smith agent at its first step; usable directly.

skills/agent-contract/SKILL.md binds this session too, and only if you load it. A session driving the work directly reads this skill and never agents/*.md, so the contract every agent it spawns receives at startup reaches it by being opened rather than by arriving — user-invocable: false permits the load and does not oblige it. #107's headline failure is an orchestrator breaking a rule it had put into every prompt it sent.

If you are orchestrating a work item rather than building it, read skills/implement/orchestration.md before the first edit; an implementer never opens it, and everything below is the implementer's and the orchestrator's alike.

The language the records are written in

Read Record language in config.md before writing any of the documents below, the same way commit-pr-convention reads its own row before a commit or a pull request. The root is resolved the way every path in this skill is.

| Item | Value |
|---|---|
| Record language | Korean |

It governs the prose in spec.md, plan.md, overview.md, questions.md, changelog.md, the cell contents of rounds/round-N.md and phases/phase-N.md and the text beneath their tables.

Every way of not naming one lands on English — no file, no such row, an empty value, a file that cannot be read. A config nobody can read must not stop the work.

It is independent of Commit and pull request language. Setting one does not carry the other, and the two surfaces have different audiences: a pull request is read by whoever opens it, and a record is read by whoever comes back to the decision six months later.

What stays English whatever it says, because these are read literally rather than by a person: every field name, section heading and vocabulary word the checkers match, listed in templates/config.md under What no row governs — that list is derived from the checkers' own constants, so it cannot drift from them; <!-- specs/<work-item-id> --> and the other markers; a drained line and the closed that opens a closed row; and all code — identifiers, comments, docstrings, file names, test function names. A translated field name is not a translation, it is a checker that stops reading.