start
Skill0 starsChanged 7 months agoMITView on GitHub
Session initialization and lifecycle management: bootstraps session context, organizes files, generates CLAUDE.md, manages soul purpose lifecycle with completion protocol and active context harvesting. Use when user says /start, /init, bootstrap session, initialize session, or organize project.
130 other projects use a version of this.
Adopted by
Most recently taken up by
- ansvisor/ansvisortheir own version, first seen Nov 8, 2026
- dsifry/metaswarmtheir own version, first seen Nov 8, 2026
- ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tooltheir own version, first seen Nov 8, 2026
- paulocsb/worldcup-fifa-pooltheir own version, first seen Nov 8, 2026
- srinator22/New-Projecttheir own version, first seen Nov 8, 2026
- Memolok/Claude-plugintheir own version, first seen Nov 6, 2026
Used with
Projects with it also use setup-engine, team-audio 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.
CoralGameSkillsetup-engine
Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.
Also in 13 projects that use this
CoralGameSkillteam-audio
Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.
Also in 13 projects that use this
lilangMaxSkillcreate-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 11 projects that use this
lilangMaxSkillstory-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 11 projects that use this
- +5 more from CoralGame
- +3 more from lilangMax
Other versions130 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 130
- anthropics/knowledge-work-plugins★ 35ksame name
- Donchitos/Claude-Code-Game-Studios★ 27ksame name
- openai/plugins★ 7.8ksame name
- SterlingChin/marvin-template★ 1ksame name
- educlopez/ui-craft★ 441same name
- ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool★ 432same name
- dsifry/metaswarm★ 426same name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- ansvisor/ansvisor★ 233same name
- alexeykrol/claude-code-starter★ 194same name
120 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- accomplishSkill
- codifySkill
- prd-taskmasterSkill
- research-before-codingSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 12 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 117 edited versions we read keep these.
12
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
All commands output JSON. AI only handles judgment calls (questions, assessment, continuation).
- Very specific: line 50
If templates_valid is false, STOP with error.
- Distinctive: line 56
Use AskUserQuestion with 2 questions:
- Very specific: line 68
Use an Explore agent to scan root files and propose a move map.
- Very specific: line 69
If approved, use a Bash agent to execute mkdir -p + git mv/mv operations.
- Distinctive: line 70
If skipped or root_file_count <= 10: no file moves.
- Distinctive: line 74
Run these commands sequentially.
- Distinctive: line 113
Run these commands sequentially.
- Very specific: line 123
Run /init in main thread.
- Distinctive: line 148
No questions. Skip to continuation.
- Distinctive: line 151
Ask ONE question combining assessment and decision:
- Distinctive: line 158
If "Close" or "Redefine": Run harvest + archive:
- Distinctive: line 165
If harvest returns content, AI assesses what to promote (judgment call — decisions need rationale, patterns must be reused, troubleshooting …
- Distinctive: line 174
If "Close" without new purpose: Ask if user wants to set a new soul purpose.
- Distinctive: line 184
If no active soul purpose: Ask user what to work on, write as new soul purpose via archive command.
- Distinctive: line 191
All commands output JSON. Run from project root.
“Common” is measured: kept by at least 6 in 10 of the 117 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.
Files
Session Init & Lifecycle Skill
User runs
/start. Questions upfront. Everything else silent. Then seamlessly continue working.
Script: ~/.claude/skills/start/session-init.py handles all deterministic file operations.
All commands output JSON. AI only handles judgment calls (questions, assessment, continuation).
Directive Capture
Capture any text after /start as DIRECTIVE. If empty, the soul purpose is the directive.
The skill NEVER finishes with "ready to go" and stops. After setup, immediately begin working.
UX Contract (MANDATORY)
- NEVER announce step names — no "Init Step 1", no "Wave 2"
- NEVER narrate internal process — no "Detecting environment..."
- NEVER explain what you're about to do — just ask questions, then do it silently
- User sees ONLY: questions and seamless continuation into work
- Batch questions — as few rounds as possible
- No "done" message that stops — after setup, immediately begin working
Hard Invariants
- User authority is absolute — AI NEVER closes a soul purpose. Only suggests; user decides.
- Zero unsolicited behavior — Skill ONLY runs when user types
/start. - Human-visible memory only — All state lives in files.
- Idempotent — Safe to run multiple times.
- Templates are immutable — NEVER edit files in
~/claude-session-init-templates/. - NEVER auto-invoke doubt agent. Only offer it.
INIT MODE
Triggered when preflight returns
"mode": "init".
Step 1: Silent Pre-flight
python3 ~/.claude/skills/start/session-init.py preflightReturns JSON with: mode, is_git, has_claude_md, root_file_count, templates_valid, template_count.
If templates_valid is false, STOP with error. Set internal flags from JSON. No output to user.
Step 2: User Questions
Round 1 — Ask upfront
Use AskUserQuestion with 2 questions:
Question 1: "What is the soul purpose of this project?"
- Options: "Build a product", "Fix & improve", "Research & learn" (user can type custom)
Question 2: "How should Ralph Loop work?"
- Options: "Automatic", "Manual", "Skip"
Store as SOUL_PURPOSE and RALPH_MODE.
Round 2 — File organization (only if root_file_count > 10)
Use an Explore agent to scan root files and propose a move map. Present to user for approval.
If approved, use a Bash agent to execute mkdir -p + git mv/mv operations.
If skipped or root_file_count <= 10: no file moves.
Step 3: Silent Execution
Run these commands sequentially. ZERO output to user.
# 1. Bootstrap session-context + seed active context
python3 ~/.claude/skills/start/session-init.py init \
--soul-purpose "SOUL_PURPOSE_TEXT" \
--ralph-mode "RALPH_MODE"
# 2. Ensure CLAUDE.md has all governance sections
python3 ~/.claude/skills/start/session-init.py ensure-governance \
--ralph-mode "RALPH_MODE"
# 3. Cache governance before /init
python3 ~/.claude/skills/start/session-init.py cache-governanceThen run /init in main thread (Claude command to refresh CLAUDE.md).
# 4. Restore governance if /init removed sections
python3 ~/.claude/skills/start/session-init.py restore-governanceStep 4: Continuation
Transition directly into work. No "session initialized" message.
- If DIRECTIVE provided: Begin working on directive immediately.
- If RALPH_MODE = "automatic": Invoke
/ralph-wiggum:ralph-loop. - Otherwise: Begin working on soul purpose. If too vague, ask ONE clarifying question, write clarified purpose back via
archive --new-purpose, then begin.
RECONCILE MODE
Triggered when preflight returns
"mode": "reconcile".
Step 1: Silent Assessment
Run these commands sequentially. NO output to user.
# 1. Validate session files (repair from templates if needed)
python3 ~/.claude/skills/start/session-init.py validate
# 2. Cache governance before /init
python3 ~/.claude/skills/start/session-init.py cache-governanceRun /init in main thread.
# 3. Restore governance
python3 ~/.claude/skills/start/session-init.py restore-governance
# 4. Read soul purpose + active context
python3 ~/.claude/skills/start/session-init.py read-contextReturns JSON with: soul_purpose, has_archived_purposes, active_context_summary, open_tasks, recent_progress, status_hint.
Step 2: Self-Assessment (pure reasoning, no tools)
Using the read-context JSON output, classify:
| Classification | Criteria |
clearly_incomplete | open_tasks non-empty, active blockers, criteria not met |
probably_complete | No open tasks, artifacts exist, criteria met |
uncertain | Mixed signals |
Step 3: User Interaction (conditional)
If clearly_incomplete:
No questions. Skip to continuation.
If probably_complete or uncertain:
Ask ONE question combining assessment and decision:
"Soul purpose: '[purpose text]'. [1-2 sentence assessment]. What would you like to do?"
- Options: "Continue", "Verify first", "Close", "Redefine"
If "Verify first": Dispatch doubt-agent, fold findings into re-presented question (without "Verify first" option).
If "Close" or "Redefine": Run harvest + archive:
# Check for promotable content
python3 ~/.claude/skills/start/session-init.py harvestIf harvest returns content, AI assesses what to promote (judgment call — decisions need rationale, patterns must be reused, troubleshooting must have verified solutions). Present to user for approval. After approval, append promoted content to target files via Edit tool.
# Archive old purpose, optionally set new one
python3 ~/.claude/skills/start/session-init.py archive \
--old-purpose "OLD_PURPOSE_TEXT" \
--new-purpose "NEW_PURPOSE_TEXT" # omit for close-without-redefineIf "Close" without new purpose: Ask if user wants to set a new soul purpose. If declined, the archive command writes "(No active soul purpose)".
Step 4: Continuation
Transition directly into work. No "session reconciled" message.
- If DIRECTIVE provided: Begin working on directive.
- If RALPH_MODE = "automatic" (check CLAUDE.md): Invoke
/ralph-wiggum:ralph-loop. - If soul purpose just redefined: Begin working on new purpose.
- If
clearly_incomplete: Pick up where last session left off using active context. - If no active soul purpose: Ask user what to work on, write as new soul purpose via archive command.
- Otherwise: Resume work using active context as guide.
Script Reference
All commands output JSON. Run from project root.
| Command | Purpose |
preflight | Detect mode, git, CLAUDE.md, templates, session files |
init --soul-purpose "..." --ralph-mode "..." | Bootstrap session-context, seed active context |
validate | Check/repair session files from templates |
cache-governance | Cache governance sections from CLAUDE.md to /tmp |
restore-governance | Restore cached governance sections after /init |
ensure-governance --ralph-mode "..." | Add missing governance sections to CLAUDE.md |
read-context | Read soul purpose + active context summary |
harvest | Scan active context for promotable content |
archive --old-purpose "..." [--new-purpose "..."] | Archive soul purpose, reset active context |
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
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.

