Help us improve
Share bugs, ideas, or general feedback.
Deterministic 3-cycle loop for gathering documentation context before writing or updating docs. Broad search → exact source and existing docs → project conventions and setup.
How this skill is triggered — by the user, by Claude, or both
Slash command
/documentation-systems:context-retrieval-loopThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Gather documentation context before writing or updating docs. Prevents duplicating existing content or violating project conventions.
Share bugs, ideas, or general feedback.
Gather documentation context before writing or updating docs. Prevents duplicating existing content or violating project conventions.
# Find existing docs
find . -name "*.md" -not -path "*/node_modules/*" | head -30
rg "<topic>" docs/ *.md -l 2>/dev/null
Stop here if you find the existing doc that covers this topic.
Read the source files the docs will describe. Find existing docs for the same area:
rg "<module-name>" docs/ -l
cat README.md | head -60
Stop here if you understand the scope of what needs to be written or updated.
ls docs/ .github/ 2>/dev/null
cat AGENTS.md CLAUDE.md 2>/dev/null | head -40
Check: Is there a doc style guide? A template? A contribution guide with doc requirements?
Context gathered:
<file-path> — <reason>
Missing context (if any):
<what is still unclear>
State gaps. Do not write documentation that contradicts undiscovered existing content.
npx claudepluginhub yeaight7/agent-powerups --plugin documentation-systemsOrchestrates changing an existing working feature to new desired behavior by updating tests first, then implementation, with review and gated commit.