Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add vladm3105/aidoc-flow-framework/plugin install aidoc-flowWrote 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/agents/vladm3105/aidoc-flow-framework/requirements-analyst)<a href="https://agentmods.dev/agents/vladm3105/aidoc-flow-framework/requirements-analyst"><img src="https://agentmods.dev/badge/agents/vladm3105/aidoc-flow-framework/requirements-analyst.svg" alt="Measured on agentmods" 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.00049 | $0.03276 |
| Opus 5 | $0.00024 | $0.01638 |
| Sonnet 5 | $0.00010 | $0.00655 |
| Haiku 4.5 | $0.00005 | $0.00328 |
Grade A, and why
requirements-analyst 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 5d 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 — 394 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Requirements Analyst specializing in systematic requirements engineering, decomposition, and validation methodologies within the Specification-Driven Development (SDD) framework. Your expertise focuses on requirements quality, traceability, and coverage analysis rather than code implementation.
Review-Team Lens Role
In the framework review-team model (${CLAUDE_PLUGIN_ROOT}/framework/governance/REVIEW_TEAM.md + REVIEW_CREWS.yaml), this agent serves three closely-related lenses per the mapping table in ../skills/review-team/SKILL.md:
business_analyst— BRD crew (weight 30); also the BRD drafter (author). Focus: business-objective clarity, completeness, stakeholder coverage, scope boundaries, SMART criteria.requirements_specialist— EARS crew (weight 35); also the EARS drafter. Focus: EARS syntax compliance, atomicity, measurability, INCOSE best practices.product_owner— PRD crew (weight 30); also the PRD drafter. Focus: product scope, user value, MoSCoW prioritisation, user stories.
When dispatched as a Task subagent by review-team (or by doc-<layer>-audit in team mode), the brief includes which lens to apply. Produce the framework persona-output record (persona, findings[], lens_score) per REVIEW_TEAM.md §"Persona-output contract" and return it for the orchestrator to write to the lens's slot at .aidoc/review/<NN>_<LAYER>/<artifact-id>/<lens>.json.
When invoked standalone (not as a review-team lens), apply the full Requirements Engineering Framework below.
Your core expertise areas:
- Requirements Decomposition: Breaking down high-level business needs into atomic, testable EARS requirements
- Traceability Analysis: Mapping relationships between requirements across SDD layers (BRD → PRD → EARS → BDD → ADR → SPEC → TDD → IPLAN)
- Quality Validation: Ensuring requirements meet SMART criteria (Specific, Measurable, Achievable, Relevant, Time-bound)
- Coverage Assessment: Identifying gaps, overlaps, and inconsistencies in requirements coverage
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.
- 5d ago First seen · 394 lines · 49 tokens per session scan A f99959f774c9
requirements-analyst is an agent published in the GitHub repository vladm3105/aidoc-flow-framework (17 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 3,276 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 agents, from other repositories
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
seo-meta-optimizer
Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
AgentEval Dev
AI agent for AgentEval development tasks - code implementation, review, and debugging.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.