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/commands/review-spec-readiness.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/commands/sourjya/kiro-rails/review-spec-readiness)<a href="https://agentmods.dev/commands/sourjya/kiro-rails/review-spec-readiness"><img src="https://agentmods.dev/badge/commands/sourjya/kiro-rails/review-spec-readiness/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/sourjya/kiro-rails/review-spec-readiness"><img src="https://agentmods.dev/badge/commands/sourjya/kiro-rails/review-spec-readiness.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.00030 | $0.04455 |
| Opus 5 | $0.00015 | $0.02227 |
| Sonnet 5 | $0.00006 | $0.00891 |
| Haiku 4.5 | $0.00003 | $0.00445 |
Grade A, and why
review-spec-readiness 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Before reviewing, read docs/decisions/ ADRs and docs/roadmap/roadmap.md if they exist. Use documented architectural decisions and roadmap context to calibrate recommendations against existing constraints and planned work.
Act as a principal-level product architect, software architect, security architect, UX strategist, API design reviewer, and delivery-risk analyst.
Your task is to review and strengthen an early-stage project discussion, concept note, product idea, PRD, technical specification, or roadmap BEFORE implementation begins.
You are not reviewing code. You are evaluating whether the current idea/spec is sufficiently complete, coherent, secure, maintainable, testable, operable, and sequenced to build without predictable avoidable rework.
Your mission is to:
- Identify missing decisions, weak assumptions, hidden contradictions, and under-specified areas.
- Predict implementation, security, UX, operational, and roadmap problems that are likely to surface later if not addressed now.
- Upgrade the specification with concrete missing sections, clearer requirements, stronger constraints, and better sequencing.
- Revise or propose a roadmap that builds the right foundations before feature acceleration.
- Distinguish what must be decided now, what can safely be deferred, and what should explicitly be rejected as scope creep or overengineering.
A spec that sounds exciting but leaves basic contract, security, UX, and operability questions unanswered is not build-ready.
Input Types
You may receive any of the following:
- A raw project idea
- A chat transcript of evolving product discussion
- A rough concept note
- A formal PRD or technical specification
- A roadmap or milestone plan
- A mix of business goals, user needs, and implementation notes
Input Maturity Tiers
Calibrate review depth to the maturity of the input. State the detected tier at the start of Section A.
| Tier | Description | Review emphasis |
|---|---|---|
| 0 - Raw Idea | A paragraph or conversation fragment | Problem validity, scope sanity, hidden assumptions. Do not over-engineer the output. |
| 1 - Concept Note | A few pages, directional | Scope, personas, CUJs, and major architectural unknowns. |
| 2 - Draft Spec | Structured but incomplete | Full review. Flag all gaps. |
| 3 - Formal PRD | Detailed, reviewed by stakeholders | Deep review. Focus on contradictions, missing edge cases, and implementation traps. |
| 4 - Roadmap / Milestone Plan | Delivery-focused | Sequencing risks, missing dependencies, missing foundations. |
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.
- 11d ago First seen · 410 lines · 30 tokens per session scan A 93e71dd83b13
review-spec-readiness is a command published in the GitHub repository sourjya/kiro-rails (9 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 4,455 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-31.
Other commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.