implement
/implement
Pick up a task from the backlog and implement it. Reads the spec if one exists, starts the task, does the work, and marks it done. Use when the user wants to work on a specific task or the next available task.
- Author
- backloghq ↗
- Repository
- backlog ↗
- Licence
- MIT
- Last repository change
- 30.05.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 30.05.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Pick up a task from the backlog and implement it. Reads the spec if one exists, starts the task, does the work, and marks it done. Use when the user wants to work on a specific task or the next available task.
Original author description
Pick up a task from the backlog and implement it. Reads the spec if one exists, starts the task, does the work, and marks it done. Use when the user wants to work on a specific task or the next available task.
How it works
- Process
SKILL.md preview
--- name: implement description: Pick up a task from the backlog and implement it. Reads the spec if one exists, starts the task, does the work, and marks it done. Use when the user wants to work on a specific task or the next available task. --- # Implement Task Pick up a task and implement it. If an argument is provided, use it as the task ID. Otherwise, pick the highest-urgency unblocked task. ## Process 1. **Find the task** — if "$ARGUMENTS" is provided, ALWAYS resolve it with `task_info` first to confirm the task exists and get its current state (status, project, deps, attached doc). Otherwise, call `task_list` with filter `status:pending` and pick the highest-urgency task that is NOT blocked (+BLOCKED). Use the UUID from this lookup for every subsequent `task_start`/`task_done`/`task_annotate` call — never substitute a UUID from memory or a previous unrelated context. 2. **Read the spec** — call `task_doc_read` to check if the task has an attached spec. If it does, read it carefully — it defines what to build and how to verify. 3. **Start the task** — call `task_start` to mark it as actively being worked on. 4. **Do the work** — implement what the task and spec describe. Write code, create files, run tests. Use the codebase tools (Read, Edit, Write, Bash, Grep, Glob) as needed. 5. **Verify** — check the acceptance criteria from the spec. Run relevant tests. Make sure the implementation is complete. 6. **Complete the task** — call `task_done` to mark it as completed. Add an annotation with `task_annotate` summarizing what was done if the changes aren't obvious. 7. **Check what's next** — call `task_list` with filter `status:pending` to see if completing this task unblocked anything. Mention what's ready to pick up next.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · backloghq/backlog | 90 | MIT |
| ericrisco/rsc-harness | 100 | MIT |
| yonatangross/orchestkit | 100 | MIT |
| sentimony/agentic-workflow | 100 | MIT |
| moberghr/mtk-agent-toolkit | 100 | MIT |
| michielvandermeer/skills | 100 | MIT |
| rossumai/claude-marketplace | 100 | MIT |
| userKael/rastro | 100 | MIT |
| yonatangross/orchestkit | 100 | MIT |
Database snapshot: 13.11.2026 · package version 58b7d9ec1bfb (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90pick
Pick a task from the work queue (`ravenseat`) and do it yourself in this session, following the same protocol as a queue track. Use when the user types "/pick" (suggestions for what can be picked now) or "/pick <id>" (take exactly that task), or says "pick a task", "what can I… - 81task_select
Select and rank eligible live tasks from the project backlog. Use when the user asks what task to work on next, asks the agent to pick or prioritize backlog work, rank open tasks, choose from tasks/, or recommend the next task/action without editing task files. - 100take-task
This skill should be used when claiming a task to work on - "take task", "візьми таск", "працюю над", "work on task X", "pick task X", "switch to task X", "claim task". Sets task to in_progress, creates/switches branch, saves the per-branch task-state file. - 81task_create
Create exactly one new task file for one upcoming work item. Use when the user asks to make, add, file, write, or capture a single task or todo. Use task for listing, querying, updating, archiving, linting, or multi task backlog work. - 100task
Turn "remind me to / I need to / add a task" into a real backlog task (deterministic, dashboard-ready). Use for a new to-do, or the //task command. - 100worktree-task-start
Use when the user asks to start a backlog task, begin work on an issue, pick up issue N, or run `make task`. Triggers on "start task", "begin issue", "pick up issue N", "work on #N".