Requirements Engineer — Development agent for Claude Code
Refines feature ideas into detailed specs with user stories, acceptance criteria, and edge cases.
How to install Requirements Engineer
Installs to ~/.claude/agents/dagonet-open-brain-requirements-engineer.md
mkdir -p ~/.claude/agents && curl -fsSL https://raw.githubusercontent.com/dagonet/open-brain/HEAD/.claude/agents/requirements-engineer.md -o ~/.claude/agents/dagonet-open-brain-requirements-engineer.md Restart Claude Code, or start a new session, for it to be picked up.
What Requirements Engineer does
name: requirements-engineer description: Refines feature ideas into detailed specs with user stories, acceptance criteria, and edge cases. Does NOT write code. model: sonnet effort: medium tools: Read, Grep, Glob, Skill
You are a requirements engineer. You transform rough feature ideas into detailed, implementable specifications.
Responsibilities
- Feature Specification: Take a feature idea or rough description and produce a complete spec containing:
- Summary: One-para
Alternatives in Development
- Gitnexus Docs Dod Reviewer — GitNexus docs and Definition-of-Done reviewer 45.8k ★
- PRD Reviewer — Review a PRD and flag missing acceptance criteria, edge cases, and 135 ★
- Product Owner Proxy — Define business intent as user stories with clear acceptance criteria and measurable outcomes 108 ★
Full documentation available on GitHub
View Source RepositoryRelated Agents
Requirements Agent
Surfaces ambiguities, missing edge cases, and undefined behaviors before development begins. Produces a Featur
Specresearcher
Use this agent when you need to transform vague product ideas or feature requests into detailed, implementatio
Issue Refiner
Enriches issues with acceptance criteria, edge cases, technical considerations, and NFRs. Use before assigning
PM Expert
Product management expert for requirements gathering, user stories, acceptance criteria, and scope decisions.
Story Generator
Use this agent when you need to generate user stories with acceptance criteria from various inputs like git di
Sdlc PM
Produces a PRD (epics, user stories with acceptance criteria, prioritization, non-functional requirements) fro
Related Skills
Spec Specify
Phase 1 — Creates the detailed technical specification of a feature: functional requirements, non-functional r
Ac Validation
Review Acceptance Criteria for one or more user stories against completeness and quality standards. Checks hap
Amby.Specify
Turn a feature idea into a spec — user stories, EARS requirements, acceptance criteria.