What is kiro-spec-batch?

A tool for creating full feature specifications from a roadmap, including requirements, technical design, and implementation tasks. It processes independent features in parallel while respecting dependencies between them.

Use it to read pending roadmap entries, validate their briefs, generate specification files, dispatch independent work by dependency wave, and check consistency across features.

It turns a mixed roadmap into ordered, consistent specification files and checks that related features agree on models and interfaces. This reduces manual sequencing and missing planning documents.

How akaghef/M3E configures Codex

Reuse

Borrowing it

Nothing to install: this file belongs to akaghef/M3E. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/akaghef/M3E/main/.agents/skills/kiro-spec-batch/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/akaghef/M3E

Made for: 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/akaghef/m3e/kiro-spec-batch/github.svg)](https://agentmods.dev/skills/akaghef/m3e/kiro-spec-batch)

Your own site

<a href="https://agentmods.dev/skills/akaghef/m3e/kiro-spec-batch"><img src="https://agentmods.dev/badge/skills/akaghef/m3e/kiro-spec-batch/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/akaghef/m3e/kiro-spec-batch"><img src="https://agentmods.dev/badge/skills/akaghef/m3e/kiro-spec-batch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,994 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.00031	$0.01994
Opus 5.5	$0.00012	$0.00798
Sonnet 5.5	$0.00006	$0.00399
Haiku 4.5	$0.00003	$0.00199

Measured 5d ago against content hash 6b490abdbc17, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

kiro-spec-batch 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 5d 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.

.agents/skills/kiro-spec-batch/SKILL.md · 166 lines

How it starts

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

Spec Batch

<background_information>

Success Criteria:
- All features have complete spec files (spec.json, requirements.md, design.md, tasks.md)
- Dependency ordering respected (upstream specs complete before downstream)
- Independent features processed in parallel via sub-agent dispatch
- Cross-spec consistency verified (data models, interfaces, naming)
- Mixed roadmap context understood without breaking ## Specs (dependency order) parsing
- Controller context stays lightweight (sub-agents do the heavy work) </background_information>

Step 1: Read Roadmap and Validate

Read .kiro/steering/roadmap.md
Parse the ## Specs (dependency order) section to extract:
- Feature names
- One-line descriptions
- Dependencies for each feature
- Completion status ([x] = done, [ ] = pending)
If present, also read for context:
- ## Existing Spec Updates
- ## Direct Implementation Candidates Do not include these in dependency-wave execution; they are awareness-only inputs for sequencing and consistency review.
For each pending feature in ## Specs (dependency order), verify .kiro/specs/<feature>/brief.md exists
If any brief.md is missing, stop and report: "Missing brief.md for: [list]. Run $kiro-discovery to generate briefs first."

Step 2: Build Dependency Waves

Group pending features into waves based on dependencies:

Wave 1: Features with no dependencies (or all dependencies already completed [x])
Wave 2: Features whose dependencies are all in Wave 1 or already completed
Wave N: Features whose dependencies are all in earlier waves or already completed

Display the execution plan:

Spec Batch Plan:
  Wave 1 (parallel): app-foundation
  Wave 2 (parallel): block-editor, page-management
  Wave 3 (parallel): sidebar-navigation, database-views
  Wave 4 (parallel): cli-integration
  Total: 6 specs across 4 waves

If roadmap contains ## Existing Spec Updates or ## Direct Implementation Candidates, mention them separately as non-batch items so the user can see the whole decomposition.

Read the full file on GitHub · 166 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

agents/openai.yaml 131 B

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.

5d ago First seen · 166 lines · 31 tokens per session scan A 6b490abdbc17

Subscribe to this mod's changes

kiro-spec-batch is a skill published in the GitHub repository akaghef/M3E (11 stars, last pushed 5d ago), licensed MIT. It adds 31 tokens to every session and 1,994 once invoked, about $0.0001 per session on Opus 5.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-10-02.

Planning Project management

story-readiness

Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.

Donchitos/Claude-Code-Game-Studios · 35 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

M3E: Skill for Codex