agentleFS
Sign inStart free
timursafiullintimursafiullin/aod/skills/session-start/SKILL.md

session-start

Skill0 starsChanged 29 days agoApache-2.0View on GitHub

Start an AOD architect session - restore state from the repository (journal next step, open tasks, slots, running jobs) and run the baseline checks before any new work. Use at the beginning of a working session or when the user says "let's continue" in an AOD project.

41 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use deploy-verify, reflect and 2 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.
  • danielarif26Skill

    deploy-verify

    Verify a Vercel deployment actually went live and serves the correct production domain. Self-improving: reads its own run history before checking and logs the outcome after. Use when the user asks "did you deploy?", "is it live?", "verify the deploy", "check vercel", or after any Vercel deploy. Part of the Agentic OS (Level 1 backbone).

    Also in 3 projects that use this

  • Microsoft AzureSkill

    reflect

    Learning capture system that extracts HIGH/MED/LOW confidence patterns from conversations to prevent repeating mistakes. Use after user corrections ("no", "wrong"), praise ("perfect", "exactly"), or when discovering edge cases. Complements .squad/agents/{agent}/history.md and .squad/decisions.md.

    Also in 4 projects that use this

  • ibahgatSkill

    autopilot

    Run autonomous multi-stage execution loops until acceptance criteria pass or blockers are reached.

    Also in 3 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    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, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 34 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the verdict is not ready, deal with that first: a red baseline is reported to the user before any new work.

    line 15
  2. Very specific:

    Read only what read_next lists plus any ADR those packets reference.

    line 17

“Common” is measured: kept by at least 6 in 10 of the 34 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

Start an architect session

The architect remembers nothing between sessions; the repository does. CLI: aod means node "${CLAUDE_PLUGIN_ROOT}/scripts/aod.mjs".

  1. aod session start — prints the last journal entry and its Next step, open tasks, running Codex jobs, slots, whether the main checkout is clean and on the base branch, any active contract unlock, and the result of the baseline commands (session.baseline in .agents/aod.config.json). read_next lists the roadmap and the packets of tasks in flight.
  2. If the verdict is not ready, deal with that first: a red baseline is reported to the user before any new work; a dirty or off-base main checkout is explained, not silently reset.
  3. Read only what read_next lists plus any ADR those packets reference. Delegate bulk reading of code to a subagent instead of reading it into this context.
  4. Pick up exactly the journal's Next step unless the user asks otherwise. For tasks in review, continue with /aod:verify; for blocked, answer the question; for finished background jobs, read their results.
  5. Tell the user in two or three lines: where things stand and what you will do now.

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.

Check your setup, free