orientation

Loads phase roadmap, backlog alignment, and workflow context for planning sessions.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/yiwei79/root-azoth --skill orientation-yiwei79
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orientation
Source: https://github.com/yiwei79/root-azoth/tree/main/.opencode/skills/orientation
Command: npx skills add https://github.com/yiwei79/root-azoth --skill orientation-yiwei79

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeps the root CLAUDE.md small by offloading the full phase roadmap, v0.2.0 milestone details, and expanded development workflow into an on-demand skill, so agents only load planning context when editing roadmaps or aligning backlog items. ## Core Features & Use Cases - Phase Roadmap Reference: Holds the complete v0.1.0 phase history (Phases 1-7) and the active v0.2.0-p2 working slice with per-task specs under .azoth/roadmap-specs/v0.2.0/. - Backlog Alignment: Provides initiative and task mappings (P1-020 through T-004, INI-PLT-006, INI-MEM-001) for editing .azoth/backlog.yaml and .azoth/roadmap.yaml consistently. - Expanded Workflow: Supplies the six-step development workflow (read CLAUDE.md, check architecture docs, verify phase, respect scope gates, validate decisions, capture memory episodes). - Use Case: Before modifying .azoth/roadmap.yaml to mark a task complete, load this skill to confirm the current lifecycle phase, canonical version fields in azoth.yaml, and which initiatives remain deferred. ## Quick Start Load the orientation skill before editing the roadmap or backlog files so you can check the current phase and task specs.

Frequently Asked Questions about orientation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check the current project phase before editing the roadmap?▼

Load this skill and read the v0.2.0 milestone section, which lists the canonical state in azoth.yaml (phase, lifecycle_phase) and .azoth/roadmap.yaml (active_version, current_phase). Cross-check per-task specs under .azoth/roadmap-specs/v0.2.0/ for individual items.

When should I load the orientation skill instead of relying on CLAUDE.md?▼

Load it before editing .azoth/backlog.yaml or .azoth/roadmap.yaml, when answering detailed phase questions, or when implementing Phase 4-7 backlog items. Root CLAUDE.md stays minimal and only points here for roadmap and workflow detail.

What files define the canonical planning state in this workflow?▼

Canonical planning state comes from this skill plus azoth.yaml (phase and lifecycle_phase fields), .azoth/roadmap.yaml (active_version, current_phase), and per-task specs in .azoth/roadmap-specs/v0.2.0/. The bootloader-state file may supplement these when present.

Does the orientation skill handle routine implementation work?▼

No, it is explicitly not for routine implementation. It exists for planning, roadmap edits, and phase alignment so agents avoid loading historical roadmap detail on every session.

How do I keep roadmap documentation in sync after phase changes?▼

Update this skill's phase checklists when they change, not the root CLAUDE.md, unless the change is a one-line current-phase pointer. This keeps the always-loaded context small while preserving full detail here.