Menu

Individual skill

implement

0upvotes

Write the code for a piece of work the way a team will accept it: decide whether the work needs a plan before a line is written, follow the project's own conventions and reference modules, verify by layer with the project's own commands, then call the team review and fix what it blocks on before handing the change over. Use when a ticket, a plan, or a described requirement is ready to be built, and the question left is how to build it rather than what to build. Triggers on: "implement", "code this", "build this feature", "làm task này", "triển khai", "viết code cho", "code tính năng này", "実装", "コード書いて", "この機能を作って", "/atk:implement".

plugins/atk/skills/implement/SKILL.md

Read pinned source

Source commit 55481d2e4ae3cec8e2050c160303c751bbf20173

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
12
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Implement a Change (`atk:implement`)

Writes the code, between two gates. The first decides whether this work may be written at all
before somebody has agreed how: most work may, some work must not. The second is the team review,
called by this skill on its own output rather than left for the reviewer to discover.

What the skill never does is decide. It builds what was agreed, and when it finds it is about to
agree something on the team's behalf, it stops and says whose call it is.

## Scope

Handles: reading the plan, ticket, or description, scoring how much agreement the work needs before
code, writing the change against the project's conventions and reference modules, verifying by
layer with the project's own commands, tidying what was written before anyone reviews it, calling
Back to top