brd

Generates a Business Requirement Document from a business plan using parallel agent teams.

4|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/VoxTechnologies/transmute-framework --skill brd-voxtechnologies
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brd
Source: https://github.com/VoxTechnologies/transmute-framework/tree/main/skills/brd
Command: npx skills add https://github.com/VoxTechnologies/transmute-framework --skill brd-voxtechnologies

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing a comprehensive Business Requirement Document from a business plan is slow, error-prone, and often misses features buried in roadmap or future-phase sections. This Skill automates Stage 1 of the Transmute pipeline by coordinating five specialized agent teams to produce a complete, traceable, full-scope BRD. ## Core Features & Use Cases - Full-Scope Feature Extraction: Sweeps the business plan for every feature, including items labeled future, roadmap, or Phase 2/3, and builds a master feature inventory with deduplication rules. - Parallel Agent Generation: Spawns five domain-specialized teammates (business-core, technical-infrastructure, data-and-integration, user-experience-and-operations, risk-and-planning) to produce 23 numbered BRD files with unique requirement ID ranges. - Multi-Agent Quality Review: Runs completeness, consistency, and technical review agents, then remediates CRITICAL and HIGH findings with a logged review trail. - Use Case: A founder places a business plan in plancasting/businessplan/ and runs Stage 1 to receive 26 markdown files covering functional, non-functional, security, data, integration, and compliance requirements with MoSCoW priorities and mermaid diagrams. ## Quick Start Generate the BRD from my business plan in plancasting/businessplan/ by running Stage 1.

Frequently Asked Questions about brd

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

FAQPage Schema
How do I generate a BRD from a business plan?

Place your business plan files (.md or .pdf) in ./plancasting/businessplan/ and ensure plancasting/tech-stack.md exists from Stage 0. Then ask to generate the BRD or run Stage 1, and the skill coordinates agent teams to produce 26 markdown files in ./plancasting/brd/.

What files does the BRD generation produce?

It produces 23 numbered specification files (00 through 22) covering business, functional, non-functional, data, integration, security, compliance, and risk requirements, plus _context.md, _review-log.md, and a README.md navigation hub, totaling 26 files.

Does the BRD include features marked as future or Phase 2 in my plan?

Yes. The skill uses a full-build approach: all features described in the business plan are treated as in-scope regardless of phasing labels like future, roadmap, or Phase 2/3. Only features explicitly marked out-of-scope are excluded.

What happens if the business plan is too thin to derive requirements?

The skill counts assumption blockquotes against total requirement IDs. If assumptions reach 30% or more of requirements, it flags the result as CRITICAL and recommends remediating the business plan before proceeding to Stage 2.

Why did a teammate agent produce truncated BRD files?

Each agent has an output token limit, and large files like 07-functional-requirements.md can exceed it. The lead re-spawns the agent with reduced scope or splits the file by feature group with unique ID ranges, then merges outputs during integration.