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.
- Author
- yeaight7 ↗
- Repository
- agent-powerups ↗
- Licence
- Apache-2.0
- Last repository change
- 27.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.09.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
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.
Original author description
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.
How it works
- When to Use
- The 3-Cycle Loop
- Output
- Verification
SKILL.md preview
--- name: context-retrieval-loop description: 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. --- # Context Retrieval Loop (Documentation) Gather documentation context before writing or updating docs. Prevents duplicating existing content or violating project conventions. ## When to Use - About to write a new doc, README section, or ADR - Updating existing documentation and unsure of scope - Spawning a documentation subagent that needs file context ## The 3-Cycle Loop ### Cycle 1 — Broad Search ```bash # 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. ### Cycle 2 — Source and Existing Docs Read the source files the docs will describe. Find existing docs for the same area: ```bash 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. ### Cycle 3 — Conventions and Setup ```bash 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? ## Output ``` Context gathered: <file-path> — <reason> Missing context (if any): <what is still unclear> ``` State gaps. Do not write documentation that contradicts undiscovered existing content. ## Verification - [ ] Existing docs were searched before writing — duplication ruled out or the covering doc identified - [ ] The source files the docs describe were read, not assumed - [ ] Doc conventions (style guide, templates, contribution rules) were checked - [ ] Gaps are stated explicitly; nothing written contradicts existing content
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · yeaight7/agent-powerups | 100 | Apache-2.0 |
| yeaight7/agent-powerups | 100 | Apache-2.0 |
| yeaight7/agent-powerups | 100 | Apache-2.0 |
| yeaight7/agent-powerups | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 12568bb29944 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90documentation-criteria
Determines which PRD, ADR, Design Doc, and Work Plan a change requires. Use when deciding documentation scope or creating technical documents. - 100readme-style
Applies README conventions when creating or updating README.md files. Covers section ordering, writing style, standard section templates, badges, MCP server documentation, CLI documentation, and codebase cross-referencing. Use when writing a new README, updating an existing… - 95readme
When the user wants to create or update a README.md file for a project. Also use when the user says 'write readme,' 'create readme,' 'document this project,' 'project documentation,' or asks for he... - 100documentation
Guide for writing technical documentation. Use when creating README files, API documentation, guides, or inline code documentation. - 100docs
This skill should be used when the user asks about "documentation", "README", "CHANGELOG", "CONTRIBUTING", "ADR", "architecture decision record", "changelog format", "keep a changelog", "doc comments", "API documentation", or needs guidance on project documentation requirements. - 100documentation-templates
Templates for README, API docs, code comments, changelog, ADR and llms.txt. Use when writing project documentation.