Coding agent pm
Skill aiskillstore/marketplace/skills/kiwi-phantomworks/coding-agent-pm
Security-audited skills for Claude, Codex & Claude Code. One-click install, quality verified.
npx -y skills add aiskillstore/marketplace --skill coding-agent-pmAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing 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.
What its author says it does
Copied from the file, not written here
Plan, assign, review, and verify coding-agent work with tight scope control and clear acceptance criteria.
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
- Define the shipped outcome in one sentence.
- Set explicit scope: files or modules owned, files or modules excluded, and any destructive actions that are forbidden.
- Capture the relevant context before implementation starts.
- Write acceptance criteria that can be checked directly.
- Require validation commands or manual checks before final delivery.
- 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:
- Behavioral bugs or regressions.
- Missing acceptance criteria.
- Missing tests or weak validation.
- Scope drift and unrelated refactors.
- 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.mdtask-plan-template.mdprompt-snippets.mdreview-checklist.mdfirst-week-agent-workflow-tracker.md