Route Orrery documentation-system work through the platform-neutral Orrery CLI while preserving the target repository's canonical AGENTS.md authority chain. Use when asked to scaffold, validate, audit, update, or maintain Orrery documentation.
This is a thin packaged Skill. It requires the separately installed project-orrery CLI declared in adapter-manifest.json; it does not contain Orrery templates, schema, compatibility rules, or project facts.
Maintain, audit, install, or migrate a traceable Project Orrery documentation system while keeping decisions, plans, implementation, current state, and validation distinct.
Install, migrate, audit, and maintain a traceable Markdown project documentation system with Seed principles, ADRs, approved Design, Implementation Plans, State Docs, Validation, Snapshots, handoff/progress records, a local static reader, optional AI Q&A, and GitHub trend radar. Use when a user asks to create or…
Prepare and hand off new or materially rescoped Orrery-managed tasks from committed authority documents. Use when the user asks to start, split, assign, arrange, or materially change a task in an Orrery repository. Do not use for ordinary implementation that already has a current task-description version.
★not rated 45 yesterdayA63 tokens
MIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: