implement
Implement a piece of work based on a spec or set of tickets.
- License 许可
- GPL-3.0
- 最近更新
- 2026-11-09
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- implement
- description
- Implement a piece of work based on a spec or set of tickets.
02 资源文件 2
- 参考文档agents/openai.yaml138 B
- 参考文档CREDITS.md2.1 KB
03 SKILL.md 正文
A prompt or brief naming this skill is its invocation.
Implement the work described by the user in the spec or tickets.
Use /tdd where possible, at pre-agreed seams.
Run typechecking regularly, single test files regularly, and the full test suite once at the end.
Once done, use /code-review to review the work.
Commit your work to a branch that holds only this work, made from the up-to-date base branch and never the base branch itself; the current branch serves when it already is such a branch. Deliver it as the repository's contribution guide directs, such as one pull request; without one, leave the commits on that branch.
Reads
Paths are relative to the repository root.
CONTRIBUTING.md: how the repository delivers work, such as one pull request. When it is missing, leave the commits on the work's branch.
04 同仓库更多 Skills
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
triage
Move issues and external PRs through a state machine of triage roles, sort each request by where its uncertainty lies, and bring its agent brief to acceptance through research and independent review, or through a grilling session with the owner.
to-tickets
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
to-spec
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.