# Orient

> Quick orientation for a new session — shows system overview, current state, and available actions.

- Skill: `opendatadiscovery/orient` (Agent Skill)
- Install (CLI): `npx skillmds@latest add opendatadiscovery/orient`
- Raw SKILL.md: https://api.skillmd.com/api/skills/opendatadiscovery/orient/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: opendatadiscovery (https://skillmd.com/u/opendatadiscovery)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/opendatadiscovery/orient

---


# Orient

Quick orientation for working in the ODD Team maintenance system.

## Protocol

1. Read and summarize `CLAUDE.md` (2-3 sentences)
2. Read `state/PROGRESS.md` and show current phase and counts
3. List available skills:
   - `/enumerate <scanner>` — generate coverage manifest (list all items in scope)
   - `/scan <scanner>` — scan next unscanned batch from manifest
   - `/coverage [scanner]` — show what's been analyzed vs. what remains
   - `/triage <findings>` — convert findings to work items
   - `/implement <id>` — execute a work item
   - `/review <id>` — verify completed work
   - `/status` — full progress report
   - `/navigate <feature>` — find code locations
4. Check release trains (`adrs/drafts/release-train-doc-gating.md`): grep `backlog/` **and `contributor/`** for `milestone:` by status (a `backlog/`-only grep is blind to CTRIB items — LSN-041) + `git -C ../documentation branch -r --list 'origin/release/*'`. A closed milestone with `pending-release` items, or a published release whose train still exists, makes the release gate (`playbooks/release-train-merge.md`) the recommended next action.
5. Show recommended next action based on current progress
6. List any blockers or items needing attention

## Output Format

```
## ODD Team Maintenance System

{2-3 sentence summary of what this is and current phase}

### Current State
Scanners: {done}/{total} | Backlog: {count} items | Done: {count}

### Available Commands
/enumerate <scanner>     — list all items in scope (first step)
/scan <scanner>          — scan next unscanned batch
/coverage [scanner]      — what's analyzed vs. remaining
/triage <findings>       — create work items from findings
/implement <item-id>     — execute approved work item
/review <item-id>        — verify completed work
/status                  — detailed progress report
/navigate <feature>      — find code locations

### Recommended Next
{what to do next and why}
```