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

pm-product-requirements

Skill2 starsChanged 4 months agoMITView on GitHub

Turn vague ADMIN requests, chat feedback, screenshots, and workflow complaints into scoped CodeFlowMu product requirements. Use when PM needs PRD-style clarification, user stories, goals, non-goals, constraints, risks, or task input while preserving FCoP boundaries.

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 when a request is fuzzy, a UI or workflow complaint needs structure, or PM needs to prepare a TASK input.

    line 10
  2. Distinctive:

    Keep requirements inside CodeFlowMu/FCoP boundaries.

    line 15
  3. Very specific:

    Use the structure in docs/skills/pm-playbook/product-requirements.md.

    line 21
  4. Distinctive:

    Do not turn requirements into protocol changes.

    line 25
  5. Very specific:

    Do not add adopted-pending 0003.

    line 26
  6. Distinctive:

    Do not claim unimplemented runtime features exist.

    line 27
  7. Distinctive:

    Do not submit public GitHub issues automatically.

    line 28
  8. Distinctive:

    Do not bypass ADMIN.

    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 Product Requirements

When to use

Use this skill when a request is fuzzy, a UI or workflow complaint needs structure, or PM needs to prepare a TASK input.

Rules

  • Separate background, problem, goal, scope, non-scope, constraints, acceptance, risks, and split.
  • Keep requirements inside CodeFlowMu/FCoP boundaries.
  • Mark assumptions and unknowns.
  • Preserve existing PM runtime skill IDs.

Required output

Use the structure in docs/skills/pm-playbook/product-requirements.md.

Forbidden actions

  • Do not turn requirements into protocol changes.
  • Do not add adopted-pending 0003.
  • Do not claim unimplemented runtime features exist.
  • Do not submit public GitHub issues automatically.
  • Do not bypass ADMIN.

Minimal example

Goal: make PM review evidence visible
Scope: docs and manifest only
Non-scope: Panel/API runtime changes
Acceptance: docs exist, manifest parses

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