agentleFS
Sign inStart free
loganware05loganware05/captains-compass-cursor/.cursor/skills/worktree-orchestration/SKILL.md

worktree-orchestration

Skill2 starsChanged 32 days agoMITView on GitHub

Creates branches, rollback checkpoints, and isolated Git worktrees for approved work

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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:

    Create or reference the issue.

    line 24
  2. Distinctive:

    Create the feature/fix branch with the required naming convention.

    line 26
  3. Distinctive:

    Create isolated worktrees only when workstreams are cleanly separable.

    line 27
  4. Distinctive:

    If workstreams share central files, convert to sequential execution.

    line 28
  5. Distinctive:

    Do not implement on main, master, develop, or protected release branches.

    line 37
  6. Distinctive:

    Do not create parallel worktrees that will conflict on the same files.

    line 38
  7. Distinctive:

    Do not proceed without an approved plan.

    line 39

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

Worktree Orchestration

Use this Skill when

An implementation plan has been approved and work must be provisioned safely, or when parallel workstreams need isolated checkouts.

Inputs

  • Approved IMPLEMENTATION_PLAN.md
  • Issue reference
  • Base branch
  • Workstream file boundaries

Procedure

  1. Confirm plan status is APPROVED with an approval record.
  2. Confirm current branch is not a protected base branch.
  3. Create or reference the issue.
  4. Record a rollback checkpoint (annotated tag or documented SHA).
  5. Create the feature/fix branch with the required naming convention.
  6. Create isolated worktrees only when workstreams are cleanly separable.
  7. If workstreams share central files, convert to sequential execution.
  8. Hand off paths and branch names to specialist agents.

Output

Branch names, worktree paths, rollback checkpoint reference, and workstream assignment map.

Prohibited actions

  • Do not implement on main, master, develop, or protected release branches.
  • Do not create parallel worktrees that will conflict on the same files.
  • Do not proceed without an approved plan.

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