Borrowing it
Nothing to install: this file belongs to j5ik2o/event-store-adapter-js. 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/j5ik2o/event-store-adapter-js/main/.claude/commands/kiro/spec-tasks.mdgit clone --depth 1 https://github.com/j5ik2o/event-store-adapter-jsWrote 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/j5ik2o/event-store-adapter-js/spec-tasks)<a href="https://agentmods.dev/commands/j5ik2o/event-store-adapter-js/spec-tasks"><img src="https://agentmods.dev/badge/commands/j5ik2o/event-store-adapter-js/spec-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.00006 | $0.01373 |
| Opus 5 | $0.00003 | $0.00687 |
| Sonnet 5 | $0.00001 | $0.00275 |
| Haiku 4.5 | $0.00001 | $0.00137 |
Grade A, and why
spec-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.
This is a copy
89% identical to kiro-spec-tasks — 46 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.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Tasks Generator
<background_information>
- Mission: Generate detailed, actionable implementation tasks that translate technical design into executable work items
- Success Criteria:
- All requirements mapped to specific tasks
- Tasks properly sized (1-3 hours each)
- Clear task progression with proper hierarchy
- Natural language descriptions focused on capabilities </background_information>
Execution Steps
Step 1: Load Context
Read all necessary context:
.kiro/specs/$1/spec.json,requirements.md,design.md.kiro/specs/$1/tasks.md(if exists, for merge mode)- Entire
.kiro/steering/directory for complete project memory
Validate approvals:
- If
-yflag provided ($2 == "-y"): Auto-approve requirements and design in spec.json - Otherwise: Verify both approved (stop if not, see Safety & Fallback)
- Determine sequential mode based on presence of
--sequential
Step 2: Generate Implementation Tasks
Load generation rules and template:
- Read
.kiro/settings/rules/tasks-generation.mdfor principles - If
sequentialis false: Read.kiro/settings/rules/tasks-parallel-analysis.mdfor parallel judgement criteria - Read
.kiro/settings/templates/specs/tasks.mdfor format (supports(P)markers)
Generate task list following all rules:
- Use language specified in spec.json
- Map all requirements to tasks
- When documenting requirement coverage, list numeric requirement IDs only (comma-separated) without descriptive suffixes, parentheses, translations, or free-form labels
- Ensure all design components included
- Verify task progression is logical and incremental
- Collapse single-subtask structures by promoting them to major tasks and avoid duplicating details on container-only major tasks (use template patterns accordingly)
- Apply
(P)markers to tasks that satisfy parallel criteria (omit markers in sequential mode) - Mark optional test coverage subtasks with
- [ ]*only when they strictly cover acceptance criteria already satisfied by core implementation and can be deferred post-MVP - If existing tasks.md found, merge with new content
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 · 139 lines · 6 tokens per session scan A fb0b7a121aa0
spec-tasks is a command published in the GitHub repository j5ik2o/event-store-adapter-js (24 stars, last pushed today), licensed Apache-2.0. It adds 6 tokens to every session and 1,373 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to kiro-spec-tasks, differing in 46 lines, and is treated as a copy.
Other commands, from other repositories
workflow-design
Exécuter la phase de Conception (Solutioning) - spécification technique et architecture.
sprint
Équipe de Développement Sprint - Implémentation parallèle de stories utilisant les Agent Teams.
workflow-implement
Exécuter la phase d'Implémentation - développement sprint avec TDD/BDD.
auto-sprint
Orchestrateur de sprint de bout en bout (démarrage -> décomposition -> validation -> implémentation -> PR -> CI -> revue -> rétro -> merge).
workflow-plan
Exécuter la phase de Planification - création du PRD, personas et génération du backlog.
start
Préparation du Début de Sprint.