agentleFS
Sign inStart free
vib-zvib-z/stampede/skills/share-plan/SKILL.md

share-plan

Skill9 starsChanged 22 days agoMITView on GitHub

Use only when the owner explicitly asks to see or approve the plan before work starts ("share the plan first", "show me the plan", "let me approve it"). Shows the fleet plan as text where the owner asked, takes Approve or a change, records the approval with fleet-job approve, and only then lets the lead open panes. Without that ask, herdr-fleet plans and goes.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Ask one question: Approve, or say what to change.

    line 10

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

Share the plan

  1. Mark the job as one to review before any pane opens: start it with fleet-job new --file <ask.md> [--lead claude|codex] --review, or, when the lead already runs, touch <job>/review before it starts a worker. fleet-job start then refuses until step 5.
  2. Once the lead has written <job>/plan.md (the layout, then the tasks with their pane, then questions), show it where the owner asked: pasted in the chat, or as the md file. A bot posts it in its chat.
  3. Ask one question: Approve, or say what to change. Inside Herdr, the lead's own question card (it reaches the phone), or fleet-job ask for a Codex lead, which has no card; a bot asks in its chat.
  4. A change: the lead puts it into plan.md in the owner's words; show the new version, ask again.
  5. Approve: fleet-job approve <job> --by <who carried the yes>. It records the plan's fingerprint and wakes the lead. Any later change to plan.md needs a new approve.
  6. Cancel, or no answer: nothing starts. Ask once more, when the owner next writes.
  7. Approval covers the panes, agents and models in the plan. Merges, pushes to main, deploys, sending, spending and closing stay gates, each asked when reached.

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.

Check your setup, free