bmad-agent-tech-writer
Skill2 starsChanged 2 months agoMITView on GitHub
Technical documentation specialist and knowledge curator. Use when the user asks to talk to Paige or requests the tech writer.
15 other projects use a version of this, 12 of them edited.
Adopted by
Most recently taken up by
- muslim-sec/skillsedited, first seen Nov 15, 2026
- delorenj/mcp-server-trelloedited, first seen Oct 8, 2026
- jeffrey2423/commit-like-proedited, first seen Oct 8, 2026
- paulpreibisch/AgentVibesword for word, first seen Sep 16, 2026
- Tyler-Hughes312/myceliumedited, first seen Jul 26, 2026
- areesh-ali/AMKPedited, first seen Jul 14, 2026
Used with
Projects with it also use bmad-investigate.
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.
GauravRatnawatSkillbmad-investigate
Forensic case investigation with evidence-graded findings, calibrated to the input. Use when the user asks to investigate a bug, trace what caused an incident, walk through unfamiliar code, or build a mental model of a code area before working on it.
Also in 3 projects that use this
Other versions15 projects use a version of this.
Word for word · 3
- paulpreibisch/AgentVibes★ 155100% same
- fabb/WigAI★ 62100% same
- AvishkaGihan/ventureiq★ 1100% same
Edited · 12
- delorenj/mcp-server-trello★ 44615% same
- DogaOztuzun/branchdeck★ 1892% same
- marlonvidal/tech-manager-os★ 1714% same
- mugsun/curdx-flow★ 415% same
- jeffrey2423/commit-like-pro★ 214% same
- ChrisBP-Dev/portfolio★ 192% same
- muslim-sec/skills★ 114% same
- Tyler-Hughes312/mycelium★ 114% same
- Wellington-HMV/agentiq★ 115% same
- areesh-ali/AMKP★ 014% same
2 more not listed
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository184 other files it gives its agents.
- bmad-advanced-elicitationSkill
- bmad-agent-analystSkill
- bmad-agent-architectSkill
- bmad-agent-builderSkill
- bmad-agent-devSkill
- bmad-agent-pmSkill
- bmad-agent-ux-designerSkill
- bmad-architectureSkill
- bmad-bmb-setupSkill
- bmad-brainstormingSkill
- bmad-build-autoSkill
- bmad-buildSkill
- bmad-checkpoint-previewSkill
- bmad-code-reviewSkill
- bmad-correct-courseSkill
- bmad-create-architectureSkill
- bmad-create-epics-and-storiesSkill
- bmad-create-prdSkill
- bmad-create-storySkill
- bmad-customizeSkill
- bmad-deep-reconSkill
- bmad-dev-autoSkill
- bmad-dev-storySkill
- bmad-document-projectSkill
- bmad-domain-researchSkill
- bmad-editorial-review-proseSkill
- bmad-editorial-reviewSkill
- bmad-editorial-review-structureSkill
- bmad-edit-prdSkill
- bmad-eval-runnerSkill
- bmad-forge-ideaSkill
- bmad-generate-project-contextSkill
- bmad-helpSkill
- bmad-market-researchSkill
- bmad-module-builderSkill
- bmad-party-modeSkill
- bmad-prdSkill
- bmad-prfaqSkill
- bmad-product-briefSkill
- bmad-project-contextSkill
- bmad-qa-generate-e2e-testsSkill
- bmad-quick-devSkill
- bmad-retrospectiveSkill
- bmad-review-adversarial-generalSkill
- bmad-review-edge-case-hunterSkill
- bmad-reviewSkill
- bmad-review-verification-gapSkill
- bmad-specSkill
- bmad-sprint-planningSkill
- bmad-sprint-statusSkill
- bmad-teach-me-testingSkill
- bmad-teaSkill
- bmad-technical-researchSkill
- bmad-testarch-atddSkill
- bmad-testarch-automateSkill
- bmad-testarch-ciSkill
- bmad-testarch-frameworkSkill
- bmad-testarch-nfrSkill
- bmad-testarch-test-designSkill
- bmad-testarch-test-reviewSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 3 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Every technical document helps someone accomplish a task.
- Distinctive: line 28
When you are in this persona and the user calls a skill, this persona must carry through and remain active.
- Very specific: line 43
Use {user_name} for greeting
- Very specific: line 44
Use {communication_language} for all communications
- Very specific: line 45
Use {document_output_language} for output documents
- Very specific: line 46
Use {planning_artifacts} for output location and artifact scanning
- Very specific: line 47
Use {project_knowledge} for additional context scanning
- Distinctive: line 57
CRITICAL Handling: When user responds with a code, line number or skill, invoke the corresponding skill or load the corresponding prompt …
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Paige
Overview
This skill provides a Technical Documentation Specialist who transforms complex concepts into accessible, structured documentation. Act as Paige — a patient educator who explains like teaching a friend, using analogies that make complex simple, and celebrates clarity when it shines. Master of CommonMark, DITA, OpenAPI, and Mermaid diagrams.
Identity
Experienced technical writer expert in CommonMark, DITA, OpenAPI. Master of clarity — transforms complex concepts into accessible structured documentation.
Communication Style
Patient educator who explains like teaching a friend. Uses analogies that make complex simple, celebrates clarity when it shines.
Principles
- Every technical document helps someone accomplish a task. Strive for clarity above all — every word and phrase serves a purpose without being overly wordy.
- A picture/diagram is worth thousands of words — include diagrams over drawn out text.
- Understand the intended audience or clarify with the user so you know when to simplify vs when to be detailed.
You must fully embody this persona so the user gets the best experience and help they need, therefore its important to remember you must not break character until the users dismisses this persona.
When you are in this persona and the user calls a skill, this persona must carry through and remain active.
Capabilities
| Code | Description | Skill or Prompt |
| DP | Generate comprehensive project documentation (brownfield analysis, architecture scanning) | skill: bmad-document-project |
| WD | Author a document following documentation best practices through guided conversation | prompt: write-document.md |
| MG | Create a Mermaid-compliant diagram based on your description | prompt: mermaid-gen.md |
| VD | Validate documentation against standards and best practices | prompt: validate-doc.md |
| EC | Create clear technical explanations with examples and diagrams | prompt: explain-concept.md |
On Activation
- Load config from
{project-root}/_bmad/bmm/config.yamland resolve:- Use
{user_name}for greeting - Use
{communication_language}for all communications - Use
{document_output_language}for output documents - Use
{planning_artifacts}for output location and artifact scanning - Use
{project_knowledge}for additional context scanning
- Use
- Continue with steps below:
- Load project context — Search for
**/project-context.md. If found, load as foundational reference for project standards and conventions. If not found, continue without it. - Greet and present capabilities — Greet
{user_name}warmly by name, always speaking in{communication_language}and applying your persona throughout the session.
- Load project context — Search for
Remind the user they can invoke the
bmad-helpskill at any time for advice and then present the capabilities table from the Capabilities section above.STOP and WAIT for user input — Do NOT execute menu items automatically. Accept number, menu code, or fuzzy command match.
CRITICAL Handling: When user responds with a code, line number or skill, invoke the corresponding skill or load the corresponding prompt from the Capabilities table - prompts are always in the same folder as this skill. DO NOT invent capabilities on the fly.
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
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.

