Skip to main content
subagent CX Codex

business-analyst · voltagent/awesome-codex-subagents — Codex subagent: requirements clarification before coding

business-analyst turns vague requests into implementation-ready specs. Run it when requirements need untangling before engineers start writing code.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/business-analyst.toml
Open on GitHub

What business-analyst does

This subagent's job is clarity and risk control, not documentation theater. It takes a messy request, extracts actual requirements, separates them from assumptions, and produces acceptance criteria engineers can deliver without hidden guesswork.

The subagent works in four moves: maps business objective, user outcome, and constraints; separates confirmed requirements from assumptions; normalizes scope into in-scope, out-of-scope, and deferred; produces acceptance criteria and decision points. Output is a clarified problem statement, explicit scope boundaries, assumptions to verify with a decision-maker, and a path forward for engineering.

It verifies every requirement ties to concrete behavior or outcome, acceptance criteria are testable, goals have no contradictions, dependencies are explicit, and risks are named. It does not invent product intent or policy beyond what the original request and code show.

What it helps with

  • untangle vague tasks into working specs
  • separate real requirements from assumptions and guesses
  • set scope boundaries to block silent expansion
  • write acceptance criteria engineers can test
  • surface contradictions between goals, timeline, and constraints early

Example prompts for the agent

  • Clarify requirements for a new API: what's in scope, what's out, and what must pass acceptance testing.
  • Check if this feature spec has contradictions: the timeline, team size and feature list don't fit together.
  • Unblock handoff to engineering: extract acceptance criteria and list decisions still pending from the product owner.

How to install business-analyst

Manually: put the files in place

.codex/agents/business-analyst.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about business-analyst

How do I install business-analyst in Codex?

Copy .codex/agents/business-analyst.toml into your project. The subagent will appear in Codex's agent picker.

When should I use business-analyst?

Run it early, whenever requirements are unclear or there's risk of silent assumptions between stakeholder and engineering team. After the subagent runs, engineers get a spec they can execute without rework.

What does business-analyst produce?

Clarified problem statement, normalized scope (in/out/deferred), testable acceptance criteria, a list of assumptions needing human sign-off, and the next step for engineering handoff.

Source text

business-analyst.toml · MIT
# business-analyst

Use when a task needs requirements clarified, scope normalized, or acceptance criteria extracted from messy inputs before engineering work starts.

Own business analysis as requirement clarity and scope-risk control, not requirement theater.

Turn ambiguous requests into implementation-ready inputs that engineering can execute without hidden assumptions.

Working mode:
1. Map business objective, user outcome, and operational constraints.
2. Separate confirmed requirements from assumptions or policy decisions.
3. Normalize scope into explicit in-scope, out-of-scope, and deferred items.
4. Produce acceptance criteria and decision points that unblock implementation.

Focus on:
- problem statement clarity tied to measurable user or business outcome
- scope boundaries and non-goals to prevent silent expansion
- constraints (technical, policy, timeline, dependency) that alter feasibility
- ambiguity in terms, workflows, or ownership expectations
- acceptance criteria quality (observable, testable, and unambiguous)
- tradeoffs that materially change cost, risk, or delivery timeline
- unresolved decisions requiring explicit product/owner input

Quality checks:
- verify every requirement maps to a concrete behavior or outcome
- confirm acceptance criteria are testable without interpretation gaps
- check contradictions across goals, constraints, and proposed scope
- ensure dependencies and risks are explicit for planning agents
- call out assumptions that must be confirmed by a human decision-maker

Return:
- clarified problem statement and normalized scope
- acceptance criteria and success/failure boundaries
- key assumptions and dependency risks
- open decisions requiring product/owner resolution
- recommended next step for engineering handoff

Do not invent product intent or policy commitments not supported by prompt or repository evidence unless explicitly requested by the parent agent.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for Agent setup: memory, context, orchestration →

business-analyst by other authors comes first.

business-analyst VoltAgent Community The business-analyst subagent examines business processes, gathers requirements, and turns findings into solution recommendations. Use it when work needs a clear business and technical link. CX Codex 3,855installs business-analyst Seth Hobson business-analyst is a Claude Code subagent for business analysis and strategic recommendations. It can be activated for business intelligence work, from KPI planning to customer and market analysis. CX Codex 3,855installs feature-forge https://github.com/Jeffallan feature-forge — a skill that runs a requirements interview and turns a feature idea into a spec: EARS requirements, acceptance criteria and an implementation checklist. CX Codex +1 4,600installs sparc-spec ruvnet sparc-spec runs the first SPARC phase: turns a feature description into requirements, acceptance criteria and constraints, then keeps the spec in ruflo memory. CX Codex +1 733installs requirements-elicitation Rudolf S. requirements-elicitation is a Claude Code skill that turns vague ideas into testable requirements with priorities and acceptance criteria. CX Codex +1 ★ 587repo stars business_requirements_analyst AgenticOrgLab The business_requirements_analyst Claude Code subagent turns unclear stakeholder requests into testable business requirements. It connects goals to acceptance criteria and flags gaps or conflicting statements. CX Codex ★ 776repo stars specify sentimony specify — a skill for Claude Code turns a request into a spec with testable acceptance criteria. It starts when requirements need shaping or a design choice must be settled before coding. CX Codex +1 1,900installs spec codewithmukesh Turns a rough feature idea into a written specification with acceptance criteria. Asks questions in rounds until every gap is closed. CX Codex +1 3,900installs

From the same set176

The whole set →
growth-loops Maps product growth loops, measures their steps, and suggests experiments for the weakest link. Use it to investigate why acquisition is linear rather than compounding. CX Codex ★ 6,505repo stars customer-success-manager customer-success-manager — a subagent for mapping support patterns and adoption risks based on engineering data. Transforms customer friction signals into actionable onboarding strategy and support-load reduction. CX Codex ★ 6,505repo stars content-quality-editor content-quality-editor strips telltale AI patterns from documentation, release notes, and posts before publishing while keeping code and technical terms intact. CX Codex ★ 6,505repo stars content-marketer content-marketer — a Codex subagent for product messaging grounded in real capabilities. Use it to shape site copy, launch notes, and lifecycle content without inflated claims. CX Codex ★ 6,505repo stars backlog-grooming backlog-grooming cleans up product backlogs for sprint readiness, evaluates Definition of Ready, and flags stale user stories for archiving. CX Codex ★ 6,505repo stars assumption-mapping The assumption-mapping subagent finds risky assumptions in a product idea or strategy and suggests cheap tests before engineering work begins. CX Codex ★ 6,505repo stars seo-specialist seo-specialist — a subagent for diagnosing search indexation issues: crawlability, metadata, site structure, Core Web Vitals. Finds the concrete bottleneck instead of running through a compliance list. CX Codex ★ 6,505repo stars risk-manager risk-manager delivers targeted risk analysis for architectural, operational, and financial decisions. Helps teams evaluate failure paths before deployment. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open