원클릭으로
implement
Implement a piece of work based on a spec or set of tickets.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Implement a piece of work based on a spec or set of tickets.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Build, launch, and drive the mindwalk web UI end-to-end for verification.
Set up or troubleshoot Yassimba's curated agent skills, Pi packages, Herdr, and Herdr plugins through the ai-setup CLI. Use when the user asks to install this collection, configure Herdr, add one of its capabilities, update the setup, or diagnose installation problems.
Backlog management: use when the user mentions a backlog, asks what's next, wants work recorded before implementation, or wants queued ideas or specs prioritized, transitioned, completed, or removed; also use when another skill needs to record lifecycle changes.
Use when the user wants to brainstorm or explore an idea — a feature, product direction, or "what if" — before deciding whether it deserves a plan. Ideation only — ends in an idea brief, not a design.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (this repo's documented coding standards) and Spec (what the originating issue/PRD asked for). Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
Use when creating a git commit — the user asks to commit, or a unit of work is complete and ready to commit.
| name | implement |
| description | Implement a piece of work based on a spec or set of tickets. |
| disable-model-invocation | true |
Implement the work described by the user in the spec or tickets.
Before writing any code, use the blueprint skill to show what you intend to build and get approval. Skip only for trivial changes — a rename, a one-line fix.
Use /tdd where possible, at pre-agreed seams. A ticket's "Rules & examples" map is the scenario list — one test per example.
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 the current branch.