agentleFS
Sign inStart free
snovak7snovak7/bmad-github-zoho-pipeline/.claude/skills/bmad-document-project/SKILL.md

bmad-document-project

Skill0 starsChanged 48 days agoMITView on GitHub

Deprecated — forwards to bmad-project-context. Use when the user says "document this project" or "generate project docs"

20 other projects use a version of this, 9 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use bmad-agent-tech-writer and bmad-agent-qa.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • DogaOztuzunSkill

    bmad-agent-tech-writer

    Technical documentation specialist and knowledge curator. Use when the user asks to talk to Paige or requests the tech writer.

    Also in 13 projects that use this

  • DogaOztuzunSkill

    bmad-agent-qa

    QA engineer for test automation and coverage. Use when the user asks to talk to Quinn or requests the QA engineer.

    Also in 4 projects that use this

The file

Create a free account to mount
Files
SKILL.md

DEPRECATED — forwards to bmad-project-context

Tell the user two things.

First: this skill is deprecated. Generating documentation volume about a codebase made agents worse, not better — agents read code more accurately than prose describing code, and the generated set was stale on arrival. bmad-project-context owns what remains useful: a small verified block in the repo's AGENTS.md carrying what the code cannot say — required policy, conventions that differ from defaults, what running the project takes that no config file states, and known pitfalls.

Second, so they are not surprised by what they get: the deeper "explain this system, its rationale and its history" material is a different altitude and is not part of that block. It is coming as its own capability. If that is what they were after, say so plainly rather than producing a thin substitute.

Then invoke bmad-project-context with setup intent, forwarding the user's original request and any paths or documents they supplied, verbatim. It takes the workflow from here.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free