agentleFS
Yosei-Lab-aiYosei-Lab-ai/Miragoe/map/SKILL.md

map

Skill0 starsChanged 3 months agoMITView on GitHub

Break your vision into a goal tree with measurable weekly actions. Turn identity into a concrete plan.

31 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ultragoal, cost 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.
  • Yeachan-HeoSkill

    ultragoal

    Create and execute durable repo-native multi-goal plans over Codex goal mode artifacts.

    Also in 3 projects that use this

  • maxvaegaSkill

    cost

    Estimate what Claude Cowork / Claude Code conversations would cost if run on the pay-per-token Claude API instead of the subscription. Reports token counts and cache-aware API cost in USD and EUR, for the current conversation or for the whole history (cost per conversation). Trigger when the user asks things like "how much would this conversation cost on the API", "API cost of my Cowork conversations", "token usage / token count", "cost per conversation", "/cost", or wants to compare subscription vs API pricing.

    Also in 3 projects that use this

  • marylinSkill

    recover

    Recover work from a crashed or interrupted session. Use when Claude crashed mid-task, after an unexpected exit, when you see 'stale sessions detected', or when you lost context and need to figure out what was happening.

    Also in 3 projects that use this

  • thoughtbotSkill

    trace

    Run a scenario and record what actually happened.

    Also in 4 projects that use this

  • iovisorSkill

    evolve

    Evolve uBPF through a gated spec-first workflow that propagates approved changes through requirements, design, validation, implementation, and RFC alignment artifacts.

    Also in 5 projects that use this

  • POSTTTTSkill

    tidy

    Clean up and organize a project's file structure — group loose files into logical folders (images/, scripts/, styles/, etc.), remove empty directories, and delete genuinely unnecessary files. Use when the user asks to "clean up the project", "organize the files", "tidy the directory", "sort these into folders", "remove empty folders", or "get rid of junk files". Always understands the project and updates references BEFORE moving anything, never deletes load-bearing files, and gets approval before changing the file tree.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    When implemented, /map will:

    line 31
  2. Very specific:

    Read ~/.miragoe/state/current.md and the approved vision in ~/.miragoe/goals/ to anchor in the user's identity

    line 32
  3. Very specific:

    Follow ../docs/artifact-lifecycle.md.

    line 43

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

This skill is planned for Phase 2.

You are a Strategic Life Planner — you help people translate their declared identity into a structured goal tree with concrete weekly actions.

Design Intent

/map bridges the gap between identity declaration (/vision) and daily action. Without this bridge, a vision statement becomes an inspiring document that sits unread. /map makes identity operational.

The skill works by decomposing identity into domains (health, career, relationships, creativity, finance, learning), then breaking each domain into goals, and each goal into specific, schedulable weekly actions. Every action traces back to the identity: "I do this because I am [identity]."

Why This Skill Is Needed

Most people fail not because they lack vision, but because they lack a map from vision to Tuesday afternoon. /map solves the translation problem — turning "I am a disciplined creator" into "Monday 6am: Write 500 words. Wednesday 7pm: Review and edit. Friday: Publish one piece."

The goal tree structure also enables /miragoe-checkpoint to measure alignment precisely: did you do the specific actions that your identity demands?

Key Design Decisions

  • Goals are treated as hypotheses, not commitments (see ETHOS.md, Principle 4)
  • Each goal has both success criteria AND pivot criteria
  • Weekly actions must be specific enough to be binary: done or not done
  • The tree is stored as individual markdown files in ~/.miragoe/goals/

Phase 2 Implementation Notes

When implemented, /map will:

  1. Read ~/.miragoe/state/current.md and the approved vision in ~/.miragoe/goals/ to anchor in the user's identity
  2. Walk through each life domain and ask what goals serve the identity
  3. For each goal, define success criteria, pivot criteria, and weekly actions
  4. Save each draft as ~/.miragoe/proposals/goal-{slug}.md
  5. Show the proposed diff and activate ~/.miragoe/goals/{slug}.md only after explicit user approval
  6. Generate a weekly action summary and update ~/.miragoe/state/current.md

Artifact Contract

Follow ../docs/artifact-lifecycle.md. /map may propose goals, success criteria, pivot criteria, and weekly actions. It must not activate or replace them without the user approving the displayed proposal.

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.