state
Skill425 starsChanged 5 months agoMITView on GitHub
Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.
8 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- microsoft/Copilot-Managed-Runtimetheir own version, first seen Nov 8, 2026
- synaptiai/agent-capability-standardtheir own version, first seen Nov 1, 2026
- gr219/OpenBA-Kittheir own version, first seen Oct 25, 2026
- aihu-project/aihutheir own version, first seen Oct 20, 2026
- spmtitsolution/OpenBA-Kittheir own version, first seen Oct 20, 2026
- aigengame/skillstheir own version, first seen Oct 17, 2026
Used with
Projects with it also use discover and delegate.
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.
anombyte93Skilldiscover
Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.
Also in 3 projects that use this
scott2bSkilldelegate
Intelligently analyzes tasks and delegates them to the most appropriate AI system when delegation adds value (project, gitignored)
Also in 3 projects that use this
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- vbrevik/claude_code_skills★ 097% same
Wrote their own version · 7
- spmtitsolution/OpenBA-Kit★ 38same name
- synaptiai/agent-capability-standard★ 6same name
- aihu-project/aihu★ 4same name
- microsoft/Copilot-Managed-Runtime★ 4same name
- aigengame/skills★ 2same name
- vlting/claude-skills★ 2same name
- gr219/OpenBA-Kit★ 0same name
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 repository87 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- memstack-automation-api-integrationSkill
- memstack-automation-content-pipelineSkill
- memstack-automation-cron-schedulerSkill
- memstack-automation-hosted-mcp-catalogSkill
- memstack-automation-n8n-workflow-builderSkill
- memstack-automation-webhook-designerSkill
- memstack-business-client-onboardingSkill
- memstack-business-contract-templateSkill
- memstack-business-financial-modelSkill
- memstack-business-freelancer-toolkitSkill
- memstack-business-gdprSkill
- memstack-business-invoice-generatorSkill
- memstack-business-licensingSkill
- memstack-business-proposal-writerSkill
- memstack-business-scope-of-workSkill
- memstack-business-sop-builderSkill
- compressSkill
- memstack-content-blog-postSkill
- memstack-content-email-sequenceSkill
- memstack-content-landing-page-copySkill
- memstack-content-newsletterSkill
- memstack-content-product-descriptionSkill
- memstack-content-tiktok-scriptSkill
- memstack-content-twitter-threadSkill
- memstack-content-youtube-scriptSkill
- memstack-deployment-ci-cd-pipelineSkill
- memstack-deployment-docker-setupSkill
- memstack-deployment-domain-sslSkill
- memstack-deployment-hetzner-setupSkill
- memstack-deployment-netlify-deploySkill
- memstack-deployment-railway-deploySkill
- memstack-development-api-designerSkill
- memstack-development-changelog-generatorSkill
- memstack-development-code-reviewerSkill
- memstack-development-mentorSkill
- memstack-development-migration-plannerSkill
- memstack-development-performance-auditSkill
- memstack-development-refactor-plannerSkill
- memstack-development-test-writerSkill
- memstack-development-webapp-testingSkill
- diarySkill
- echoSkill
- familiarSkill
- forgeSkill
- goalSkill
- governorSkill
- grimoireSkill
- humanizeSkill
- memstack-marketing-competitor-analysisSkill
- memstack-marketing-facebook-adSkill
- memstack-marketing-google-adSkill
- memstack-marketing-launch-planSkill
- memstack-marketing-lead-magnetSkill
- memstack-marketing-marketplace-submitSkill
- memstack-marketing-pricing-strategySkill
- memstack-marketing-sales-funnelSkill
- memstack-marketing-webinar-scriptSkill
- memstack-product-feature-specSkill
- memstack-product-feedback-analyzerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
When this skill activates, output:
- Distinctive: line 38
If found, read it and present a brief summary:
- Distinctive: line 42
If not found, say: "No STATE.md exists yet.
“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.
Files
📍 State: Updating Project State...
Maintain a living document of where you are right now in a project.
Activation
When this skill activates, output:
📍 State: Updating project state...
Then execute the protocol below.
Context Guard
| Context | Status | Priority |
| User says "update state", "save state", "project state" | ACTIVE: update STATE.md | P1 |
| User says "where was I", "where did I leave off" | ACTIVE, read and present STATE.md | P1 |
| User starts a session and STATE.md exists | ACTIVE, read silently, use as context | P2 |
| User says "save diary" or "log session" | DORMANT, Diary handles full session logs | none |
| User says "save project" or "handoff" | DORMANT, Project skill handles lifecycle | none |
| User asks to recall past sessions | DORMANT, Echo handles historical recall | none |
Protocol
Reading State (session start or "where was I")
- Check for STATE.md in the current project's
.claude/directory:{project_dir}/.claude/STATE.md - If found, read it and present a brief summary:
- What was being worked on
- Any blockers
- The immediate next step
- If not found, say: "No STATE.md exists yet. I can create one after we start working."
Writing/Updating State
- Gather current state:
- What task/phase is actively being worked on right now
- Decisions made during this session (with rationale)
- Open blockers or unanswered questions
- Explicit next steps (not vague, specific enough to resume cold)
- Key files modified recently
- Check git status for uncommitted work:
git status --short - Write STATE.md to the project's
.claude/directory:# Project State *Last updated: {YYYY-MM-DD HH:MM}* ## Currently Working On {Active task or phase: be specific} ## Decisions Made - {Decision}: {Rationale} ## Blockers - [ ] {Blocker description} ## Next Steps 1. {Immediate next action, specific enough to start cold} 2. {Following action} ## Recently Modified Files - {file path}: {what changed} ## Uncommitted Changes {List any unstaged/uncommitted work, or "None: clean working tree"} - Confirm with a brief summary of what was saved.
Deconfliction
| Skill | What it tracks | When |
| State | Current snapshot, where you are right now | During session, living document |
| Diary | Historical log, what you did in a session | End of session, append-only |
| Project | Project lifecycle, handoff between sessions | Session boundaries |
| Work | Task list, what needs to be done | When planning/tracking todos |
State is the present tense complement to Diary's past tense. State tells you where to resume; Diary tells you what happened.
Inputs
- Current working context (project, files, git status)
- User's description of current state (or auto-detected from session)
Outputs
{project_dir}/.claude/STATE.md: updated living document- Brief confirmation summary
Example Usage
User: "update state"
📍 State: Updating project state...
Saved: C:\Projects\AdminStack\.claude\STATE.md
Currently: Building CC Monitor notification system
Blockers: None
Next: Wire up WebSocket events to notification dropdown
This will auto-load next session for seamless pickup.Level History
- Lv.1: Base: Living STATE.md creation and update protocol. Read via Work Step 0 or manual invocation. Deconfliction with Diary/Project/Work. (Origin: MemStack v3.1, Feb 2026)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

