CtrlK
BlogDocsLog inGet started
Tessl Logo

bmad-document-project

Document brownfield projects for AI context. Use when the user says "document this project" or "generate project docs"

74

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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

A tightly written, actionable activation workflow with clear sequencing and a verification checkpoint. The main weakness is progressive disclosure: the core detail is delegated to ./instructions.md, which is not present in the bundle, leaving a dead reference.

Suggestions

Include the referenced ./instructions.md (or place it under references/) so the primary delegated content actually exists in the bundle.

For the fallback merge procedure, consider moving the detailed base->team->user merge rules into a short reference note to keep the activation section even leaner.

Add a one-line note clarifying that the {project-root}/_bmad/* paths are external to the skill bundle, so readers do not expect them under the skill root.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no concept explanations or padding — with every section (conventions, activation steps, config loading) earning its place; the dense merge rules are necessary procedural detail, not fluff.

3 / 3

Actionability

It gives concrete executable guidance: an exact resolve script invocation ('python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow') plus a precise ordered fallback (three named files in base->team->user order with explicit merge rules).

3 / 3

Workflow Clarity

The activation process is a clearly sequenced Step 1-6 workflow with an explicit failure fallback and a final verification checkpoint ('confirm every entry was executed in order before proceeding'), matching the level-3 anchor.

3 / 3

Progressive Disclosure

Sections are well-organized and the main reference ('Read fully and follow: ./instructions.md') is clearly signaled, but that referenced file is absent from the bundle (no references/scripts/assets dirs exist), so the one-level-deep pointer is to a missing target.

2 / 3

Total

11

/

12

Passed

Description

90%

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 concise, well-formed description that clearly states both what the skill does and when to use it via natural quoted triggers. The only weakness is that it names a single action rather than enumerating multiple concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain ('brownfield projects for AI context') and the action ('Document'), but lists only a single action rather than multiple concrete capabilities, so it falls short of the level-3 anchor.

2 / 3

Completeness

It explicitly answers both 'what' (Document brownfield projects for AI context) and 'when' via an explicit 'Use when...' clause with quoted triggers, matching the level-3 anchor.

3 / 3

Trigger Term Quality

The 'Use when the user says "document this project" or "generate project docs"' clause quotes natural phrasings a user would actually say, giving good coverage of trigger terms.

3 / 3

Distinctiveness Conflict Risk

The 'brownfield projects for AI context' niche plus specific quoted trigger phrases make it clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
bmad-code-org/BMAD-METHOD
Reviewed

Table of Contents

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.