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

retro

Skill0 starsChanged 3 months agoMITView on GitHub

Reflect on your cycle — what worked, what didn't, and what you learned about who you are.

193 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use plan-tune, ios-clean 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.
  • ShreyRaviSkill

    plan-tune

    Self-tuning question sensitivity + developer psychographic for gstack (v1: observational). Review which AskUserQuestion prompts fire across gstack skills, set per-question preferences (never-ask / always-ask / ask-only-for-one-way), inspect the dual-track profile (what you declared vs what your behavior suggests), and enable/disable question tuning. Conversational interface — no CLI syntax required.

    Also in 9 projects that use this

  • Saqlain-811Skill

    ios-clean

    Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)

    Also in 5 projects that use this

  • Saqlain-811Skill

    ios-fix

    Autonomous iOS bug fixer. (gstack)

    Also in 5 projects that use this

  • seek888Skill

    pair-agent

    Pair a remote AI agent with your browser. One command generates a setup key and prints instructions the other agent can follow to connect. Works with OpenClaw, Hermes, Codex, Cursor, or any agent that can make HTTP requests. The remote agent gets its own tab with scoped access (read+write by default, admin on request). Use when asked to "pair agent", "connect agent", "share browser", "remote browser", "let another agent use my browser", or "give browser access". (gstack) Voice triggers (speech-to-text aliases): "pair agent", "connect agent", "share my browser", "remote browser access".

    Also in 11 projects that use this

  • ShreyRaviSkill

    landing-report

    Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)

    Also in 8 projects that use this

  • timurgaleevSkill

    document-generate

    Generate missing docs for a feature, module or project as tutorials, how-tos, reference and explanation.

    Also in 7 projects that use this

  • +1 more from Saqlain-811
  • +2 more from ShreyRavi

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 171 edited versions we read keep these.

  • 2

    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, /miragoe-retro will:

    line 28
  2. Distinctive:

    Read all checkpoints since the last retro

    line 29
  3. Distinctive:

    Put suggested identity, goal, or commitment changes in a clearly labeled proposal

    line 34
  4. Very specific:

    Update ~/.miragoe/state/current.md and suggest /commit for the next cycle

    line 35
  5. Very specific:

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

    line 39

“Common” is measured: kept by at least 6 in 10 of the 171 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 Reflective Guide — you help people extract meaning from their experiences without judgment. You ask the questions that surface patterns invisible to the person living them.

Design Intent

/miragoe-retro is the learning engine of Miragoe. While /miragoe-checkpoint measures alignment, /miragoe-retro asks why. Why did certain actions come easily? Why did others feel impossible? What does the pattern reveal about who you really are versus who you declared yourself to be?

Why This Skill Is Needed

Experience without reflection is just repetition. /miragoe-retro prevents the common failure mode of personal development: doing the same thing cycle after cycle while expecting different results. By structured reflection, the user evolves both their tactics and — when necessary — their identity itself.

Key Design Decisions

  • Structured around three questions: What worked? What didn't? What did I learn about myself?
  • Explicitly asks whether any goals should change (connects to /pivot)
  • Requires specific evidence, not general impressions
  • Looks for patterns across multiple checkpoints, not just the latest one
  • Saved to ~/.miragoe/miragoe-retros/{date}.md

Phase 2 Implementation Notes

When implemented, /miragoe-retro will:

  1. Read all checkpoints since the last retro
  2. Analyze alignment score trends and action completion patterns
  3. Guide a structured reflection conversation
  4. Explicitly ask: "Should any goals change? Should your identity statement evolve?"
  5. Save a new immutable retrospective to ~/.miragoe/miragoe-retros/{date}-{id}.md
  6. Put suggested identity, goal, or commitment changes in a clearly labeled proposal
  7. Update ~/.miragoe/state/current.md and suggest /commit for the next cycle

Artifact Contract

Follow ../docs/artifact-lifecycle.md. /miragoe-retro records evidence and proposes changes; it never rewrites the approved vision, goals, or commitments by itself.

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.