AGENT SKILL

implement

Use when agreed work is to be written into code.

License 许可
MIT
最近更新
2026-10-14
Stars
★ 0
Forks
0

01 前言 Front Matter

name
implement
description
Use when agreed work is to be written into code.

03 SKILL.md 正文

Mechanism: not yet

Implement the work described by the relevant architecture decisions (spec, ticket, RFC, prior discussion).

Pick entity names in vibe with the project glossary. Do not use implementation-shaped names or parameters; orient them at the function's meaning toward the client.

Use /tdd where possible, at pre-agreed seams. Make sure implementation, even in dummy/degenerate form, fully follows contract surfaces in the docs.

Make methods behind main architectural boundaries clear — they should read almost as a story explaining the boundary logic, with separate concerns extracted to properly named sub-methods. Prefer to split submethods by responsibility.

The code should read as a story. Make sure the main process appears first in the file, where possible, and main boundaries' implementation reads through entities, interfaces and submethods used as nouns, adjectives and verbs.

Mark code an open question's answer will change with a comment line beginning TODO that names the question, per the entry file's straw-dog rule, and say so in the docstring.

Where the code you write follows a rule that a load-bearing record of the project states — its architecture or an ADR — name each such rule at the end of the comment phrase it backs, as (<path from the tree's root>: "<the rule's name>"), whole on one line — wrap the comment before it, never inside it — the name being the rule's heading or the bold lead of its paragraph, word for word. A rule with no such name gets one in its record first. Code no such rule governs carries no pointer.

Make sure the errors follow error rules.

Make sure to read and follow /improve-comments rules. Mark other pending actions — hotpaths that may need optimization, work with no named successor — as TODO too; without a ticket they are notes, and the listing script reports them as guesses.

During the work, run the checks in the project's verification set, as /verify defines it. /verify is the verification of landed work; a local run of a subset is not that pass.

Once done, and unless you need to take a break, use /verify.

Read commit from AGENTS.md. Do not commit until that switch allows it. Repair during the work follows the repair switch; it is not a substitute for /verify.

<installed by="local"> L3 The verification set: the project's CI and the harness's record checks, every one green.

uv run ruff check .
uv run ruff format --check .
uv run pyright
uv run pytest
uv run python .agents/scripts/gw/tickets.py --check
uv run python .agents/scripts/gw/edges.py --check
uv run python .agents/scripts/gw/questions.py --check
uv run python .agents/scripts/gw/product.py --check
uv run python .agents/scripts/gw/maintain.py --check

</installed>

04 同仓库更多 Skills