Borrowing it
Nothing to install: this file belongs to gaoconggit/SharpPad. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gaoconggit/SharpPad/main/.claude/commands/kiro/spec-impl.mdgit clone --depth 1 https://github.com/gaoconggit/SharpPadWrote 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.
[](https://agentmods.dev/commands/gaoconggit/sharppad/spec-impl)<a href="https://agentmods.dev/commands/gaoconggit/sharppad/spec-impl"><img src="https://agentmods.dev/badge/commands/gaoconggit/sharppad/spec-impl/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.
<a href="https://agentmods.dev/commands/gaoconggit/sharppad/spec-impl"><img src="https://agentmods.dev/badge/commands/gaoconggit/sharppad/spec-impl.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00007 | $0.00556 |
| Opus 5.5 | $0.00003 | $0.00222 |
| Sonnet 5.5 | $0.00001 | $0.00111 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade A, and why
spec-impl 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 13d 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.
This is a copy
100% identical to spec-impl — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Execute Spec Tasks with TDD
Execute implementation tasks for $1 using Kent Beck's Test-Driven Development methodology.
Instructions
Pre-Execution Validation
Validate required files exist for feature $1:
- Requirements:
.kiro/specs/$1/requirements.md - Design:
.kiro/specs/$1/design.md - Tasks:
.kiro/specs/$1/tasks.md - Metadata:
.kiro/specs/$1/spec.json
Context Loading
Core Steering:
- Structure: @.kiro/steering/structure.md
- Tech Stack: @.kiro/steering/tech.md
- Product: @.kiro/steering/product.md
Custom Steering:
- Additional
*.mdfiles in.kiro/steering/(excluding structure.md, tech.md, product.md)
Spec Documents for $1:
- Metadata: @.kiro/specs/$1/spec.json
- Requirements: @.kiro/specs/$1/requirements.md
- Design: @.kiro/specs/$1/design.md
- Tasks: @.kiro/specs/$1/tasks.md
Task Execution
- Feature: $1
- Task numbers: $2 (optional, defaults to all pending tasks)
- Load all context (steering + spec documents)
- Execute selected tasks using TDD methodology
TDD Implementation
For each selected task:
- RED: Write failing tests first
- GREEN: Write minimal code to pass tests
- REFACTOR: Clean up and improve code structure
- Verify:
- All tests pass
- No regressions in existing tests
- Code quality and test coverage maintained
- Mark Complete: Update checkbox from
- [ ]to- [x]in tasks.md
Note: Follow Kent Beck's TDD methodology strictly, implementing only the specific task requirements.
Implementation Notes
- Feature: Use
$1for feature name - Tasks: Use
$2for specific task numbers (optional) - Validation: Check all required spec files exist
- TDD Focus: Always write tests before implementation
- Task Tracking: Update checkboxes in tasks.md as completed
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.
- 13d ago First seen · 63 lines · 7 tokens per session scan A 731f5790f9b1
spec-impl is a command published in the GitHub repository gaoconggit/SharpPad (83 stars, last pushed 7mo ago), licensed MIT. It adds 7 tokens to every session and 556 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to spec-impl, differing in 1 line, and is treated as a copy.
Other commands, from other repositories
bug-fix-tdd
Fix a bug using TDD: reproduce with a failing test first, then implement the fix, then verify. Prevents regressions.
proof-driven-development
A disciplined workflow for ambiguous, high-stakes tasks — assess, post proof-tagged assumptions, lock a testable goal, plan as TDD, build via subagents with two-stage review, prove with a live end-to-end run, and flag gaps honestly. Use when starting a vague ticket or a feature that touches auth, identity, money, or…
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.
speckit.tdd.plan
Derive the feature's test list by delegating to zfa tdd plan (deterministic engine); falls back to LLM-guided derivation only when zfa is unavailable.