agentsclimarketplace
Sign in

Spec

Skill backloghq/backlog/skills/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.From its SKILL.md

Install
npx -y skills add backloghq/backlog --skill spec

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.3 KB, as published. Nobody here has run it

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

  1. 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.

  2. Understand the context — read relevant code, configs, and existing docs in the codebase to understand what the task involves.

  3. Write the spec — use task_doc_write to 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

  4. 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.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.