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

pm-delivery-plan

Skill2 starsChanged 4 months agoMITView on GitHub

Split CodeFlowMu requirements into P0/P1/P2 delivery plans with owners, file scope, acceptance criteria, risks, and dependencies. Use when PM needs to dispatch work to OPS/DEV/QA/EVAL while preserving scope and FCoP boundaries.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when a large request needs executable phases, owners, file ranges, and acceptance criteria.

    line 10
  2. Distinctive:

    Keep public issue submission and archive decisions with ADMIN.

    line 17
  3. Very specific:

    Use the structure in docs/skills/pm-playbook/delivery-plan.md.

    line 21
  4. Distinctive:

    Do not dispatch unrelated files.

    line 25
  5. Distinctive:

    Do not replace ADMIN final confirmation.

    line 26
  6. Distinctive:

    Do not submit public issues automatically.

    line 27
  7. Distinctive:

    Do not change lifecycle without authority.

    line 28

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

When to use

Use this skill when a large request needs executable phases, owners, file ranges, and acceptance criteria.

Rules

  • Split work by priority and owner.
  • Include file scope and acceptance criteria per stage.
  • Name forbidden items.
  • Keep public issue submission and archive decisions with ADMIN.

Required output

Use the structure in docs/skills/pm-playbook/delivery-plan.md.

Forbidden actions

  • Do not dispatch unrelated files.
  • Do not replace ADMIN final confirmation.
  • Do not submit public issues automatically.
  • Do not change lifecycle without authority.

Minimal example

P0: add manifest and mapping docs, owner DEV
P1: add PM Playbook docs, owner DEV
P2: validate and report, owner DEV

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