Plugin

documentation-systems

Name: documentation-systems
Author: yeaight7

Write, audit, and maintain project documentation including architecture decision records (ADRs), API reference validation against route handlers, README hardening, handoff summaries, and stale reference detection. Extracts style guides from PR reviews.

What's Inside

Slash Commands4

Architecture Note Command

/architecture-note

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

Doc Audit Command

/doc-audit

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

README Review Command

/readme-review

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

Write Handoff Command

/write-handoff

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

Agents4

Agent Docs Architect

/agent-docs-architect

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

Doc Consistency Reviewer

/doc-consistency-reviewer

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

Handoff Writer

/handoff-writer

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

README Reviewer

/readme-reviewer

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

Skills9

agent-readable-docs

/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

/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

/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

/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

/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.

Stats

Version0.6.3

ReleasedJul 27, 2026

LanguageTypeScript

Stars6

Forks2

MaintenanceExcellent

LicenseApache-2.0

Last CommitJul 27, 2026

AddedMay 6, 2026

Actions

View on GitHub View README Plugin Marketplace JSON Homepage

Available In

agent-powerups6

Safety Signals

Caution

Uses power tools

Uses Bash, Write, or Edit tools

Tags

Agent Powerups

Oh My Zsh for coding agents.

Agent Powerups is an Oh My Zsh-style collection of reusable skills, slash commands, MCP configs, hooks, AGENTS.md templates, and workflows for coding agents.

Today, this repo ships:

reusable skills

safe local CLI (apx) with runnable local checks

persistent Gemini relay for always-active secondary-agent delegation

validation and requirement-check scripts

verified local GitHub MCP check, smoke, and install flow

command, hook, workflow, examples, and AGENTS.md templates

plugins with native install, marketplace metadata, and apx plugins inspection (apx plugins list)

user-intent profiles with apx profiles for curated skill/plugin sets

Native install is direct for humans. Safety boundaries stay around external tools, secrets, shell profiles, and MCP enablement.

What Is Here

Path

Status

Notes

skills/

shipped

Reusable agent workflows such as systematic-debugging and writing-plans

mcp/

shipped

Local-first GitHub MCP config with check, smoke, and explicit install commands

agents-md/

shipped

Starter AGENTS.md templates

commands/

shipped

Review-first command prompts plus safe runnable checks

hooks/

shipped

Review-before-use hook recipes plus safe runnable checks

workflows/

shipped

Scenario guides

plugins/

shipped

Plugins with local-first discovery, validation, native install, and marketplace metadata (apx plugins list)

scripts/

shipped

Validation and tool-check helpers for this repo

examples/

shipped

Minimal safe setup examples

Agent Quickstart

If you are an agent working in a repo with Agent Powerups available, route tasks to capabilities yourself instead of waiting to be told:

Match first. On Claude Code the host already lists skills natively — match the task to the narrowest fitting skill (plus obvious fits like no-fluff). On Codex, Gemini, or generic agents, start with apx discover.

Discover the rest — anything not natively loaded (MCP configs, hooks, AGENTS.md templates, installed-only assets):

apx discover "<the user's task>" --target <codex|claude-code|gemini|generic> --json
apx info <chosen-asset>     # what it is, when to use it, source path, next action

Read, apply, verify. Read the asset's SKILL.md (or file) before applying it; run apx check <asset> only if it declares external requirements; then verify the result against the task.

Gate risky assets. MCP configs and hooks are review-before-use — surface them for approval, never auto-enable.

Quickstart

Using npm (Recommended)

npm install -g agent-powerups apx install claude --full

Agent-Powerups

Agent Powerups

Oh My Zsh for coding agents.

Node.js Version

Quickstart · Agent Quickstart · Plugins · Installation · Security Model · Contributing

Agent Powerups is an Oh My Zsh-style collection of reusable skills, slash commands, MCP configs, hooks, AGENTS.md templates, and workflows for coding agents.

Today, this repo ships:

reusable skills
safe local CLI (apx) with runnable local checks
persistent Gemini relay for always-active secondary-agent delegation
validation and requirement-check scripts
verified local GitHub MCP check, smoke, and install flow
command, hook, workflow, examples, and AGENTS.md templates
plugins with native install, marketplace metadata, and apx plugins inspection (apx plugins list)
user-intent profiles with apx profiles for curated skill/plugin sets

Native install is direct for humans. Safety boundaries stay around external tools, secrets, shell profiles, and MCP enablement.

What Is Here

Path	Status	Notes
`skills/`	shipped	Reusable agent workflows such as `systematic-debugging` and `writing-plans`
`mcp/`	shipped	Local-first GitHub MCP config with check, smoke, and explicit install commands
`agents-md/`	shipped	Starter AGENTS.md templates
`commands/`	shipped	Review-first command prompts plus safe runnable checks
`hooks/`	shipped	Review-before-use hook recipes plus safe runnable checks
`workflows/`	shipped	Scenario guides
`plugins/`	shipped	Plugins with local-first discovery, validation, native install, and marketplace metadata (`apx plugins list`)
`scripts/`	shipped	Validation and tool-check helpers for this repo
`examples/`	shipped	Minimal safe setup examples

Agent Quickstart

If you are an agent working in a repo with Agent Powerups available, route tasks to capabilities yourself instead of waiting to be told:

Match first. On Claude Code the host already lists skills natively — match the task to the narrowest fitting skill (plus obvious fits like no-fluff). On Codex, Gemini, or generic agents, start with apx discover.

Discover the rest — anything not natively loaded (MCP configs, hooks, AGENTS.md templates, installed-only assets):

apx discover "<the user's task>" --target <codex|claude-code|gemini|generic> --json
apx info <chosen-asset>     # what it is, when to use it, source path, next action

Read, apply, verify. Read the asset's SKILL.md (or file) before applying it; run apx check <asset> only if it declares external requirements; then verify the result against the task.
Gate risky assets. MCP configs and hooks are review-before-use — surface them for approval, never auto-enable.

Quickstart

Using npm (Recommended)

npm install -g agent-powerups
apx install claude --full

documentation-systems

What's Inside

documentation-systems

Popularity

What's Inside

Confidence

README

Agent Powerups

What Is Here

Agent Quickstart

Quickstart

Using npm (Recommended)

Similar Plugins

fullstack-dev-skills

ecc

context7

octo

creative-writing

c4-architecture

More by yeaight7

mcp-development

tool-integrations

spec-quality-gates

machine-learning-ops

agentic-systems

Agent Powerups

What Is Here

Agent Quickstart

Quickstart

Using npm (Recommended)

Popularity

Health & Quality

More by yeaight7

mcp-development

tool-integrations

spec-quality-gates

machine-learning-ops

agentic-systems

Similar Plugins

fullstack-dev-skills

ecc

context7

octo

creative-writing

c4-architecture