Borrowing it
Nothing to install: this file belongs to pilotspace/pilot-space. 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/pilotspace/pilot-space/main/.claude/commands/speckit.tasks-detail.mdgit clone --depth 1 https://github.com/pilotspace/pilot-spaceWrote 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/pilotspace/pilot-space/speckit.tasks-detail)<a href="https://agentmods.dev/commands/pilotspace/pilot-space/speckit.tasks-detail"><img src="https://agentmods.dev/badge/commands/pilotspace/pilot-space/speckit.tasks-detail.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.00000 | $0.03435 |
| Opus 5 | $0.00000 | $0.01717 |
| Sonnet 5 | $0.00000 | $0.00687 |
| Haiku 4.5 | $0.00000 | $0.00344 |
Grade A, and why
speckit.tasks-detail 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 — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Task Details
description: Generate task detail files from tasks.md with implementation guidance for AI agents. handoffs:
- label: Implement Tasks agent: speckit.implement prompt: Start implementing tasks in order send: true
- label: Analyze Consistency agent: speckit.analyze prompt: Run consistency analysis send: true
- label: Review Tasks agent: code-review prompt: Review task detail files send: false
User Input
$ARGUMENTS
Consider user input before proceeding. Load @docs/dev-pattern/README.md for project rules.
Purpose
Generate task detail files from tasks.md:
- Grouped files (
P{N}-{IDs}.md) for simple, related tasks (complexity ≤6) - Individual files (
T{ID}.md) for complex tasks (complexity >6)
| Condition | Output |
|---|---|
| Complexity ≤6 + Same Phase + Same Type + ≥2 tasks | P{N}-{IDs}.md |
| Complexity >6 OR single task of type | T{ID}.md |
Flags
| Flag | Description | Default |
|---|---|---|
--incremental |
Generate only missing/changed tasks | false |
--validate-only |
Validate without generating | false |
--range T{START}-T{END} |
Generate task range | all |
--phase {N} |
Generate phase only | all |
--force |
Regenerate all | false |
--dry-run |
Preview without writing | false |
--no-group |
Disable grouping | false |
--group-threshold {N} |
Complexity threshold | 6 |
Workflow
Phase 1: Setup
Run .specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks from repo root. Parse JSON for FEATURE_DIR and AVAILABLE_DOCS (use absolute paths).
Phase 2: Validation
Verify before generating:
- tasks.md format compliance (no duplicate IDs, valid P1-P4 priority)
- User story refs exist in spec.md
- Phase numbers sequential
Stop and report if validation fails.
Phase 3: Load Context
Required (from FEATURE_DIR): plan.md, spec.md, tasks.md
Optional: data-model.md, contracts/, research.md
Templates: .specify/templates/task-detail-template.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 · 384 lines · 0 tokens per session scan A 1521df85e77e
speckit.tasks-detail is a command published in the GitHub repository pilotspace/pilot-space (2 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,435 tokens. 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-31.
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.