| name | orca-docs-system |
| description | Maintain ORCA Framework's layered docs system, wiki routing, start-here flow, and doc refresh signals without creating orphaned doc sprawl. |
ORCA Framework Docs System
Trigger
Use when a user asks for:
- where to start
- documentation structure
- wiki or guide creation
- doc refresh after a feature change
- stale-doc detection or docs maintenance
Core Rules
- Start with routing, not volume.
- Prefer one clear summary page over several overlapping summaries.
- Keep README, start-here pages, indexes, and wiki homepage aligned.
- Treat docs changes as part of the feature, not as a later cleanup.
- When a new concept appears, update glossary, indexes, and the most relevant guide before adding more reference prose.
Expected Workflow
- Identify the audience: new user, active user, contributor, or maintainer.
- Identify the layer: intro, quickstart, concept, guide, command, feature, workflow, wiki, or contributor docs.
- Update routing surfaces first.
- Update deeper reference pages only where needed.
- Record refresh signals when something remains likely stale.
Quality Bar
The docs system should make ORCA Framework easier to enter and easier to navigate after feature growth.
Common Failure Modes
- adding pages without updating routing
- duplicating the same explanation across README, docs, and wiki
- leaving new commands out of indexes
- letting wiki pages become a stale mirror
