project-documentation
Docs Governance
Govern a repository's docs/ directory or equivalent docs set from repository reality rather than generic documentation advice. This skill is for documentation-system maintenance work: mapping the docs tree, consolidating duplicate pages, improving navigation and source-of-truth structure, refreshing stale docs after changes, and auditing docs for drift.
Outputs
- Docs-set inventories with topic clusters, source-of-truth notes, and overlap findings
- Consolidation plans for
docs/sprawl, duplicate pages, and broken information architecture - Updated docs indexes, landing pages, navigation pages, and cross-links
- Targeted refreshes to pages inside
docs/after code or workflow changes - Verification reports covering drift, dead links, stale commands, and docs-to-repo mismatches
- Short assumptions logs when the repository does not fully answer an important documentation claim
Invocation Posture
Treat this skill as manual-first.
Why:
More from liqiongyu/my-agents
brainstorming
Manual-first brainstorming workflow for turning ambiguous ideas or competing directions into an approved decision before planning or implementation. Activate when the user explicitly asks to brainstorm, explore options, compare approaches, or pressure-test a direction. Do not activate for clarification, review, detailed planning, or straightforward execution once a direction is already chosen.
10deep-research
Use when the user explicitly asks for comprehensive, citation-backed research such as a deep dive, due diligence, market analysis, or a multi-source comparison/report. Do not activate for quick factual lookups, ordinary coding tasks, or routine content generation unless the user first asks for research or source verification.
7readme-craftsman
Create, update, or review a repository README when the user explicitly asks for README work. Use it to draft a new README, refresh an existing README after project changes, or audit a README against the current repository. Do not use it for general documentation, API docs, architecture docs, or documentation tasks that do not specifically target a README file.
5prompt-engineering
>
5review
>
4business-plan
Use this skill for substantial business planning work: drafting or revising a business plan, investor-ready financial analysis, market sizing, pitch deck narrative, strategic review, or business valuation. It is especially useful when the user needs structured commercial thinking, investor-grade outputs, China fundraising context, or AI/agent business analysis. Prefer this skill when the main deliverable is a business analysis or plan, not open-ended idea exploration, general current-events research, or final file production in slides, docs, or spreadsheets.
4