Update docs

Skill transparent-pegasus/herdrpowers/skills/update-docs

Use when code, config, prompt, schema, or task changes require updating Markdown files directly under docs/, such as architecture, structure, config-sync, theories, adopted-theories, or todo documents.From its SKILL.md

Install

npx -y skills add transparent-pegasus/herdrpowers --skill update-docs

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

11 stars11 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.2 KB, as published. Nobody here has run it

Update Docs

Overview

Keep root-level Markdown docs under docs/ aligned with the current codebase and config.

Use ROOT_DOCS.md in this directory as the contract for what each root doc should contain.

Scope

Edit only files matching docs/*.md
Do not edit files inside docs/*/
Leave generated or output directories alone, including planning directories, generated content directories, and other paths explicitly marked as outputs by the initialized repository.

Workflow

Identify which root docs are affected by the change.
Check ROOT_DOCS.md to confirm each affected doc's role and boundaries.
Check the current source of truth in code, config, prompts, schemas, or git history.
Update only the sections that changed.
Keep terminology, tone, and structure consistent with the existing file.
Keep diffs minimal. Prefer surgical edits over rewrites.
If a doc conflicts with the source of truth, fix the doc.