brave-breakdown

Use this skill to guide a developer or designer through a BRAVE framework breakdown of a task before they start work. Trigger whenever someone wants to think through a ticket, break down a card, plan their approach before starting, validate a task before picking it up, or prepare a breakdown to share with a teammate or client. Also trigger for any of these phrases or close variations: "BRAVE this", "brave it", "break down this card", "think through this ticket", "help me plan this out before I start", "want to make sure I understand this before I start coding", "want to revalidate this card", "help me think through this before my standup/meeting", or "I'm about to pick up a card and want to break it down". If someone mentions starting work on a card and wants help planning, validating, or understanding it first — this skill should run.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%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 well-structured, actionable instruction skill with a clear phased workflow, explicit validation checkpoints, specific tooling, and a concrete output template supported by one-level-deep reference files. Only minor conciseness trims would improve it.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient instruction with concrete prompts, named tools, and a compact template; minor tone/philosophy phrasings ('not as a checklist, but as a genuine conversation', 'a clean synthesis') could be trimmed, placing it just below the lean level-5 anchor.	4 / 5
Actionability	Highly actionable for an instruction-only skill: names specific MCP tools (mcp__claude_ai_Linear__get_issue, mcp__claude_ai_Linear__list_issues), provides a ready-to-use breakdown document template, exact buffer guidance (15%, 32+ points), and concrete sample prompts.	5 / 5
Workflow Clarity	Clear three-phase sequence (Get oriented -> Brainstorm -> Reflect via AVE) with explicit checkpoints throughout: confirm framing before continuing, reflect back what was heard, transition only when grasp is solid, and a final 'does anything feel off' review before sharing.	5 / 5
Progressive Disclosure	SKILL.md is a clear overview with well-signaled, one-level-deep references (references/brave-framework.md, references/estimating.md, references/brave-craftsmanship.md), each cited at the relevant phase and verified as real files, with content appropriately split.	5 / 5
	Total	19 / 20 Passed

Description

91%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 thorough and explicit, clearly stating both the skill's purpose and an extensive set of natural trigger phrases. Its main weakness is mild verbosity and some overlap risk from generic planning phrasings, but it is a strong, well-targeted description.

Suggestions

Trim the redundant trigger phrase list to the most distinctive variations to reduce verbosity without losing coverage.

Lead with the BRAVE-specific framing more sharply so generic 'plan this out' phrasings are clearly scoped to card/ticket breakdown before starting work.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('guide a developer or designer through a BRAVE framework breakdown', 'think through a ticket', 'break down a card', 'plan their approach', 'validate a task', 'prepare a breakdown to share'), but they are largely facets of one core capability and the phrasing repeats, so it sits just below the comprehensive 5 anchor.	4 / 5
Completeness	Explicitly answers both what ('guide a developer or designer through a BRAVE framework breakdown of a task before they start work') and when (extensive concrete trigger phrases and situations), matching the level-5 anchor.	5 / 5
Trigger Term Quality	Comprehensive coverage of natural trigger phrases including synonyms and close variations ('BRAVE this', 'brave it', 'break down this card', 'think through this ticket', 'help me plan this out before I start', 'want to revalidate this card'), matching the level-5 anchor.	5 / 5
Distinctiveness Conflict Risk	The BRAVE framing and 'before I start work on a card' context give it a clear niche, but several trigger phrases ('help me plan this out before I start', 'think through this ticket') are generic enough to overlap with general planning skills, so it is mostly distinct with minor overlap risk.	4 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: RoleModel/rolemodel-skills
Path: skills/brave-breakdown/SKILL.md
Commit: 6695348

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.