agentmods.dev

speckit.implement

An implementation command that follows a project's prepared task list and technical plan. It can require unfinished checklists to be confirmed and uses TDD, meaning tests are written before the code they check.

In plain words
What is it for?
Use it to carry out planned feature tasks, run the required checks, write tests first, implement the smallest solution, and report completed and remaining tasks.
Why use it?
It prevents implementation from skipping required planning, review steps, or unresolved specification issues. This makes progress and remaining work easier to track.

Command for Claude Code

34 9d ago A scan 34 tokens original MIT
View the source file akiojin/unity-mcp-server
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/akiojin/unity-mcp-server/speckit.implement
Clone the repo
git clone --depth 1 https://github.com/akiojin/unity-mcp-server

Made for: Claude Code.

Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 663 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.00034 $0.00663
Opus 5 $0.00017 $0.00331
Sonnet 5 $0.00007 $0.00133
Haiku 4.5 $0.00003 $0.00066

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

Security

Grade A, and why

speckit.implement 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.

.claude/commands/speckit.implement.md · 46 lines

What it actually says

ユーザー入力

$ARGUMENTS

空でない場合、続行する前にユーザー入力を考慮する必要があります。

実行手順

  1. リポジトリルートから .specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks を実行し、JSON出力から FEATURE_DIR と AVAILABLE_DOCS を取得します（パスは絶対パス）。

  2. チェックリスト状態を確認します（FEATURE_DIR/checklists/ が存在する場合）:

    • - [ ] / - [x] / - [X] の行数で Total/Completed/Incomplete を数える

    • 例のテーブルを作る:

      | Checklist | Total | Completed | Incomplete | Status |
|-----------|-------|-----------|------------|--------|
| requirements.md | 12 | 10 | 2 | ✗ FAIL |

    • Incomplete が1つでもある場合は停止し、次を確認する:

      • 「チェックリストが未完了です。実装を続行しますか？ (yes/no)」

    • ユーザーが no/stop/wait なら中断、yes/proceed/continue なら続行

  3. 実装コンテキストを読み込みます（必須/任意）:

    • 必須: tasks.md（タスク一覧と順序）
    • 必須: plan.md（技術スタック、構造、制約）
    • 存在すれば: data-model.md, contracts/, research.md, quickstart.md

  4. tasks.md を上から順に実行します:

    • 各タスクは「対象ファイル」「期待結果」「完了条件」を明確化してから着手
    • [P] タスクは、依存がなければ並列で進められる（ただし競合ファイルは避ける）
    • テストを含む場合は TDD を守る（テスト→失敗確認→最小実装→成功→整理）

  5. 実装中の注意:

    • 憲章（docs/constitution.md）に反する場合は、実装を止めて計画/タスク側を修正する
    • 不明点が顕在化したら、仕様（spec.md）へ [要明確化] を追加して戻す（必要なら /speckit.clarify を使う）

  6. 最後にユーザーへ、完了したタスクID/残タスク/次の推奨アクションを報告します。

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 · 46 lines · 34 tokens per session scan A 5008e58bad77

Subscribe to this mod's changes

speckit.implement is a command published in the GitHub repository akiojin/unity-mcp-server (34 stars, last pushed 9d ago), licensed MIT. It adds 34 tokens to every session and 663 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.

Game developmentPlanningTesting
Related

Other commands, from other repositories

cert-check

Review the current state against certification and platform compliance expectations.

MRCalderon3D/everything-game-dev-code · 11 tokens

combat-design

Design or revise combat rules, variables, readability, and tuning direction.

MRCalderon3D/everything-game-dev-code · 14 tokens

ui-flow-review

Review menus, HUD, navigation, and player flow from a UX perspective.

MRCalderon3D/everything-game-dev-code · 15 tokens

tech-debt

You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create actionable remediation plans.

HermeticOrmus/claude-code-game-development · 0 tokens

unity-optimize

Profile and optimize performance — uses MCP profiler for frame timing, memory, rendering stats. Identifies bottlenecks and applies fixes.

XeldarAlz/everything-claude-unity · 30 tokens

drift

Run the drift check and report the result. If it fails, identify which file has the stale reference and fix it.

undergroundrap/UEFN-TOOLBELT · 0 tokens