Agent skill
spec
Write a detailed spec document for a task before implementation begins. Use when the user wants to define requirements, acceptance criteria, or technical design for a task.
Install this agent skill to your Project
npx add-skill https://github.com/backloghq/backlog/tree/main/skills/spec
SKILL.md
Write Task Spec
Write a specification document for a task. If an argument is provided, use it as the task ID or description to find the task. Otherwise, ask which task to spec.
Process
-
Find the task — use
task_listortask_infoto find the task matching "$ARGUMENTS". If $ARGUMENTS is empty, calltask_listwith filterstatus:pending -docto show tasks without specs and ask which one. -
Understand the context — read relevant code, configs, and existing docs in the codebase to understand what the task involves.
-
Write the spec — use
task_doc_writeto attach a markdown document to the task with:- Goal: what this task achieves
- Requirements: specific things that must be built or changed
- Technical approach: key decisions and implementation strategy
- Acceptance criteria: how to verify the task is done
- Relevant code: file paths and functions to modify
-
Confirm — show a summary of the spec that was written and the task it was attached to.
Keep specs concise and actionable — a spec should be something an agent can pick up and implement without further context.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
refine
Review and improve the backlog — identify vague tasks, missing priorities, broken dependencies, tasks needing specs, and stale items. Use when the user wants to groom, refine, clean up, or improve their task backlog.
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.
tasks
Show the current task backlog — pending, active, blocked, and overdue tasks. Use when the user asks about tasks, status, what needs to be done, or what's in progress.
handoff
Prepare a session handoff — summarize progress, annotate tasks with current status, and identify what's ready for the next session. Use at the end of a work session or when the user says they're done for now.
plan
Break down a goal into actionable tasks with dependencies, priorities, and optional specs. Use when the user wants to plan work, decompose a feature, or create a task breakdown.
standup
Daily standup summary — what was completed recently, what's in progress, and what's blocked. Use when the user asks for a standup, status update, or summary of recent work.
Didn't find tool you were looking for?