Borrowing it
Nothing to install: this file belongs to growilabs/growi-mcp-server. 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/growilabs/growi-mcp-server/main/.claude/commands/kiro/spec-tasks.mdgit clone --depth 1 https://github.com/growilabs/growi-mcp-serverWrote 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/growilabs/growi-mcp-server/spec-tasks)<a href="https://agentmods.dev/commands/growilabs/growi-mcp-server/spec-tasks"><img src="https://agentmods.dev/badge/commands/growilabs/growi-mcp-server/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.00629 |
| Opus 5 | $0.00003 | $0.00315 |
| Sonnet 5 | $0.00001 | $0.00126 |
| Haiku 4.5 | $0.00001 | $0.00063 |
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
92% identical to spec-tasks — 16 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Tasks Generator
Parse Arguments
- Feature name:
$1 - Auto-approve flag:
$2(optional, "-y") - Sequential mode flag:
$3(optional, "--sequential")
Validate
Check that design has been completed:
- Verify
.kiro/specs/$1/exists - Verify
.kiro/specs/$1/design.mdexists - Determine
sequential = ($3 == "--sequential")
If validation fails, inform user to complete design phase first.
Invoke Subagent
Delegate task generation to spec-tasks-agent:
Use the Task tool to invoke the Subagent with file path patterns:
Task(
subagent_type="spec-tasks-agent",
description="Generate implementation tasks",
prompt="""
Feature: $1
Spec directory: .kiro/specs/$1/
Auto-approve: {true if $2 == "-y", else false}
Sequential mode: {true if sequential else false}
File patterns to read:
- .kiro/specs/$1/*.{json,md}
- .kiro/steering/*.md
- .kiro/settings/rules/tasks-generation.md
- .kiro/settings/rules/tasks-parallel-analysis.md (include only when sequential mode is false)
- .kiro/settings/templates/specs/tasks.md
Mode: {generate or merge based on tasks.md existence}
Instruction highlights:
- Map all requirements to tasks and list requirement IDs only (comma-separated) without extra narration
- Promote single actionable sub-tasks to major tasks and keep container summaries concise
- Apply `(P)` markers only when parallel criteria met (omit in sequential mode)
- Mark optional acceptance-criteria-focused test coverage subtasks with `- [ ]*` only when deferrable post-MVP
"""
)
Display Result
Show Subagent summary to user, then provide next step guidance:
Next Phase: Implementation
Before Starting Implementation:
- IMPORTANT: Clear conversation history and free up context before running
/kiro:spec-impl - This applies when starting first task OR switching between tasks
- Fresh context ensures clean state and proper task focus
If Tasks Approved:
- Execute specific task:
/kiro:spec-impl $1 1.1(recommended: clear context between each task) - Execute multiple tasks:
/kiro:spec-impl $1 1.1,1.2(use cautiously, clear context between tasks) - Without arguments:
/kiro:spec-impl $1(executes all pending tasks - NOT recommended due to context bloat)
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 · 76 lines · 6 tokens per session scan A cdda0f5273d1
spec-tasks is a command published in the GitHub repository growilabs/growi-mcp-server (19 stars, last pushed 1mo ago), licensed MIT. It adds 6 tokens to every session and 629 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to spec-tasks, differing in 16 lines, and is treated as a copy.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.