agentsclimarketplace
Sign in

Coding agent pm

Skill bg-szy/TOP-SKILLS/skills/marketplace/coding-agent-pm

Plan, assign, review, and verify coding-agent work with tight scope control and clear acceptance criteria.From its SKILL.md

Install
npx -y skills add bg-szy/TOP-SKILLS --skill coding-agent-pm

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.8 KB, 331 tokens by cl100k_base, as published. Nobody here has run it

Coding Agent PM

Use this skill when a human is preparing, delegating, reviewing, or recovering implementation work done by Claude Code, Codex, OpenClaw, or another coding agent.

Operating Loop

  1. Define the shipped outcome in one sentence.
  2. Set explicit scope: files or modules owned, files or modules excluded, and any destructive actions that are forbidden.
  3. Capture the relevant context before implementation starts.
  4. Write acceptance criteria that can be checked directly.
  5. Require validation commands or manual checks before final delivery.
  6. Review the diff before accepting the work.

Assignment Rules

  • Keep the task brief concrete and bounded.
  • State whether the agent may edit files or should only inspect and plan.
  • Give ownership boundaries for code changes.
  • Tell the agent not to revert unrelated user work.
  • Prefer existing project patterns over new abstractions.
  • Require the final response to include changed files, checks run, results, and remaining risks.

Review Rules

Prioritize findings in this order:

  1. Behavioral bugs or regressions.
  2. Missing acceptance criteria.
  3. Missing tests or weak validation.
  4. Scope drift and unrelated refactors.
  5. Security, privacy, or destructive-command risk.

If the agent drifted, stop new edits and ask it to map each change back to the original acceptance criteria.

Templates

Use the templates in templates/ when a structured artifact is helpful:

  • pm-agent-brief.md
  • task-plan-template.md
  • prompt-snippets.md
  • review-checklist.md
  • first-week-agent-workflow-tracker.md

What ships with it: 5 files

28.6 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,286. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.