bmad-document-project

Forwards project documentation requests to the bmad-project-context skill.

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-document-project-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-document-project
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/bmad-document-project
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-document-project-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill handles legacy requests to "document this project" by redirecting them to the maintained bmad-project-context skill, preventing the generation of stale, low-value documentation volumes that quickly drift out of sync with the actual codebase. ## Core Features & Use Cases - Deprecation Notice: Informs the user that bulk project documentation generation is deprecated and explains why agents read code more accurately than prose describing code. - Request Forwarding: Invokes bmad-project-context with setup intent, passing the user's original request and any supplied paths or documents verbatim. - Expectation Setting: Clarifies that deeper system rationale and history material is a separate upcoming capability, not part of the AGENTS.md context block. - Use Case: A user asks to "generate project docs" for their repository; this Skill explains the deprecation and routes the request so a small verified context block lands in the repo's AGENTS.md instead. ## Quick Start Ask the assistant to document this project, and it will explain the deprecation and forward your request to bmad-project-context automatically.

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 documentation for my project with BMAD?

Requesting project documentation triggers this deprecated skill, which forwards your request to bmad-project-context. That skill writes a small verified context block into your repo's AGENTS.md rather than generating a large documentation set.

Why was the document-project skill deprecated?

Generated documentation volumes made agents worse, not better: agents read code more accurately than prose describing code, and the generated docs were stale on arrival. Only policy, conventions, and pitfalls that code cannot express remain useful.

What does bmad-project-context produce instead of full documentation?

It produces a small verified block in the repository's AGENTS.md carrying what code cannot say: required policy, conventions differing from defaults, runtime requirements not stated in config files, and known pitfalls.

Can I still get deep system rationale and architecture history docs?

Not through this skill. Deeper explanatory material about a system's rationale and history is planned as a separate capability at a different altitude, and this skill will tell you so rather than produce a thin substitute.

When should I not use the document-project skill?

Do not use it directly at all; it exists only as a forwarding shim. Invoke bmad-project-context with setup intent for project context, since this skill performs no documentation generation itself.