doc-master

Plugin doc-master from marketplace claude-plugin-marketplace in JosiahSiegel/claude-plugin-marketplace. Commands read from the repo's manifest — 1 month ago.

Skills (8)

• adr-backfill

  This skill should be used to retroactively record an architectural decision that was made in the past but never written up as an ADR — typically surfaced by a doc audit or by a user realising a long-ago shipped change should have been documented. PROACTIVELY activate on "backfill ADR", "retroactive

• adr-critique

  This skill should be used to audit an existing or legacy ADR, especially one imported, LLM-generated, stale, or never self-critiqued. PROACTIVELY activate on "review this ADR", "critique this ADR", "audit our decision log", "is this ADR any good?", "fix this old ADR", "rewrite this legacy ADR", "ADR

• adr-discovery

  This skill should be used before drafting an ADR when context, components, relationships, deciders, or prior decisions are unclear. PROACTIVELY activate on "I want to write an ADR for X", "gather context for a decision", "discovery for an ADR", "ADR intake", "ADR pre-flight", "prep work before an AD

• adr-drafting

  This skill should be used when a decision is ready to become an ADR and the user wants co-thinking rather than template filler. PROACTIVELY activate on "draft the ADR", "write up the decision", "co-think this ADR", "challenge my reasoning", "ADR for X", "MADR for X", "Y-statement for X", "we decided

• c4-model

  This skill should be used to create or update a C4 architecture diagram alongside an ADR, especially in LikeC4. PROACTIVELY activate on "add a C4 diagram", "create a context diagram", "container view", "LikeC4 model", "draw the architecture", "diagram this decision", "architecture diagram for the AD

• doc-diagnostic

  This skill should be used when deciding whether a doc should exist, where it belongs, whether something is really an ADR, or whether an architectural decision is missing from the record. PROACTIVELY activate on "should this be an ADR?", "where should I document X?", "is this architecturally signific

• markdown-style

  This skill should be used to review, lint, or fix Markdown formatting in READMEs, ADRs, runbooks, how-tos, design docs, or any `.md` file. PROACTIVELY activate on "review this markdown", "lint this doc", "lint this README", "style-check this doc", "fix the formatting", "review my README", "is this m

• repo-health

  This skill should be used when bootstrapping, auditing, or reviewing the community-health and repository-cornerstone files in a code repository: README, LICENSE, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, SUPPORT, issue / PR templates, CODEOWNERS, FUNDING, CITATION, and REUSE / SPDX metadata. PROACTIV

Slash commands (6)

• /doc-master:adr-critique

  Audit a pre-existing or legacy ADR line-by-line. Quotes offending lines verbatim, names the rule broken, proposes shorter rewrites, requires per-line approval. Use for ADRs that did NOT go through the /adr-new + adr-drafting flow.

• /doc-master:adr-discover

  Run the zero-hallucination pre-flight Q&A before writing an ADR. Confirms domain, components, relationships, related ADRs, and decision-makers one fact at a time. Produces a discovery brief and an open-questions register. Use BEFORE drafting if context is fuzzy.

• /doc-master:adr-new

  Run the "is this an ADR?" diagnostic on a proposed decision, then either draft the ADR using the project's existing template, or recommend the correct alternative documentation form.

• /doc-master:adr-scan

  Scan code and history for architecturally significant decisions that lack ADRs. Produces BACKFILL-ADR candidates and open questions only; never drafts without human confirmation.

• /doc-master:doc-audit

  Audit documentation and ADR coverage against the four-question test and ADR canon. Finds stale/cluttered docs plus architecture decisions visible only in code/history, surfacing BACKFILL-ADR candidates without drafting. Produces a KEEP / MERGE / REWRITE / DELETE / MOVE / BACKFILL-ADR action list — d

• /doc-master:doc-lint

  Lint a Markdown document — two-pass review (syntax must-fix, then style should-fix) per-finding with architect approval. Cites a rule and source layer for every finding. Does not bulk-rewrite.

Subagents (1)

• doc-expert

  Documentation, Markdown style, and Architecture Decision Record (ADR) expert. PROACTIVELY activate for: (1) writing or recording ADRs and architectural decisions, (2) missing ADRs, missing decision records, implicit decisions in code, architecture/code archaeology, undocumented architecture, inherit

Similar plugins