documentation-systems

Plugin documentation-systems from marketplace agent-powerups in yeaight7/agent-powerups. Commands read from the repo's manifest — 1 month ago.

Skills (9)

• agent-readable-docs

  Use when writing technical documentation that needs to be readable by both humans and AI models, converting existing docs to HADS format, validating a HADS document, or optimizing documentation for token-efficient AI consumption.

• api-doc-review

  Use when API documentation may have drifted from the implementation -- endpoints changed without a spec update, integration partners report mismatches, or a PR touches routes, params, or response shapes.

• architecture-decision-records

  Use when a significant architectural choice is being finalized, revisited, or reversed -- technology selection, structural patterns, or trade-offs that future maintainers or agents might unknowingly undo.

• context-docs

  Use when a subsystem needs persistent context for future agents or engineers -- its boundaries keep being rediscovered the hard way, invariants keep getting violated, or sessions repeatedly ask the same questions about it.

• context-retrieval-loop

  Use when about to write a new doc, README section, or ADR, updating existing documentation with unclear scope, or spawning a documentation subagent that needs file context.

• doc-consistency-check

  Use when documentation may have rotted against the code -- files were renamed or moved, scripts or env vars changed, or readers report commands and paths from the docs that no longer work.

• handoff-discipline

  Use when ending a session, handing a task back to the user, or approaching the context limit with work unfinished -- the next session or engineer must be able to resume the work instantly.

• readme-hardening

  Use when a README cannot be followed verbatim -- setup or test commands fail or are vague, environment requirements are unstated, or a new engineer or agent cannot bootstrap the project quickly.

• review-comment-style-mining

  Use when mining PR review comments and text diffs for reusable writing, documentation, tone, and editorial improvement patterns.

Slash commands (4)

• /documentation-systems:architecture-note

  Record a brief Architecture Decision Record (ADR) about a recent technical choice.

• /documentation-systems:doc-audit

  Audit the repository's documentation for broken paths, missing setup commands, and stale code blocks.

• /documentation-systems:readme-review

  Review the README.md to ensure it functions as an executable contract for new developers.

• /documentation-systems:write-handoff

  Generate a dense state-restoration document before ending a session.

Subagents (4)

• agent-docs-architect

  Specializes in structuring repository documentation to minimize context usage and improve agent navigation.

• doc-consistency-reviewer

  Scans documentation for stale file paths, outdated code blocks, and broken links after refactoring.

• handoff-writer

  Summarizes the current state of a task into a dense handoff document for the next session.

• readme-reviewer

  Audits README files to ensure all setup commands work and architecture pointers are accurate.

Similar plugins