Borrowing it
Nothing to install: this file belongs to sourjya/kiro-rails. 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/sourjya/kiro-rails/main/.claude/skills/spec-implement/SKILL.mdgit clone --depth 1 https://github.com/sourjya/kiro-railsWrote 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/skills/sourjya/kiro-rails/spec-implement)<a href="https://agentmods.dev/skills/sourjya/kiro-rails/spec-implement"><img src="https://agentmods.dev/badge/skills/sourjya/kiro-rails/spec-implement/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/skills/sourjya/kiro-rails/spec-implement"><img src="https://agentmods.dev/badge/skills/sourjya/kiro-rails/spec-implement.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.00035 | $0.00462 |
| Opus 5.5 | $0.00014 | $0.00185 |
| Sonnet 5.5 | $0.00007 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
spec-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 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.
What it actually says
Spec Implement Workflow
Implement a feature that has an approved spec in .kiro/specs/<feature-name>/.
Steps
- Read the full spec - proposal.md, requirements.md, design.md, tasks.md
- Confirm readiness - all artifacts exist and tasks are defined
- Implement using TDD - for each task:
- RED: Write a failing test
- GREEN: Write minimal code to pass
- REFACTOR: Clean up while tests pass
- Check off tasks as completed in tasks.md
- Update design.md if implementation deviates from plan (document WHY)
Pre-Implementation Checklist
Before writing any code, verify:
-
proposal.mdexists and is approved (user confirmed) -
requirements.mdhas testable acceptance criteria -
design.mddescribes the approach -
tasks.mdhas atomic, ordered tasks - No open questions remain in proposal.md (or they've been answered)
Implementation Rules
- Follow task order - implement tasks in the sequence defined in tasks.md
- One task at a time - complete and verify each task before starting the next
- Mark progress - update
- [ ]to- [x]in tasks.md after each task passes tests - Stay in scope - if you discover needed work not in the spec, note it but don't implement it. Add it as a new task or flag it for a follow-up spec.
- Test against acceptance criteria - each requirement's criteria must have a corresponding test
- Document deviations - if the implementation differs from design.md, update design.md with the actual approach and rationale
Completion
When all tasks are checked off:
- Run the full test suite
- Verify all acceptance criteria in requirements.md are met
- Inform the user the spec is ready for verification (use
spec-verify)
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.
- 1mo ago First seen · 45 lines · 35 tokens per session scan A 0bab55ea91b9
spec-implement is a skill published in the GitHub repository sourjya/kiro-rails (9 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 462 once invoked, about $0.0001 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-31.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.