business-requirements-capture

Capture and refine business requirements into BRD-style documents with confidence markers.

5|3|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/richfrem/agent-plugins-skills --skill business-requirements-capture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: business-requirements-capture
Source: https://github.com/richfrem/agent-plugins-skills/tree/main/plugins/exploration-cycle-plugin/skills/business-requirements-capture
Command: npx skills add https://github.com/richfrem/agent-plugins-skills --skill business-requirements-capture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Captures and refines business requirements, including functional requirements, non-functional requirements, business rules, constraints, assumptions, and success measures. Produces structured BRD-style documents with [CONFIRMED] and [UNCONFIRMED] confidence markers. Trigger with "capture requirements", "generate a BRD", "document business rules", "list the constraints", or "create a requirements document".

Core Features & Use Cases

  • BRD generation from exploration captures — functional, non-functional, rules, constraints, assumptions, and success measures.
  • Ledgers for business rules and constraints to support governance and traceability.
  • Interactive co-authoring workflow with stage-based input gathering from stakeholders.

Quick Start

Provide your problem framing or captures and invoke the BRD workflow to generate the document.

Frequently Asked Questions about business-requirements-capture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture business requirements and turn them into a BRD?

To capture business requirements, use an interactive co-authoring workflow that gathers stakeholder input across functional, non-functional, rules, constraints, and assumptions to produce a structured BRD ready for review.

Can I document business rules and constraints separately from the main BRD?

Document business rules and constraints separately by generating specific ledgers for governance and traceability. The requirements capture workflow supports outputting dedicated rules ledgers alongside the primary BRD document.

How does an interactive workflow help refine stakeholder requirements?

An interactive workflow refines stakeholder requirements by using stage-gated sections to gather input progressively. This co-authoring approach validates problem framing and ensures all success measures are confirmed during discovery.

What's the best way to track unconfirmed assumptions during requirements capture?

Track unconfirmed assumptions during requirements capture by using [CONFIRMED] and [UNCONFIRMED] confidence markers within the generated BRD. This structured document approach highlights items needing further stakeholder validation.

Do I need prior documentation to start generating a business requirements document?

You do not need prior documentation to start generating a business requirements document. Simply provide your initial problem framing or verbal exploration captures to invoke the BRD workflow and begin the interactive input gathering.