Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aj-geddes/bmad-document-project
BROWNFIELD planning input. Scans an existing codebase READ-ONLY and writes project-documentation.md — ground truth for stack, structure, key flows, conventions, and integration points — so downstream BMAD planning skills start from reality. Does NOT modify code; produces only the doc artifact.
Passed 11 of 17 test cases with the skill, and 4 of 17 without it.
and 12 more in the full report
11 fixed4 passed either way7 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
The instructions your model reads when the skill loads.
BROWNFIELD entry point. When a project already has code, planning skills need
ground truth — not guesses about the stack or conventions. This skill performs a
systematic, READ-ONLY codebase scan and emits project-documentation.md, the
authoritative current-state snapshot that every downstream BMAD planning skill loads.
No code is written, modified, or executed. Allowed tools are Read, Glob, Grep, Write (for the output document only), and TodoWrite (to track scan progress).
bmad-output/project-documentation.md
(or the user-configured output folder — honor it)
Load bmad-output/project-context.md if it exists; merge any constraints already
recorded there rather than rediscovering them from scratch.
Ask which intent applies if ambiguous; never silently regenerate an existing document.
Use TodoWrite to track the six scan passes below. Complete every pass before writing the final document.
Pass 1 — Repository skeleton
Glob: **/* (depth ≤ 3, exclude node_modules, .git, dist, build, __pycache__, .venv)
Glob: *.md, *.txt, *.rst at root and docs/
Capture: directory tree shape, presence of monorepo markers (packages/,
apps/, libs/), top-level config files, documentation roots.
test cases passed, vs 4 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.