agentleFS
opendatadiscoveryopendatadiscovery/odd-team/.claude/skills/orient/SKILL.md

orient

Skill0 starsChanged 2 months agoApache-2.0View on GitHub

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

27 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use retro, ui-ux-pro-max and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AWSSkill

    retro

    Conduct a retrospective on a coding session.

    Also in 3 projects that use this

  • StrayDragonSkill

    ui-ux-pro-max

    UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

    Also in 3 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read and summarize CLAUDE.md (2-3 sentences)

    line 13
  2. Very specific:

    Read state/PROGRESS.md and show current phase and counts

    line 14

“Common” is measured: kept by at least 6 in 10 of the 25 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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}

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.