What is kiro-spec-status?

A skill that reports the current progress of a feature specification. It reads the available specification files and shows completed phases, missing work, blockers, and related dependency context.

For checking the status of a `.kiro/specs/ ` directory. It helps identify incomplete requirements, design, tasks, approvals, and upstream or downstream dependencies.

It removes the need to inspect several files manually to understand where specification work stands. It also highlights whether the specification is ready for the next phase.

How takumi0706/google-calendar-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to takumi0706/google-calendar-mcp. 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/takumi0706/google-calendar-mcp/main/.claude/skills/kiro-spec-status/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/takumi0706/google-calendar-mcp

Made for: Claude Code.

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/takumi0706/google-calendar-mcp/kiro-spec-status/github.svg)](https://agentmods.dev/skills/takumi0706/google-calendar-mcp/kiro-spec-status)

Your own site

<a href="https://agentmods.dev/skills/takumi0706/google-calendar-mcp/kiro-spec-status"><img src="https://agentmods.dev/badge/skills/takumi0706/google-calendar-mcp/kiro-spec-status/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/takumi0706/google-calendar-mcp/kiro-spec-status"><img src="https://agentmods.dev/badge/skills/takumi0706/google-calendar-mcp/kiro-spec-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 708 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00010	$0.00708
Opus 5	$0.00005	$0.00354
Sonnet 5	$0.00002	$0.00142
Haiku 4.5	$0.00001	$0.00071

Measured 12d ago against content hash 063979c17c12, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

kiro-spec-status 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 12d 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.

.claude/skills/kiro-spec-status/SKILL.md · 71 lines

How it starts

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

kiro-spec-status Skill

Core Mission

Success Criteria:
- Show current phase and completion status
- Identify next actions and blockers
- Provide clear visibility into progress
- Surface boundary readiness, upstream/downstream context, and likely revalidation needs when available

Execution Steps

Step 1: Load Spec Context

Read .kiro/specs/$ARGUMENTS/spec.json for metadata and phase status
Read .kiro/specs/$ARGUMENTS/brief.md if it exists
Read existing files: requirements.md, design.md, tasks.md (if they exist)
Check .kiro/specs/$ARGUMENTS/ directory for available files
Read .kiro/steering/roadmap.md if it exists and this spec appears in it

Step 2: Analyze Status

Parse each phase:

Requirements: Count requirements and acceptance criteria
Design: Check for architecture, components, diagrams, and whether boundary sections are present
Tasks: Count completed vs total tasks (parse - [x] vs - [ ])
Approvals: Check approval status in spec.json
Boundary context:
- From brief.md: note Boundary Candidates, Upstream / Downstream, and Existing Spec Touchpoints if present
- From design.md: note Boundary Commitments, Out of Boundary, Allowed Dependencies, and Revalidation Triggers if present
- From roadmap.md: note upstream dependencies and whether this spec is adjacent to Existing Spec Updates
Revalidation watchlist:
- Identify downstream specs, neighboring existing-spec updates, or rollout-sensitive design notes that may need revalidation if this spec changes
- Call out when the current spec shape looks too broad and may want roadmap/design splitting instead of more local repair

Step 3: Generate Report

Create report in the language specified in spec.json covering:

Current Phase & Progress: Where the spec is in the workflow
Completion Status: Percentage complete for each phase
Task Breakdown: If tasks exist, show completed/remaining counts
Boundary Context: Upstream/downstream, out-of-boundary, and allowed dependency notes when available
Revalidation Watchlist: Downstream or adjacent work likely affected by changes to this spec
Next Actions: What needs to be done next
Blockers: Any issues preventing progress

Read the full file on GitHub · 71 lines

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.

12d ago First seen · 71 lines · 10 tokens per session scan A 063979c17c12

Subscribe to this mod's changes

kiro-spec-status is a skill published in the GitHub repository takumi0706/google-calendar-mcp (59 stars, last pushed 25d ago), licensed MIT. It adds 10 tokens to every session and 708 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.

Planning

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

google-calendar-mcp: Skill for Claude Code