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.
npx skills add DauQuangThanh/hanoi-rainbow --skill requirement-reviewgit clone --depth 1 https://github.com/DauQuangThanh/hanoi-rainbowWrote 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/dauquangthanh/hanoi-rainbow/requirement-review)<a href="https://agentmods.dev/skills/dauquangthanh/hanoi-rainbow/requirement-review"><img src="https://agentmods.dev/badge/skills/dauquangthanh/hanoi-rainbow/requirement-review/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/dauquangthanh/hanoi-rainbow/requirement-review"><img src="https://agentmods.dev/badge/skills/dauquangthanh/hanoi-rainbow/requirement-review.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.00115 | $0.01419 |
| Opus 5 | $0.00057 | $0.00709 |
| Sonnet 5 | $0.00023 | $0.00284 |
| Haiku 4.5 | $0.00012 | $0.00142 |
Grade A, and why
requirement-review 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirement Review
Systematically review requirements to validate quality and identify issues before design and development begins. Ensure requirements are complete, clear, consistent, testable, and traceable.
Review Workflow
1. Preparation
Gather all relevant documentation:
- Requirements documents (BRD, SRS, user stories)
- Non-functional requirements and constraints
- Requirements Traceability Matrix (if available)
- Project context (charter, goals)
- Existing acceptance criteria
2. Quality Assessment
Evaluate each requirement using six quality attributes:
- Completeness: All needs captured, no missing details or TBDs, dependencies identified
- Clarity: Unambiguous, specific, no vague terms ("user-friendly", "fast", "easy")
- Consistency: No conflicts, consistent terminology and priorities
- Testability: Verifiable with measurable acceptance criteria and clear pass/fail
- Traceability: Links to business goals, design, and tests
- Feasibility: Technically achievable within constraints (budget, timeline, capability)
See quality-checklists.md for detailed assessment criteria and document-specific checklists
3. Issue Identification
Identify common requirement problems:
Ambiguous: "system shall be fast" → Specify measurable criteria: "< 2s response for 95% of requests"
Untestable: "system shall be secure" → Define specific controls: password complexity, encryption standards, audit logging
Incomplete: "system shall send notifications" → Specify channel, timing, content, recipients
Conflicting: REQ-012 "phone required" vs REQ-089 "phone optional" → Flag for stakeholder resolution
See examples.md for extensive before/after examples
4. Quality Scoring
Calculate scores for each quality attribute (0-100%):
- 90-100%: Excellent - minimal issues
- 75-89%: Good - minor improvements needed
- 60-74%: Fair - notable gaps exist
- Below 60%: Poor - major rework required
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 145 lines · 115 tokens per session scan A dd4eb6ed34cd
requirement-review is a skill published in the GitHub repository DauQuangThanh/hanoi-rainbow (17 stars, last pushed 7mo ago), licensed MIT. It adds 115 tokens to every session and 1,419 once invoked, about $0.0006 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 skills, from other repositories
spec-driven-development
Spec-first workflow where an executable, testable specification is written before code and becomes the single source of truth that tests verify against, flowing spec → acceptance criteria → tasks → implementation.
implementation-standards
Reference material with coding standards (defensive coding, error handling, testing patterns). Loaded on demand by the Developer sub-agent (.github/agents/developer.md); not directly invokable.
clarification-strategies
Reference material with ambiguity-audit patterns and critique strategies for requirements. Loaded on demand by clarify-spec; not directly invokable.
universal-live-check
Universal live-check framework for coding agents. Executes incremental, deterministic validation across all software domains (CLI, backend, frontend, mobile, embedded, libs). Change-type-aware (feat, fix, hotfix, refactor, migrate, docs). Triggers whenever an agent needs to validate code quality, run linting, perform…
spec-driven-task-decomposer
Use this skill when approved requirements and design need to be decomposed into tasks.md for Phase 3 of a Spec-Driven change. It creates atomic, traceable implementation and testing tasks, validates the plan, and should not be used to design architecture or write implementation code.
test-forge
Generate comprehensive tests across all stacks — .NET, NestJS, React, React Native, Flutter.