Coding-agent projects can drift when tasks, scope, and checks are vague. This skill gives PM templates and review rules that keep Claude, Codex, and Claude Code work bounded and verifiable.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "coding-agent-pm" from https://skillstore.io/skills/kiwi-phantomworks-coding-agent-pm.md and its manifest at https://skillstore.io/api/skills/kiwi-phantomworks-coding-agent-pm/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.
Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
All 19 static findings are false positives after context review. The hidden-directory entries are documented installation paths, the backtick hits are Markdown filename formatting, and the reconnaissance hits are benign marketing or review checklist text.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Bridge AI Labs. (2026). coding-agent-pm security audit report (audit version 4) [Author version 1.0.1]. Skillstore. https://skillstore.io/skills/kiwi-phantomworks-coding-agent-pm/audits/4
BibTeX citation
@techreport{bridge-ai-labs-kiwi-phantomworks-coding-agent-pm-2026,
author = {Bridge AI Labs},
title = {coding-agent-pm security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/kiwi-phantomworks-coding-agent-pm/audits/4},
note = {Author version 1.0.1}
}
CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "coding-agent-pm security audit report (audit version 4)"
version: "1.0.1"
type: report
authors:
- name: "Bridge AI Labs"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/kiwi-phantomworks-coding-agent-pm/audits/4"
identifiers:
- type: other
value: "skillstore:kiwi-phantomworks-coding-agent-pm:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this scoreEvidence Confidence: Medium
55
Architecture
100
Maintainability
87
Content
67
Community
91
Spec Compliance
What You Can Build
Prepare a first agent task
Create a clear brief with scope, context, acceptance criteria, and validation steps before a coding agent starts work.
Review implementation work
Check whether a completed agent change stayed in scope, met requirements, ran checks, and reported remaining risks.
Coordinate parallel agent assignments
Split implementation work into bounded tasks with separate file ownership, expected outputs, and review checkpoints.
Try These Prompts
Create a basic task brief
Use coding-agent-pm to turn this request into a short agent brief. Include the outcome, in-scope files, out-of-scope files, acceptance criteria, and validation commands.
Plan a scoped implementation
Use coding-agent-pm to prepare an implementation plan for this feature. Keep the plan limited to the named modules, identify required context, and define checks the agent must run before final delivery.
Review a completed agent change
Use coding-agent-pm to review this agent result. Put findings first, compare the change against the original acceptance criteria, and list any missing checks, scope drift, or security and privacy risks.
Design parallel agent assignments
Use coding-agent-pm to split this project into independent coding-agent assignments. Give each task a disjoint write scope, expected output, acceptance criteria, validation commands, and a human review checkpoint.
Best Practices
Name the shipped outcome, owned files, excluded files, and validation commands before implementation starts.
Require the final response to report changed files, checks run, results, and remaining risks.
Review the diff against acceptance criteria before asking for new edits or accepting the work.
Avoid
Giving a broad feature idea without ownership boundaries or acceptance criteria.
Accepting agent work that claims validation without showing the command and result.
Letting a coding agent keep expanding scope after it drifts from the original request.
Frequently Asked Questions
Which coding agents does this skill support?
It is written for Claude Code, Codex, OpenClaw, and similar coding-agent workflows where a human owns scope and review.
Does this skill write code for me?
No. It helps you plan, assign, review, and verify coding-agent work with better prompts and templates.
Can it help when an agent changes too much?
Yes. It includes recovery guidance that asks the agent to stop, map changes to acceptance criteria, and identify out-of-scope edits.
What templates are included?
It includes a PM agent brief, task plan, prompt snippets, review checklist, and first-week workflow tracker.
Is this useful for non-technical PMs?
Yes. The templates use plain task, scope, and review language, but a technical reviewer should inspect code changes.
Does it replace testing or code review?
No. It helps define required checks and review questions, but humans and project tests still validate the result.