agentmods.dev

kairo-requirements

A requirements-writing command that turns a feature overview into a detailed specification using EARS, a structured way to describe software requirements and their conditions. It can also define user stories, acceptance criteria, non-functional requirements, and edge cases.

In plain words
What is it for?
Use it to prepare a feature specification from a user-provided summary and optional product-requirements document, with the amount of detail chosen for the project.
Why use it?
It turns an incomplete feature idea into clearer requirements that developers and testers can use.

Command

974 26d ago A scan 48 tokens original MIT
View the source file classmethod/tsumiki
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/classmethod/tsumiki/kairo-requirements
Clone the repo
git clone --depth 1 https://github.com/classmethod/tsumiki
Per session 48 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 11,236 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00048 $0.11236
Opus 5 $0.00024 $0.05618
Sonnet 5 $0.00010 $0.02247
Haiku 4.5 $0.00005 $0.01124

Measured 2d ago against content hash 2e6caf733cf1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

kairo-requirements 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 2d 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.

legacy/commands/kairo-requirements.md · 1,062 lines

How it starts

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

Kairo開発の要件整理を実施し、PRD・EARS要件定義書・設計文書を参照しながら機能仕様を明確化します。信頼性レベルを示しながら要件定義を作成します。

context

出力ディレクトリ="docs/spec" 要件名={{requirement_name}} PRDファイル={{prd_file_path}} 作業規模={{work_scope}} 信頼性評価=[]

step

  • $ARGUMENTS がない場合、「引数に要件名を指定してください（例: ユーザー認証システム）。PRDファイルがあればパスも指定してください（例: ユーザー認証システム docs/prd/auth-prd.md）」と言って終了する
  • $ARGUMENTS の内容と context の内容をまとめてユーザに宣言する
  • step2 を実行する

step2: 作業規模の確認

  • AskUserQuestion ツールを使って作業規模を質問する：

    • question: "この要件の作業規模について教えてください"
    • header: "作業規模"
    • multiSelect: false
    • options:
      • label: "フル機能開発（推奨）" description: "詳細なEARS要件定義、包括的なユーザーストーリー、完全な受け入れ基準、非機能要件・エッジケース含む"
      • label: "軽量開発" description: "必要最小限の要件定義、基本的なユーザーストーリーのみ、主要な受け入れ基準のみ、非機能要件は最低限"
      • label: "カスタム" description: "含めたい項目を個別に選択"

  • ユーザーの選択を context の {{work_scope}} に保存

  • カスタムを選択した場合は、AskUserQuestion ツールを使って以下を質問：

    • question: "要件定義書に含める項目を選択してください（複数選択可）"
    • header: "含める項目"
    • multiSelect: true
    • options:
      • label: "詳細なユーザーストーリー" description: "包括的なユーザーストーリーを作成"
      • label: "非機能要件の詳細化" description: "パフォーマンス・セキュリティ等の詳細な非機能要件"
      • label: "エッジケースの洗い出し" description: "エラー処理・境界値等のエッジケース"
      • label: "パフォーマンス要件" description: "詳細なパフォーマンス要件の定義"

  • step3 を実行する

step3: 開発コンテキストの準備

  • タスクノートの読み込み

    • docs/spec/{要件名}/note.md が存在する場合は読み込み
    • 存在しない場合:
      • Task ツールを使用して subagent_type: "general-purpose" で /tsumiki-legacy:kairo-tasknote {要件名} コマンドを実行してノートを生成
      • 生成されたノートファイルを読み込み
    • ノートには技術スタック、開発ルール、関連実装、設計文書、注意事項が含まれる

  • PRDファイルの読み込み（引数で指定された場合）

    • {{prd_file_path}} が指定されている場合は読み込み
    • PRD（Product Requirements Document）には以下が含まれることを期待：
      • プロダクトビジョン
      • ターゲットユーザー
      • 主要機能
      • ビジネス要件
      • 成功指標

  • 追加ルールの読み込み

    • docs/rule ディレクトリが存在する場合は読み込み
    • docs/rule/kairo ディレクトリが存在する場合は読み込み
    • docs/rule/kairo/requirements ディレクトリが存在する場合は読み込み
    • 各ディレクトリ内のすべてのファイルを読み込み、追加ルールとして適用

  • プロジェクト基本情報収集

    • CLAUDE.md の内容を読み込み（プロジェクト概要・技術スタック・制約）
    • README.md が存在する場合は読み込み
    • プロジェクト構造（ディレクトリ構成）を把握

Read the full file on GitHub · 1,062 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. 2d ago First seen · 1,062 lines · 48 tokens per session scan A 2e6caf733cf1

Subscribe to this mod's changes

kairo-requirements is a command published in the GitHub repository classmethod/tsumiki (974 stars, last pushed 26d ago), licensed MIT. It adds 48 tokens to every session and 11,236 once invoked, about $0.0002 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
Related

Other commands, from other repositories

git

Git operations with intelligent commit messages and workflow optimization.

SuperClaude-Org/SuperClaude_Framework · 11 tokens

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

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.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

constitution

Create or update the project constitution from interactive or provided principle inputs.

github/spec-kit · 13 tokens