agentleFS
Sign inStart free
joinwell52-AIjoinwell52-AI/CodeFlowMu-open/skills/pm-scope-control/SKILL.md

pm-scope-control

Skill2 starsChanged 4 months agoMITView on GitHub

Control CodeFlowMu task scope and prevent drive-by expansion. Use when PM must define allowed files, forbidden files, non-goals, risk expansion points, or when an agent proposes refactors, runtime changes, protocol changes, or external skill imports beyond the task.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill before dispatching work or when a task is growing beyond its original intent.

    line 10
  2. Distinctive:

    Treat external skills as inspiration only unless separately approved.

    line 17
  3. Very specific:

    Use the structure in docs/skills/pm-playbook/scope-control.md.

    line 21
  4. Distinctive:

    Do not expand the formal FCoP protocol.

    line 25
  5. Very specific:

    Do not add adopted-pending 0003.

    line 26
  6. Distinctive:

    Do not perform drive-by refactors.

    line 27
  7. Distinctive:

    Do not copy external skills wholesale.

    line 28
  8. Distinctive:

    Do not turn Playbook into runtime API.

    line 29

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

PM Scope Control

When to use

Use this skill before dispatching work or when a task is growing beyond its original intent.

Rules

  • Name allowed and forbidden change areas.
  • Keep non-goals explicit.
  • Split large or risky work into separate tasks.
  • Treat external skills as inspiration only unless separately approved.

Required output

Use the structure in docs/skills/pm-playbook/scope-control.md.

Forbidden actions

  • Do not expand the formal FCoP protocol.
  • Do not add adopted-pending 0003.
  • Do not perform drive-by refactors.
  • Do not copy external skills wholesale.
  • Do not turn Playbook into runtime API.

Minimal example

Allowed: docs/skills, skills/*/SKILL.md, agent manifest
Forbidden: PmGovernancePlanner, Panel API, FCoP protocol files

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