QPrisma Documentation Sync Skill
Use this skill when code, APIs, workflows, architecture, evaluation behavior, or maintainer process
changes.
Required reads
AGENTS.md
.github/instructions/docs.instructions.md
- Changed implementation/workflow files
- Existing docs that mention the changed behavior
CHANGELOG.md when the change is user-visible, operator-visible, release-facing, or workflow-facing
Primary documentation targets
README.md
API_DOCUMENTATION.md
TESTING.md
CHANGELOG.md
docs/ARCHITECTURE.md
docs/BACKEND_ARCHITECTURE.md
docs/INFRASTRUCTURE.md
docs/MEMORY_ARCHITECTURE.md
backend/agent/ARCHITECTURE.md
.github/copilot-instructions.md
.github/agents/*.agent.md
.github/skills/*/SKILL.md
.github/PULL_REQUEST_TEMPLATE.md
Guardrails
- Prefer edits to existing docs over creating new files.
- Do not document aspirational behavior; document shipped or explicitly planned workflow only.
- Do not duplicate large sections. Cross-reference the source of truth.
- Keep examples runnable and aligned with current repository commands.
- Explicitly note external prerequisites such as Azure, Neo4j, PostgreSQL, Foundry, or deployed hosted
agent.
- Redact private values in examples and evidence.
Process
- Identify impacted docs from changed files and user-visible/operator-visible behavior.
- Search for stale references across docs, Copilot instructions, agents, skills, and PR templates.
- Update existing sections with precise paths, commands, environment variables, and constraints.
- Add changelog entries only when the behavior or workflow matters to users, operators, or maintainers.
- Verify there are no contradictory statements across docs.
Validation
- Run
git diff --check for text formatting issues.
- Inspect Markdown headings, links, commands, and examples touched by the change.
- For docs generated from implementation, run the existing generator/check command if one exists.
Output format
### Updated docs
- `path`: change summary
### Consistency checks
- ...
### Remaining gaps
- ...
Source: alexandergg/QPrisma — distributed by TomeVault.
1---2name: qprisma-doc-sync3description: Keep QPrisma documentation, Copilot instructions, agents, skills, PR templates, and changelog synchronized with implementation and workflow behavior. Use when this capability is needed.4---56# QPrisma Documentation Sync Skill78Use this skill when code, APIs, workflows, architecture, evaluation behavior, or maintainer process9changes.1011## Required reads12131. `AGENTS.md`142. `.github/instructions/docs.instructions.md`153. Changed implementation/workflow files164. Existing docs that mention the changed behavior175. `CHANGELOG.md` when the change is user-visible, operator-visible, release-facing, or workflow-facing1819## Primary documentation targets2021- `README.md`22- `API_DOCUMENTATION.md`23- `TESTING.md`24- `CHANGELOG.md`25- `docs/ARCHITECTURE.md`26- `docs/BACKEND_ARCHITECTURE.md`27- `docs/INFRASTRUCTURE.md`28- `docs/MEMORY_ARCHITECTURE.md`29- `backend/agent/ARCHITECTURE.md`30- `.github/copilot-instructions.md`31- `.github/agents/*.agent.md`32- `.github/skills/*/SKILL.md`33- `.github/PULL_REQUEST_TEMPLATE.md`3435## Guardrails3637- Prefer edits to existing docs over creating new files.38- Do not document aspirational behavior; document shipped or explicitly planned workflow only.39- Do not duplicate large sections. Cross-reference the source of truth.40- Keep examples runnable and aligned with current repository commands.41- Explicitly note external prerequisites such as Azure, Neo4j, PostgreSQL, Foundry, or deployed hosted42 agent.43- Redact private values in examples and evidence.4445## Process46471. Identify impacted docs from changed files and user-visible/operator-visible behavior.482. Search for stale references across docs, Copilot instructions, agents, skills, and PR templates.493. Update existing sections with precise paths, commands, environment variables, and constraints.504. Add changelog entries only when the behavior or workflow matters to users, operators, or maintainers.515. Verify there are no contradictory statements across docs.5253## Validation5455- Run `git diff --check` for text formatting issues.56- Inspect Markdown headings, links, commands, and examples touched by the change.57- For docs generated from implementation, run the existing generator/check command if one exists.5859## Output format6061```markdown62### Updated docs63- `path`: change summary6465### Consistency checks66- ...6768### Remaining gaps69- ...70```7172---73> Source: [alexandergg/QPrisma](https://github.com/alexandergg/QPrisma) — distributed by [TomeVault](https://tomevault.io).74<!-- tomevault:4.0:skill_md:2026-05-23 -->