implement
Implement one ticket (or a small set) end to end: worktree, TDD, review, verified PR.
- License 许可
- MIT
- 最近更新
- 2026-11-05
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- implement
- description
- Implement one ticket (or a small set) end to end: worktree, TDD, review, verified PR.
- argument-hint
- Issue number(s), or a spec/ticket path
- disable-model-invocation
- true
02 资源文件 1
- 参考文档agents/openai.yaml139 B
03 SKILL.md 正文
Implement the work described by the user in the spec or tickets.
Call the Skill tool with dk:issue-flow and follow it for every git and GitHub step: reading the ticket, the worktree, scope intake, commits, evidence and the PR. Fetch each ticket and state its title before starting. If the reference is ambiguous, ask.
Call the Skill tool with dk:tdd where possible, at pre-agreed seams.
Run typechecking regularly, single test files regularly, and the full test suite once at the end. Commit after each green step.
When the code is done, call the Skill tool with dk:verify and prove the change.
Then call the Skill tool with dk:code-review to review the work, and answer its findings by its Answer findings step: each id fixed, disagreed with or declined in the ledger, within its round budget. The PR body carries the ledger.
Finally open the PR with the body from the dk:pr skill, per dk:issue-flow.
Asking
A question in a plain message reads like a finished run, so it goes unseen. When the maintainer has said they are away for the run, ask only for one of these reasons:
- no proof of the change is possible;
- the ready gate (
dk:issue-flowstep 6) cannot pass, and you cannot fix that yourself; - the next step is outside the grant, which is this issue's worktree, branch and PR: deleting data, touching production, changing anything outside the repo, closing a PR, or force-pushing another branch;
- the goal is ambiguous in a way that changes the result;
- another PR makes this one obsolete.
Ask through the AskUserQuestion tool, and put the PR link when one exists, what blocks you and the options in the question, your recommendation first. With no question tool, or no answer from it, take the safe path: stop where the work stands, and open your final message with the question.
Decide everything else with a sensible default, including the seams dk:tdd asks you to agree, and list each decision under Decisions taken in the report.
Several tickets
With more than one ticket, each gets an implementer subagent that runs the sequence above in its own worktree, launched by the fan-out rules in dk:issue-flow step 2.
Before reporting, dry-merge the tickets' branches: fetch, then run git merge-tree --write-tree --name-only on each branch against origin/<base> (the base, dk:issue-flow step 2) and on each pair of branches. Exit status 1 is a conflict, with the conflicting files listed after the tree id. The report names each conflict by its two tickets and its files, or says the branches merge cleanly.
Report
The final message is the report: the PR link and its head, the proof, dk:code-review's Answer findings report (the rounds run, the ledger, the shortstat before and after, each declined finding's issue number), the Decisions taken with the reason for each, and the risks that remain. It ends with the verdict from dk:issue-flow step 6's Ready gate., one per PR. A run stopped before any PR reports where it stopped, the question and the Decisions taken, and ends on the question, with no verdict line.
04 同仓库更多 Skills
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
verify
Prove a change works by driving it in a stack you started, against a control run of the pre-fix state. Use before calling any change verified, or when asked to verify or prove a fix.
verify-doc-check
Monthly check that this repo's docs/agents/verify.md still starts the stack: read every claim against the source, run the recipe in a fresh worktree, fix or file each drifted step.
triage
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
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.