alex
204bbb4c84
Remove the megamemory MCP knowledge graph and replace with plain markdown files in .memory/ for tracking plans, research, knowledge, and implementation state. This enables collaboration across people and agentic coding tools (Claude Code, Copilot, Cursor, etc.). Changes: - Remove megamemory MCP from opencode.jsonc - Delete tool/megamemory.ts and .megamemory/ database - Rewrite all 25 config files to use .memory/ markdown files - Add cross-tool instruction file awareness (AGENTS.md, CLAUDE.md, copilot-instructions.md, .cursorrules) - Update save-memory, bootstrap-memory, status commands for md workflow - Update all agent files, skills, and commands consistently
2.6 KiB
2.6 KiB
name, description
| name | description |
|---|---|
| doc-coverage | Documentation coverage checklist and update procedures — load when completing a feature or change set |
When to Use
Load this skill when a feature or change set is nearing completion. Documentation is a completion gate — a task is not done until docs are handled.
Coverage Checklist
For every completed change set, verify documentation coverage:
1. README
- Does the README reflect the current state of the project?
- Are new features, commands, or configuration options documented?
- Are removed features cleaned up from the README?
2. Docs directory (docs/*)
- Are there relevant docs files that need updating?
- Do new features need their own doc page?
- Are API changes reflected in API documentation?
3. Agent/Tool Instruction Files
- Did this change alter workflow, policies, conventions, commands, or architecture guidance?
AGENTS.md(OpenCode instructions) is updated if needed.CLAUDE.md(Claude Code instructions) is updated if needed..github/copilot-instructions.md(GitHub Copilot instructions) is updated if needed..cursorrules(Cursor instructions) is updated if needed.- Are all instruction files consistent with each other?
- Do instruction files reflect the current project state?
4. Inline documentation
- Are complex functions/components documented with comments explaining why, not what?
- Are public APIs documented with parameter descriptions?
Update Procedure
- Review the list of changed files and their purpose.
- Identify which documentation files are affected.
- Read the current state of each affected doc file.
- Update docs to reflect the implemented changes — keep descriptions accurate and concise.
- If a change removes functionality, remove or update the corresponding documentation.
- If creating a new feature, add documentation in the most appropriate location.
Anti-patterns
- Never leave stale docs. If you changed behavior, the docs must change too.
- Never create placeholder docs. "TODO: document this" is not documentation.
- Never duplicate content across doc files. Link to the canonical source instead.
- Never wait for the user to ask. If docs need updating, update them proactively as part of the change set.
Delegation
- The librarian subagent is the specialist for documentation work.
- Lead should delegate doc coverage review to librarian after coder completes implementation.
- Librarian reads the changes, identifies doc gaps, and writes/updates documentation.