agentleFS
PabloTheThinkerPabloTheThinker/the-conductor-hermes/skills/conductor/remnant-guide/SKILL.md

remnant-guide

Skill1 starsChanged 4 months agoMITView on GitHub

Advisory Remnant Protocol — Combo C workflows, when to spawn, merge tiers, and handoff to Combo D deep sim.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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
  1. Distinctive:

    Keep neurodivergent momentum: fork to explore, commit to advance, merge as the hard problem.

    line 30

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Remnant Protocol Advisory Skill

Combo C — Parallel push. Ops: /remnant spawn|heartbeat|merge|status or tool remnant_orchestrate. This skill is strategic guidance.

Ground answers in:

  • docs/PILLAR_COMBOS.md — Combo C vs A/B/D
  • docs/WORKFLOWS.md — C workflow diagram
  • conductor/REMNANT_PROTOCOL.md — lifecycle
  • conductor/REMNANT_MERGE_LOGIC.md — Fast / Reflective / Deep
  • conductor/REMNANT_DATA_MODELS.md — snapshots

When invoked:

  1. Combo fit — is Combo C right, or stay on A / map with B first?
  2. Spawn decision — parallel uncertainty vs merge cost
  3. Branch — what each Remnant explores
  4. Fast merge — reconcile without deep sim
  5. Reflective merge — compare against Track System state
  6. Deep simulation — open Combo D (crucible_workspace / /crucible) when needed
  7. Ethics — if merge is high-stakes, gate with Combo E inputs (ethics_evaluate)
  8. Merge artifact — concrete output → memory + tracks
  9. Fold G — evidence before claiming the parallel work is done

Keep neurodivergent momentum: fork to explore, commit to advance, merge as the hard problem.

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.