agentleFS
lynchypinlynchypin/project-onboard/skills/start-session/SKILL.md

start-session

Skill0 starsChanged 3 months agoMITView on GitHub

Orient a new session in any project directory. Detects empty directory, existing codebase, or resume state, gathers cheap signals, and routes to wayfinder. The only user-invoked entry point.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 3 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run once at the beginning of a conversation to orient.

    line 9
  2. Very specific:

    Check whether .agent/state.json exists in the project root.

    line 27
  3. Very specific:

    Read .agent/state.json in full.

    line 33
  4. Very specific:

    Check schema version: If version is 1 (v1 state), tell the user: "This project has v1 state from an earlier version of the plugin.

    line 34
  5. Very specific:

    Read the wayfinder map (at map_ref path) and any CONTEXT.md or ADRs.

    line 38
  6. Very specific:

    If size class is medium or large, invoke skills/scope-lock/SKILL.md before any broad reading.

    line 72
  7. Distinctive:

    Never start implementation before wayfinder has completed its map.

    line 79
  8. Very specific:

    Never re-run the full orient when .agent/state.json already exists (use Path A instead).

    line 80
  9. Distinctive:

    Never read broadly across a medium/large repo before scope-lock runs.

    line 82

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

Run once at the beginning of a conversation to orient. Gathers cheap signals and routes to wayfinder.

Bundled skills (always available)

The following mattpocock/skills ship with this plugin in skills/ — no external detection or installation needed:

grilling, grill-with-docs, domain-modeling, tdd, prototype, codebase-design, diagnosing-bugs, improve-codebase-architecture

These are referenced at specific integration points by wayfinder, implement, to-spec, and code-review.

Process

Step 1: Determine which path applies

Check whether .agent/state.json exists in the project root.


Path A: Resume (.agent/state.json exists)

  1. Read .agent/state.json in full.
  2. Check schema version. If version is 1 (v1 state), tell the user: "This project has v1 state from an earlier version of the plugin. Would you like me to migrate it to v2, or start fresh?" Act on their answer.
  3. Read the wayfinder map (at map_ref path) and any CONTEXT.md or ADRs.
  4. Summarize current status to the user: what the destination is, which tickets are done, which are next.
  5. Resume: read the map and pick up the next unresolved ticket.

Path B: Empty directory (no substantive files)

Count files excluding .git*, .agent*, README*, LICENSE*, .gitignore, .gitattributes. If zero:

  1. Tell the user: "This directory is empty — treating as a new project."
  2. Invoke skills/setup/SKILL.md to configure the tracker.
  3. Invoke skills/wayfinder/SKILL.md — the first ticket on the map will be a grilling ticket to establish what the project is.

Path C: Existing codebase (has files)

Gather cheap heuristic signals:

  1. Tracked files — git ls-files | wc -l (or directory file count).
  2. Approximate LOC — count lines across common source extensions.
  3. Existing documentation — check for CONTEXT.md, docs/CONTEXT.md, docs/agents/, docs/adr/, docs/architecture/.
  4. Size class — large (300+ files or 30k+ LOC), medium (40+ or 3k+), small (everything else).

Report signals to the user, then:

  1. Invoke skills/setup/SKILL.md to configure the tracker.
  2. If size class is medium or large, invoke skills/scope-lock/SKILL.md before any broad reading.
  3. Invoke skills/wayfinder/SKILL.md — the first ticket on the map will be a grilling ticket to establish what the user wants to do.

What this skill must never do

  • Never start implementation before wayfinder has completed its map.
  • Never re-run the full orient when .agent/state.json already exists (use Path A instead).
  • Never read broadly across a medium/large repo before scope-lock runs.

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.