implement

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

Implement the work described by the user in the spec or tickets.

If the user passes a ticket reference, fetch it from the issue tracker and
state its title before starting. If the reference is ambiguous, ask.

Use `tdd` where possible, at pre-agreed seams.

Run focused validation while changing the code and repository-required checks
before delivery. Repeat broader checks when later changes or failures warrant
them.

## Hold the scope

Implement what the spec or tickets ask for. Do not add helper functions,
abstraction layers, configuration options, or defensive scaffolding that no
ticket requested. Do not widen the work into adjacent cleanup, refactoring, or
documentation.

Compare the diff against the requirement and revert anything the work did not
need.

## Deliver

Once done, use `code-review` to review the work.

For an existing PR, a request to implement fixes or address valid feedback
includes committing and pushing the validated changes to that PR, unless the
user asks to keep them local. Verify the remote head and inspect its checks
after pushing. Permission to fix code does not include review replies, thread
resolution, rebasing, force-pushing, merging, or deployment.

For new work, follow the delivery boundary already agreed with the user. If
publication was not requested, leave validated changes local. Use `file-pr`
when they want a pull request.

From dwin/skills, MIT.

More from dwin/skills