bmad-document-project

Document brownfield repositories with scan levels and incremental state-file updates.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/cassioalexandre/agf --skill bmad-document-project-cassioalexandre
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-document-project
Source: https://github.com/cassioalexandre/agf/tree/main/_bmad/bmm/1-analysis/bmad-document-project
Command: npx skills add https://github.com/cassioalexandre/agf --skill bmad-document-project-cassioalexandre

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly turn an unfamiliar brownfield codebase into clear, AI-ready documentation so that agents can understand structure, architecture, and integration points without manual digging.

Core Features & Use Cases

  • Brownfield project documentation: Produces project docs from an existing repository, optimized for “AI context” consumption.
  • Scan-depth options: Supports quick, deep, and exhaustive modes to control how much of the codebase is read.
  • Workflow resumability: Writes and updates a state file so interrupted runs can resume safely.
  • Generated documentation set: Creates artifacts like source-tree analysis, architecture docs, and supporting guides to support planning and PRDs.

Quick Start

Use the bmad-document-project skill to document this project by running the workflow defined in ./workflow.md and generating the required docs into the project knowledge/output folder.

Frequently Asked Questions about bmad-document-project

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document an existing codebase for AI context?

To document an existing codebase for AI context, run a workflow that scans your repository structure, analyzes architecture, and generates AI-ready documentation artifacts directly to disk for agent consumption.

What is brownfield analysis for project documentation?

Brownfield analysis scans an existing, unfamiliar codebase to capture its structure, architecture, and integration details. You need it when preparing AI context for downstream planning tasks like generating brownfield PRDs.

Can I control how much of the codebase is read during project documentation generation?

Yes, you can control codebase scanning depth using quick, deep, and exhaustive scan modes. These options balance analysis speed against the level of architectural detail captured for AI context generation.

What happens if the codebase documentation workflow is interrupted?

If the documentation workflow is interrupted, it resumes safely. The process writes and updates a state file during execution, allowing incremental updates to resume exactly where the previous run stopped.

Does the project documentation process validate generated files?

Yes, the project documentation process validates generated files. It performs validation after each document is written immediately to disk, ensuring output quality before proceeding to the next artifact.

What is the best way to prepare repository documentation for downstream planning?

The best way to prepare repository documentation for planning is to generate a comprehensive documentation set including source-tree analysis and architecture docs. This provides the necessary AI context for downstream planning tasks like brownfield PRDs.