agentleFS
matteo-strategamatteo-stratega/claude-cortex/.claude/skills/start/SKILL.md

start

Skill8 starsChanged 5 months agoMITView on GitHub

Session start ritual. Loads context, checks the last closing report, and proposes priorities. Use when the user begins a work session — says "start", "let's begin", "good morning", or asks what to work on today.

139 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use project-stage-detect, team-level and 10 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.
  • CoralGameSkill

    project-stage-detect

    Automatically analyze project state, detect stage, identify gaps, and recommend next steps based on existing artifacts.

    Also in 18 projects that use this

  • CoralGameSkill

    team-level

    Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.

    Also in 13 projects that use this

  • lilangMaxSkill

    create-stories

    Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

    Also in 12 projects that use this

  • lilangMaxSkill

    story-done

    End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.

    Also in 12 projects that use this

  • +3 more from CoralGame
  • +5 more from lilangMax

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 0 are common, 5 are distinctive, and 9 are very specific to this project.

  • 0

    Common

    Most of the 126 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 9

    Very specific

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

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

    Read brain/team.md and count the entries under users:.

    line 12
  2. Distinctive:

    0 or 1 user (SOLO): run the Solo protocol below.

    line 14
  3. Distinctive:

    2 or more users (TEAM): run the Team protocol below.

    line 15
  4. Very specific:

    If brain/team.md does not exist, treat it as SOLO.

    line 17
  5. Very specific:

    Read brain/context.md (the index — always loaded).

    line 24
  6. Very specific:

    Read the latest notes/daily-summaries/closing-*.md file (if any).

    line 25
  7. Distinctive:

    Wait for the response before proceeding.

    line 36
  8. Distinctive:

    Only the session reports are per-person, so two people can work and close on the same day without overwriting each other.

    line 58
  9. Very specific:

    Ask: "Who is starting this session?" and match the answer to a handle in brain/team.md.

    line 62
  10. Very specific:

    Read brain/context.md (the shared index — always loaded).

    line 72
  11. Very specific:

    If state_isolation: per-user, also read brain/context-<user>.md if it exists (this person's own state.

    line 73
  12. Very specific:

    Read the latest notes/daily-summaries/<user>/closing-*.md (this person's own last close).

    line 79
  13. Very specific:

    Read the most recent dated entries in brain/changelog.md (if it exists) to see what teammates changed in shared brain files since this user …

    line 80
  14. Distinctive:

    If nothing is relevant, say nothing — no filler lines.

    line 95

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

Execute the session start protocol.

Step 0: Solo or team?

Read brain/team.md and count the entries under users:.

  • 0 or 1 user (SOLO): run the Solo protocol below. Do not ask who is here.
  • 2 or more users (TEAM): run the Team protocol below.

If brain/team.md does not exist, treat it as SOLO.


Solo protocol

Step 1: Load context

  1. Read brain/context.md (the index — always loaded).
  2. Read the latest notes/daily-summaries/closing-*.md file (if any).

Step 2: Propose

Summarize in max 5 bullet points:

  • What was done last session (from the closing report).
  • What is pending.
  • Current focus from the context index.

Then ask: "What are we working on today?"

Step 3: STOP

Wait for the response before proceeding.

Step 4: Load relevant context

Based on the answer, load ONLY the matching file from brain/contexts/:

User says...Load
Work, clients, sales, dealsbrain/contexts/work.md
Building, coding, projectsbrain/contexts/projects.md
Content, blog, social, videobrain/contexts/content.md
Anything elseAsk: "Is this work, building, or content?"

Never load all context files at once. One area per session.

Step 5: Work

Proceed with the task — the right context is loaded.


Team protocol

The brain (brain/context.md, brain/contexts/*, agents, hooks) is shared. Only the session reports are per-person, so two people can work and close on the same day without overwriting each other.

Step 1: Identify the user

Ask: "Who is starting this session?" and match the answer to a handle in brain/team.md.

Skip the question if the user already named themselves in this message, or the context makes it obvious. If the answer matches no handle, stop and ask again — never guess. Below, <user> is the matched handle.

Step 2: Load context

First check state_isolation in brain/team.md (absent means shared).

  1. Read brain/context.md (the shared index — always loaded).
    • If state_isolation: per-user, also read brain/context-<user>.md if it exists (this person's own state; on a first session it may not yet — that is fine, /close creates it). In that mode context.md holds only the shared header (team, this-week priorities, cross-person handoffs); each operator's deals and areas live in their own file. Do not read the other operators' context-<handle>.md files.
  2. Read the latest notes/daily-summaries/<user>/closing-*.md (this person's own last close).
  3. Read the most recent dated entries in brain/changelog.md (if it exists) to see what teammates changed in shared brain files since this user last worked.

Step 2.5: Surface only relevant teammate activity

Scan the latest closing report of each other user (notes/daily-summaries/<other>/closing-*.md). Surface an item ONLY if it is one of these — otherwise skip it:

  1. Blocker: a teammate is waiting on <user>, or <user> is blocked waiting on them. Flag as a P0 callout.
  2. Area overlap: the teammate touched something in <user>'s area (same client, deal, project, or topic).
  3. Cross-cutting decision: a teammate made a call that changes how <user> should approach today's work.

Skip routine work that does not affect <user>: internal refactors, doc maintenance, hooks/scripts, brain housekeeping, and work in areas <user> does not own. If a teammate's last close is older than 3 days, skip them entirely. If nothing is relevant, say nothing — no filler lines.

Step 3: Propose

Summarize in max 5 bullet points:

  • What <user> did last session (from their closing report).
  • What is pending on <user>'s plate.
  • Current focus from the context index, filtered to <user>'s areas.

Then ask: "What are we working on today?"

Step 4: STOP

Wait for the response before proceeding.

Step 5: Load relevant context

Same routing table as the Solo protocol (Step 4). Load ONLY the one matching file from brain/contexts/. Never load all context files at once.

Step 6: Work

Proceed with the task.

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.