Stats
Actions
Tags
From backlog
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/backlog:specThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
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.
Find the task — use task_list or task_info to find the task matching "$ARGUMENTS". If $ARGUMENTS is empty, call task_list with filter status:pending -doc to 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_write to attach a markdown document to the task with:
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.
npx claudepluginhub backloghq/backlog --plugin backlogCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.