Tessl • The management layer for AI agent skills

SkillPublic

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

88%

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

78%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.

A well-structured instruction-only skill: an efficient, imperative overview with concrete naming conventions, a sequenced workflow ending in verification, and clean one-level-deep pointers to a real template and guide. The main gaps are the absence of an explicit error-recovery loop in the verify step and a few directional passages that could be made more concrete.

Suggestions

In step 7 (Save and verify), add a short error-recovery loop, e.g. "If any check fails, fix the file and re-verify before reporting to the user," to reach the top workflow-clarity anchor.

Make the "Evidence Rules" more actionable by specifying what to do when verification is inconclusive (e.g., mark the claim as an assumption in the Open Questions section) instead of the directional "browse or otherwise verify with reliable sources".

Tighten the "Good diagram choices" bullet list by folding it into the diagram guidance in references/brd-writing-guide.md to reduce inline duplication.

Dimension	Reasoning	Score
Conciseness	The body is lean and imperative with no padding of concepts Claude already knows (e.g., "Use tables for structured scope, metrics, risks" rather than explaining what a table is), but a few spots could be tightened, such as the enumerated "Good diagram choices" list and restatements like "Do not let 'launch completed' stand in for 'business value achieved'".	4 / 5
Actionability	Guidance is concrete for an instruction-only skill: exact file patterns ("markdown/<topic>-BRD-<YYYYMMDD>.md", "figure-1-<topic>-BRD-<YYYYMMDD>.svg"), a decision chain template, a 13-section minimum list, and an explicit verification checklist — but steps like "browse or otherwise verify with reliable sources" and the lens descriptions remain directional rather than fully specified.	4 / 5
Workflow Clarity	A clear 7-step sequence culminates in an explicit "Save and verify" step with a checklist (confirm file exists, diagram exists, SVG exists, required sections present, report path and assumptions). It stops short of the top anchor because there is no error-recovery loop stating what to do when a verification check fails.	4 / 5
Progressive Disclosure	The body is a well-organized overview that signals exactly two one-level-deep references — "Read `assets/brd-template.md` when drafting" and "For extra guidance... read `references/brd-writing-guide.md`" — both of which exist in the bundle, and neither file nests further references, so navigation is clean and appropriately split.	5 / 5
	Total	17 / 20 Passed

Description

95%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.

A strong description: third-person voice, explicit what and when clauses, rich synonym coverage, and distinctive BRD-specific triggers. Its only limitation is that the action list centers on a single deliverable rather than multiple distinct capabilities.

Dimension	Reasoning	Score
Specificity	Concrete actions are named ("Write a practical Business Requirements Document (BRD)", "write, draft, generate, refine, or save") along with concrete output specifics ("saved under the current project's markdown directory and include diagrams using Mermaid, SVG, or ASCII"), but all verbs serve a single deliverable, so coverage has minor gaps versus the comprehensive multi-action anchor.	4 / 5
Completeness	Both parts are explicit: the what ("Write a practical Business Requirements Document (BRD) from a product idea, feature concept, customer request, business problem, or rough product opportunity") and the when ("Use when the user asks to write, draft, generate, refine, or save a BRD/business requirements document/product business case in Markdown") with concrete trigger phrases and output-location guidance.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage with synonyms: "BRD", "business requirements document", "product business case", "write, draft, generate, refine, or save", "Markdown", "markdown directory", and "Mermaid, SVG, or ASCII" — these are exactly the phrases a user would naturally say.	5 / 5
Distinctiveness Conflict Risk	Clear niche (BRD/business-case writing with a distinct Markdown-output-and-diagram trigger) that is unlikely to fire for generic document or PRD skills; trigger terms like "BRD", "business requirements document", and "product business case" are distinctive.	5 / 5
	Total	19 / 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
Revision: 7abecbf

Reviewed: 28 days ago

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.

write-brd

Table of Contents

Is this your skill?