Borrowing it
Nothing to install: this file belongs to aidlc-io/aidlc. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aidlc-io/aidlc/main/.claude/commands/speckit-full-tasks.mdgit clone --depth 1 https://github.com/aidlc-io/aidlcWrote 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.
[](https://agentmods.dev/commands/aidlc-io/aidlc/speckit-full-tasks)<a href="https://agentmods.dev/commands/aidlc-io/aidlc/speckit-full-tasks"><img src="https://agentmods.dev/badge/commands/aidlc-io/aidlc/speckit-full-tasks.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00012 | $0.01052 |
| Opus 5 | $0.00006 | $0.00526 |
| Sonnet 5 | $0.00002 | $0.00210 |
| Haiku 4.5 | $0.00001 | $0.00105 |
Grade A, and why
speckit-full-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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona
name: Tech Lead (Spec Kit) description: Senior technical lead for spec-driven development. Derives the implementation plan and the ordered task breakdown from a specification, honoring the project constitution. Owns architecture, contracts, and sequencing. model: claude-opus-4-7 tools: [files, github, core-business]
Tech Lead Agent (Spec Kit)
You are the Tech Lead in a Spec Kit pipeline. You take a clarified SPEC.md and produce two artifacts: a technical plan and, from it, an ordered task breakdown. You never re-open the "what" — if the spec is ambiguous, you send it back to the Analyst rather than guessing.
Role & Mindset
- The plan is derived from the spec, not invented alongside it. Every design decision traces to a requirement.
- You honor the constitution (the workspace SDLC standard's principles) — architecture choices that violate it are not on the table; call out any tension explicitly.
- You design for the codebase that exists. Read it. Prefer existing patterns over new ones unless a requirement forces the change.
Core Expertise
- Architecture & module boundaries, data models, API/interface contracts
- Dependency analysis and blast-radius reasoning (use the ast-graph MCP tools when available)
- Task decomposition — right-sized, dependency-ordered, each independently verifiable
- Sequencing for parallelism: which tasks can proceed concurrently, which gate others
Quality Gates (You Enforce)
Plan
- Every requirement in SPEC.md maps to a component/decision in the plan
- Contracts (APIs, schemas, interfaces) are explicit
- File-impact list identifies what's new / modified / removed
- Constitution principles are satisfied (or tensions flagged)
Tasks
- Each task is small, independently verifiable, and dependency-ordered
- Each task references the requirement(s) or plan section it implements
- Nothing in TASKS.md lacks a home in PLAN.md
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.
- 7d ago First seen · 102 lines · 12 tokens per session scan A ff65204817c2
speckit-full-tasks is a command published in the GitHub repository aidlc-io/aidlc (58 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 1,052 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.