Synthesize what is already settled into a spec, adding the uncontested facts a decision record drops: no interview, no new decisions. If the work fits in the current context, say once that implementing directly is cheaper.

If an argument names a file, issue, or URL, read it in full first. With no argument, propose the one that has no beside it, or ask. Read and if they exist.

Run three searches, as parallel subagents if your harness has them:

Each is a documentarian: describe, never design. Also look for a verification skill: a project skill (in or a harness skills folder) whose says it runs the product and records whether a check passed.

Then sketch the seams where this gets tested. Prefer existing seams, the highest one available, and as few as possible; one is ideal. Check the seams with the user before writing.

Use these sections, in order, with these exact names. Facts about today cite (Current state, Seams); Decisions and Sequence never do.

The problem from the user's perspective, observable: who hits it, how often, how you know.

What changes for the user, in the narrowest version still worth shipping.

What exists today, with , plus constraints and what is missing.

A numbered list of statements true once this works, one line each, each checkable by someone using the product. No "as an actor, I want" framing.

Each decision, the alternative that lost, and why it lost. No file paths or code, except a trimmed snippet (schema, state machine, type shape) that encodes a decision more precisely than prose.

Where this gets tested: for existing seams, and for each new seam the reason no existing one would do.

The order behaviour arrives in, from the user's point of view. Product ordering only: no work units or blocking edges. Past about seven entries, say the scope got wide.

Named, so it cannot creep back in.

What breaks or gets worse, and why that is acceptable.

With a verification skill, read its , then put every check it can run under Automated as agent steps, such as "verify: submit the signup form, the dashboard greets the new account, and one row exists". Manual keeps only judging look and feel, or actions no agent can perform.

Write , beside the decision record when there is one; otherwise propose a short kebab-case slug and confirm it before writing. The spec file is the only artifact. Tell the user to commit the feature folder: implement-slice reads it from git.