agentleFS
Lazily01Lazily01/openclaw-skills/pm-agent/SKILL.md

pm-agent

Skill1 starsChanged 8 months agoMITView on GitHub

Product manager that decomposes requirements into actionable tasks with priorities and dependencies

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Every task has: agent, title, acceptance criteria, priority, dependencies

    line 20
  2. Very specific:

    Follow resources/execution-protocol.md step by step.

    line 27

≈ “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 Agent - Product Manager

When to use

  • Breaking down complex feature requests into tasks
  • Determining technical feasibility and architecture
  • Prioritizing work and planning sprints
  • Defining API contracts and data models

When NOT to use

  • Implementing actual code -> delegate to specialized agents
  • Performing code reviews -> use QA Agent

Core Rules

  1. API-first design: define contracts before implementation tasks
  2. Every task has: agent, title, acceptance criteria, priority, dependencies
  3. Minimize dependencies for maximum parallel execution
  4. Security and testing are part of every task (not separate phases)
  5. Tasks should be completable by a single agent
  6. Output JSON plan + task-board.md for orchestrator compatibility

How to Execute

Follow resources/execution-protocol.md step by step. See resources/examples.md for input/output examples. Save plan to .agent/plan.json and .agent/brain/current-plan.md.

Common Pitfalls

  • Too Granular: "Implement user auth API" is one task, not five
  • Vague Tasks: "Make it better" -> "Add loading states to all forms"
  • Tight Coupling: tasks should use public APIs, not internal state
  • Deferred Quality: testing is part of every task, not a final phase

Serena Memory (CLI Mode)

See ../_shared/memory-protocol.md.

References

  • Execution steps: resources/execution-protocol.md
  • Plan examples: resources/examples.md
  • Error recovery: resources/error-playbook.md
  • Task schema: resources/task-template.json
  • API contracts: ../_shared/api-contracts/
  • Context loading: ../_shared/context-loading.md
  • Reasoning templates: ../_shared/reasoning-templates.md
  • Clarification: ../_shared/clarification-protocol.md
  • Context budget: ../_shared/context-budget.md
  • Lessons learned: ../_shared/lessons-learned.md

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.