speckit-tasks

speckit-tasks is a skill for Claude Code, Codex from open-software-network/os-clovy. It costs 24 tokens per session (2,303 once invoked), scanned A, a copy of speckit-tasks, MIT.

A task generator that turns a feature's design documents into a dependency-ordered tasks.md file. The file lists implementation work in an order that accounts for which tasks depend on others.

In plain words
What is it for?
Use it to prepare an actionable implementation checklist from the available feature specification and design artifacts.
Why use it?
It turns design notes into a concrete work list and helps avoid starting tasks before their prerequisites are ready.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/open-software-network/os-clovy/speckit-tasks
Any agent
npx skills add open-software-network/os-clovy --skill speckit-tasks
Clone the repo
git clone --depth 1 https://github.com/open-software-network/os-clovy

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for speckit-tasks

README.md
[![agentmods](https://agentmods.dev/badge/skills/open-software-network/os-clovy/speckit-tasks.svg)](https://agentmods.dev/skills/open-software-network/os-clovy/speckit-tasks)
Your own site
<a href="https://agentmods.dev/skills/open-software-network/os-clovy/speckit-tasks"><img src="https://agentmods.dev/badge/skills/open-software-network/os-clovy/speckit-tasks.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,303 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 91% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.02303
Opus 5 $0.00012 $0.01151
Sonnet 5 $0.00005 $0.00461
Haiku 4.5 $0.00002 $0.00230

Measured 6d ago against content hash 54c4665be618, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

speckit-tasks scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

91% identical to speckit-tasks — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/speckit-tasks/SKILL.md · 203 lines

How it starts

The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Pre-Execution Checks

Check for extension hooks (before tasks generation):

  • Check if .specify/extensions.yml exists in the project root.
  • If it exists, read it and look for entries under the hooks.before_tasks key
  • If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
  • Filter out hooks where enabled is explicitly false. Treat hooks without an enabled field as enabled by default.
  • For each remaining hook, do not attempt to interpret or evaluate hook condition expressions:
    • If the hook has no condition field, or it is null/empty, treat the hook as executable
    • If the hook defines a non-empty condition, skip the hook and leave condition evaluation to the HookExecutor implementation
  • When constructing slash commands from hook command names, replace dots (.) with hyphens (-). For example, speckit.git.commit/speckit-git-commit.
  • For each executable hook, output the following based on its optional flag:
    • Optional hook (optional: true):
      ## Extension Hooks
      
      **Optional Pre-Hook**: {extension}
      Command: `/{command}`
      Description: {description}
      
      Prompt: {prompt}
      To execute: `/{command}`
      
    • Mandatory hook (optional: false):
      ## Extension Hooks
      
      **Automatic Pre-Hook**: {extension}
      Executing: `/{command}`
      EXECUTE_COMMAND: {command}
      
      Wait for the result of the hook command before proceeding to the Outline.
      
  • If no hooks are registered or .specify/extensions.yml does not exist, skip silently

Outline

  1. Setup: Run .specify/scripts/bash/setup-tasks.sh --json from repo root and parse FEATURE_DIR, TASKS_TEMPLATE, and AVAILABLE_DOCS list. FEATURE_DIR and TASKS_TEMPLATE must be absolute paths when provided. AVAILABLE_DOCS is a list of document names/relative paths available under FEATURE_DIR (for example research.md or contracts/). For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot").

Read the full file on GitHub · 203 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 203 lines · 24 tokens per session scan A 54c4665be618

Subscribe to this mod's changes

speckit-tasks is a skill published in the GitHub repository open-software-network/os-clovy (357 stars, last pushed 5d ago), licensed MIT. It adds 24 tokens to every session and 2,303 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to speckit-tasks, differing in 4 lines, and is treated as a copy.

Related

Other skills, from other repositories

personal-commands

Edit hex.config.ts, not .hex-sdk. Config and installed dependencies execute with the user's normal permissions; use only trusted packages and avoid network, filesystem, environment, or subprocess access unless the requested command requires it. Run bun run check after editing.

anomalyco/hex · 0 tokens

hex-personal-commands

Configure HEX personal voice commands, voice-dictation control phrases, and deterministic transcript transformations. Use when the user wants to add or change commands or transformations for the HEX macOS voice app.

anomalyco/hex · 44 tokens

verify-dictation

The canonical "prove VZT Flow actually works" checklist — the human hotkey test plus its automated equivalents. Use before claiming a dictation-pipeline change works, before a release, or when the user runs /verify-dictation.

vonzelle-vzt/vzt-flow · 53 tokens

macparakeet-stt

Use when the user asks to transcribe audio or video, inspect or manage MacParakeet meeting recordings, search prior dictations/transcripts, or give an AI agent local speech-to-text tools on Apple Silicon.

moona3k/macparakeet · 50 tokens

release-murmur

Cut a signed, notarized macOS release of Murmur (Tauri 2 + Angular 22). The exact, proven step-by-step runbook — preflight gates → version bump (+ Cargo.lock sync) → JakubGawr commit → PR-merge to the murmur trunk (never direct-push) → rustup targets → stop dev → universal build → Developer-ID sign BY IDENTITY HASH…

murmur-io/murmur · 169 tokens

ship-feature

Ship a Murmur feature through scope, isolated implementation, fresh adversarial and required security review, project gates, a JakubGawr commit, and a PR to murmur. Use the verifier-only Harness for risky, multi-step, or explicitly requested work; ordinary low-risk fixes keep the normal isolated-worktree route.

murmur-io/murmur · 69 tokens