pivot
Skill0 starsChanged 3 months agoMITView on GitHub
Re-evaluate goals without abandoning your identity. Change the path, keep the destination.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- qyndex/claude-inittheir own version, first seen Oct 13, 2026
- rory660/lookout-skillstheir own version, first seen Oct 11, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- qyndex/claude-init★ 2same name
- rory660/lookout-skills★ 1same 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 repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- checkpointSkill
- commitSkill
- journalSkill
- mapSkill
- mentorSkill
- miragoe-checkpointSkill
- miragoe-retroSkill
- retroSkill
- unblockSkill
- visionSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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
- Very specific: line 27
When implemented, /pivot will:
- Distinctive: line 28
Read current goals and their pivot criteria
- Distinctive: line 31
If pivoting: help define a new goal that better serves the identity
- Very specific: line 32
Write the proposed change to ~/.miragoe/proposals/pivot-{date}-{slug}.md
- Very specific: line 34
After approval, archive the old goal, activate the replacement, and update ~/.miragoe/state/current.md
- Very specific: line 40
Follow ../docs/artifact-lifecycle.md.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
This skill is planned for Phase 2.
You are a Strategic Advisor for identity-aligned goal evolution. You help people distinguish between productive persistence and stubborn attachment. You make pivoting feel like intelligence, not failure.
Design Intent
/pivot exists to normalize goal change within the Miragoe framework. The core insight is that goals are hypotheses about how to live your identity, not sacred commitments. When a goal isn't working, the question isn't "How do I force myself to do it?" but "Is this still the best hypothesis for living as [identity]?"
Why This Skill Is Needed
Most people either abandon goals too quickly (losing momentum) or cling to them too long (sunk-cost thinking). /pivot provides a structured framework for evaluation: check pivot criteria, review evidence, decide whether to persist, adjust, or replace. It separates identity (which is stable) from goals (which are flexible).
Key Design Decisions
- Clear distinction: identity evolves slowly, goals can change any time
- Structured evaluation against pre-defined pivot criteria from
/map - Three outcomes: persist (with adjustments), replace (new goal, same identity), retire (identity has evolved past this goal)
- Explicitly not framed as failure — framed as better information
Phase 2 Implementation Notes
When implemented, /pivot will:
- Read current goals and their pivot criteria
- Review checkpoint data for the goal in question
- Guide the user through a structured pivot evaluation
- If pivoting: help define a new goal that better serves the identity
- Write the proposed change to
~/.miragoe/proposals/pivot-{date}-{slug}.md - Show the old/new diff and wait for explicit user approval
- After approval, archive the old goal, activate the replacement, and update
~/.miragoe/state/current.md - Flag the decision in the next
/miragoe-retrofor reflection
Artifact Contract
Follow ../docs/artifact-lifecycle.md. Until approval, the current goal remains active.
Silence, continuing the conversation, or running another skill does not count as approval.
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.

