ccmanager: Command for Claude Code

.claude/commands/kiro/spec-init.md

spec-init is a command for Claude Code from kbwo/ccmanager. It costs 10 tokens per session (616 once invoked), scanned A, original, MIT.

A command that starts a new project specification from a detailed description and requirements. It creates a named folder with project metadata and an initial requirements document.

In plain words
What is it for?
Starting feature specifications, recording the project description, and preparing files for later design and task planning.
Why use it?
It gives a new feature a consistent starting structure and checks that its name does not conflict with an existing specification.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md.

This is kbwo/ccmanager's own configuration. It tells Claude Code how to work on ccmanager itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ccmanager configures →

About the project

CCManager is a command-line application for managing multiple sessions of AI coding assistants across Git worktrees and projects. It is for developers working with tools such as Claude Code, Gemini CLI, Codex CLI, Cursor Agent, Copilot CLI, Cline CLI, OpenCode, and Kimi CLI, and the catalogue entries provide commands and instructions for its workflows.

kbwo/ccmanager · 1,266 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to kbwo/ccmanager. 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/kbwo/ccmanager/main/.claude/commands/kiro/spec-init.md
Clone the repo
git clone --depth 1 https://github.com/kbwo/ccmanager

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.

agentmods badge for spec-init

README.md
[![agentmods](https://agentmods.dev/badge/commands/kbwo/ccmanager/spec-init/github.svg)](https://agentmods.dev/commands/kbwo/ccmanager/spec-init)
Your own site
<a href="https://agentmods.dev/commands/kbwo/ccmanager/spec-init"><img src="https://agentmods.dev/badge/commands/kbwo/ccmanager/spec-init/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.

agentmods 80×15 button for spec-init

Your own site · 80×15
<a href="https://agentmods.dev/commands/kbwo/ccmanager/spec-init"><img src="https://agentmods.dev/badge/commands/kbwo/ccmanager/spec-init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 616 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00010 $0.00616
Opus 5.5 $0.00004 $0.00246
Sonnet 5.5 $0.00002 $0.00123
Haiku 4.5 $0.00001 $0.00062

Measured 1mo ago against content hash f520df2500df, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

spec-init 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 1mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • spec-init — 100% identical, 3 lines differ
.claude/commands/kiro/spec-init.md · 86 lines

How it starts

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

Spec Initialization

Initialize a new specification based on the provided project description:

Project Description: $ARGUMENTS

Task: Initialize Specification Structure

SCOPE: This command initializes the directory structure and metadata based on the detailed project description provided.

1. Generate Feature Name

Create a concise, descriptive feature name from the project description ($ARGUMENTS). Check existing .kiro/specs/ directory to ensure the generated feature name is unique. If a conflict exists, append a number suffix (e.g., feature-name-2).

2. Create Spec Directory

Create .kiro/specs/[generated-feature-name]/ directory with:

  • spec.json - Metadata and approval tracking
  • requirements.md - Lightweight template with project description

Note: design.md and tasks.md will be created by their respective commands during the development process.

3. Initialize spec.json Metadata

Create initial metadata with approval tracking:

{
  "feature_name": "[generated-feature-name]",
  "created_at": "current_timestamp",
  "updated_at": "current_timestamp",
  "language": "en",
  "phase": "initialized",
  "approvals": {
    "requirements": {
      "generated": false,
      "approved": false
    },
    "design": {
      "generated": false,
      "approved": false
    },
    "tasks": {
      "generated": false,
      "approved": false
    }
  },
  "ready_for_implementation": false
}

4. Create Requirements Template

Create requirements.md with project description:

# Requirements Document

## Project Description (Input)
$ARGUMENTS

## Requirements
<!-- Will be generated in /kiro:spec-requirements phase -->

5. Update CLAUDE.md Reference

Add the new spec to the active specifications list with the generated feature name and a brief description.

Next Steps After Initialization

Follow the strict spec-driven development workflow:

  1. /kiro:spec-requirements <feature-name> - Create and generate requirements.md
  2. /kiro:spec-design <feature-name> - Create and generate design.md (requires approved requirements)
  3. /kiro:spec-tasks <feature-name> - Create and generate tasks.md (requires approved design)

Read the full file on GitHub · 86 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.

  1. 1mo ago First seen · 86 lines · 10 tokens per session scan A f520df2500df

Subscribe to this mod's changes

spec-init is a command published in the GitHub repository kbwo/ccmanager (1,266 stars, last pushed 3d ago), licensed MIT. It adds 10 tokens to every session and 616 once invoked, about $0.0000 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-08-30.