agentleFS
leonkoellerwirth-archleonkoellerwirth-arch/kickoff-ai/.claude/skills/session-start/SKILL.md

session-start

Skill1 starsChanged 3 months agoMITView on GitHub

Open a work session — reconstruct the exact project state from the deterministic scripts and repo memory (CONSTITUTION → BIBLE.md → HANDOFF.md) before changing anything, so work continues without drift. Counterpart to session-stop. Trigger: "session-start", "continue", "where were we", "new session", "catch me up", "weiter", start of a work session.

42 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use session-end, deploy-verify and 3 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.
  • jasonmichaelbell78-creatorSkill

    session-end

    Also in 12 projects that use this

  • 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

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

  • 0

    Common

    Most of the 35 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep it to a few lines. The goal is "caught up and grounded", not a wall of output.

    line 27

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

session-start

Reconstruct the exact state before touching anything. Facts first (deterministic), reasoning second.

Steps

  1. Read the constitution chain (highest precedence first): dev/base/CONSTITUTION.md, then this repo's BIBLE.md (invariants + open decisions), then the newest HANDOFF.md entry. If a family constitution / ECOSYSTEM.md is referenced, read it before the repo's own docs.
  2. Run the backbone (zero AI):
    • ./scripts/state.sh — branch, ahead/behind, source/test counts, last commits, newest HANDOFF.
    • ./scripts/gate.sh — is the tree already green? (don't fix yet, just know.)
  3. Layer in the plugin context (if available). The session hook may have injected a claude-mem block (timeline, observation IDs, token stats). Treat it as background. If it contradicts BIBLE.md, BIBLE.md wins. If an observation names a file, function or flag, verify it against the code before building on it.
  4. Report back, briefly: where we are, what the newest HANDOFF says is Next, and whether any blocking decision is open in BIBLE.md or the gate is red.
  5. Do not start substantive work while a blocking decision is open or the gate is red — resolve or surface that first.

Keep it to a few lines. The goal is "caught up and grounded", not a wall of output.

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.