write-brd

Write a practical Business Requirements Document (BRD) from a product idea, feature concept, customer request, business problem, or rough product opportunity. Use when the user asks to write, draft, generate, refine, or save a BRD/business requirements document/product business case in Markdown, especially when the output should be saved under the current project's markdown directory and include diagrams using Mermaid, SVG, or ASCII.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a lean, well-structured instruction skill with a clear sequenced workflow, real one-level-deep references, and concrete output rules. Its only gap is that verification is a terminal step rather than an inline validate-and-retry loop.

Suggestions

Add an inline validation checkpoint between drafting and final save (e.g. re-check required sections against the Minimum BRD Sections list before writing the file) to turn step 7 from a post-hoc check into a feedback loop.

Surface the key template structure inline (the section headings or the one-line decision pattern) so Claude can draft without first opening assets/brd-template.md for routine cases.

Dimension	Reasoning	Score
Conciseness	Lean, decision-oriented prose with no padding of concepts Claude already knows; every section earns its place (e.g. 'Do not let "launch completed" stand in for "business value achieved"'), matching the level-5 'every token earns its place' anchor.	5 / 5
Actionability	Provides concrete executable guidance — exact file paths ('markdown/<topic>-BRD-<YYYYMMDD>.md'), SVG naming, and a specific success/stop-condition checklist — but as an instruction-only skill it has no copy-paste code; the guidance is actionable yet slightly short of the fully executable level-5 anchor.	4 / 5
Workflow Clarity	A clear 7-step workflow with an explicit verification step (7. Save and verify: confirm file/diagram/SVG existence and required sections) provides most checkpoints, but validation is concentrated at the end rather than as a per-step feedback loop, keeping it just below the level-5 anchor.	4 / 5
Progressive Disclosure	Clear overview in SKILL.md with well-signaled one-level-deep references to real bundle files ('Read assets/brd-template.md', 'read references/brd-writing-guide.md'), both verified to exist, matching the level-5 clear-overview-with-shallow-references anchor.	5 / 5
	Total	18 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, and complete with an explicit 'Use when' clause, while staking out a clear BRD-vs-PRD niche. It is strong overall, with only minor room to tighten the action enumeration toward a fully comprehensive list.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — 'Write... draft, generate, refine, or save a BRD/business requirements document/product business case' plus diagram output (Mermaid/SVG/ASCII) — but the action list is procedural rather than a tight enumeration, leaving minor coverage gaps versus the level-5 anchor.	4 / 5
Completeness	Explicitly answers 'what' (write a practical BRD) and 'when' with a concrete 'Use when the user asks to write, draft, generate, refine, or save...' clause, matching the level-5 anchor's both-what-and-when-with-trigger-phrases pattern.	5 / 5
Trigger Term Quality	Strong natural phrases users would actually say ('write, draft, generate, refine, or save a BRD', 'business requirements document', 'product business case'), with a few common synonyms missing, so it sits just below the comprehensive level-5 anchor.	4 / 5
Distinctiveness Conflict Risk	Clearly distinguishes BRD from PRD ('This skill writes BRDs, not PRDs') and uses distinct triggers tied to a narrow niche, giving minimal conflict risk consistent with the level-5 anchor.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: digoal/blog
Path: skills/write-brd/SKILL.md
Commit: 3b9c83d

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.