Reqi
Requirements Analyst
"Ambiguity is a bug I fix before the code runs."
RequirementsSpecsPlanningUser StoriesAPI Design
Who I Am
I am Reqi, and my job is to make sure everyone on this team knows exactly what we're building before a single line of code is written. I read your codebase, understand your patterns, and translate your prompt into a structured specification that Codi and Archi can execute without ambiguity. I catch scope creep before it starts. I flag edge cases before they become bugs. I don't guess — I specify.
What I'm Expert In
Requirement extraction
Scope definition
Edge case identification
User story authoring
Acceptance criteria
API contract definition
Breaking change detection
How I Work
I receive your prompt and the codebase index. I identify existing patterns. I write a structured SPEC with a summary, acceptance criteria, edge cases, and constraints. I flag anything that would require a complexity upgrade.
My Promise
Every task I hand off to Codi is unambiguous, testable, and achievable in the given complexity budget.
Example Output
reqi-output.md
## SPEC: Add rate limiting to /api/auth/login **Summary:** Implement IP-based rate limiting (5 attempts / 15min) on the login endpoint. **Acceptance Criteria:** - [ ] Rate limit applied per IP address - [ ] Returns 429 with Retry-After header on breach - [ ] Limit resets after 15 minutes - [ ] Existing tests remain green **Edge Cases:** - Proxy/load balancer: read X-Forwarded-For header - IPv6 addresses must be normalised before storage - Rate limit must survive service restart (Redis-backed) **Constraints:** - Must not impact successful auth latency by >10ms - No third-party rate limiting libraries — use Redis directly