bmad-document-project

Generate AI-context documentation for brownfield projects from codebases.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/jaydubya818/New_baseline --skill bmad-document-project-jaydubya818
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-document-project
Source: https://github.com/jaydubya818/New_baseline/tree/main/skills/bmad/analysis/bmad-document-project
Command: npx skills add https://github.com/jaydubya818/New_baseline --skill bmad-document-project-jaydubya818

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brownfield projects often lack structured, AI-ready documentation, making it hard for teams to plan, onboard, and extend the codebase. This skill generates coherent, actionable documentation that captures the project context, architecture, data flows, and deployment considerations so AI agents can reason about and extend the project effectively.

Core Features & Use Cases

  • Automated project context capture: Generates a canonical project brief, architecture overview, and technology stack summary.
  • End-to-end documentation package: Creates API contracts, data models, deployment guidelines, and development workflows for brownfield PRD readiness.
  • Multi-part and monorepo support: Documents single-part and multi-part projects, with cross-part integration mapping when applicable.

Quick Start

Provide the root path of the project to document and any optional context; the skill will generate a complete AI-context documentation package.

Frequently Asked Questions about bmad-document-project

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

FAQPage Schema
How do I generate AI-ready documentation for an existing brownfield project?

Generating AI-ready documentation for an existing brownfield project involves analyzing the codebase, architecture, and deployment patterns to produce a coherent project brief, API contracts, and data models. This skill automates that capture by pointing to your project root.

What's the best way to document a monorepo for AI-driven planning?

Documenting a monorepo for AI-driven planning requires mapping cross-part integrations alongside individual technology stacks. This skill supports multi-part projects by generating comprehensive architecture overviews and deployment guidelines across the entire repository structure.

Can I create a brownfield PRD without manually writing the technical context?

Creating brownfield PRDs without manual writing is possible by extracting project context, data flows, and development workflows automatically. The skill outputs these structured artifacts to a project_knowledge folder for immediate PRD generation use.

Does this automated codebase documentation approach work without special configuration?

Automated codebase documentation works without special configuration beyond pointing to the project root directory. Optionally selecting deep-dive analyses allows you to tailor the generated architecture overviews and deployment guidelines to your specific modernization needs.

Why does my team need structured AI-context documentation for legacy codebases?

Structured AI-context documentation is needed for legacy codebases because brownfield projects often lack coherent technical context, making it hard for AI agents to reason about, plan, and extend the system effectively during modernization efforts.