Agent skill
docs
Documentation workflow for updating markdown docs, technical writing, PRDs, release notes, and public content without touching application source code.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/docs-avav25-ai-assets-3
SKILL.md
Documentation
Use this workflow for documentation-only changes.
Scope
Allowed:
- Markdown docs
- PRDs
- ADRs
- Release notes
- Blog or marketing copy
Not allowed:
- Application source code
- Build config
- Infrastructure code
- Dependency manifests
1. Gather Context
Read:
- Root
AGENTS.md - Relevant scoped
AGENTS.md - Existing docs in the target area
- Related code only when needed for technical accuracy
2. Classify the Content
Identify whether the change is:
- Internal technical docs
- Product or planning docs
- Public-facing marketing or blog content
- Release communication
3. Write
Rules:
- English only unless the user requests otherwise
- Match existing terminology
- Keep examples technically accurate
- Prefer concise, scannable structure
For public content, include SEO-aware structure where relevant.
4. Verify
Check:
- Links resolve
- Terminology matches project conventions
- Formatting is consistent
- No code or config files were changed
5. Report
Summarize the files changed and any follow-up review recommended.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?