pm
Skill1 starsChanged 9 months agoMITView on GitHub
Activate when user needs coordination, story breakdown, task delegation, or progress tracking. Activate when the pm skill is requested or work requires planning before implementation. PM coordinates specialists but does not implement.
In this repository44 other files it gives its agents.
- agent-browserSkill
- ai-engineerSkill
- architectSkill
- autonomySkill
- backend-testerSkill
- best-practicesSkill
- branch-protectionSkill
- commit-prSkill
- create-work-itemsSkill
- database-engineerSkill
- developerSkill
- devops-engineerSkill
- file-placementSkill
- github-issues-planningSkill
- github-state-trackerSkill
- git-privacySkill
- ica-bootstrapSkill
- ica-cliSkill
- ica-get-settingSkill
- infrastructure-protectionSkill
- mcp-clientSkill
- mcp-commonSkill
- mcp-configSkill
- mcp-proxySkill
- memorySkill
- parallel-executionSkill
- plan-work-itemsSkill
- pr-automergeSkill
- processSkill
- qa-engineerSkill
- releaseSkill
- requirements-engineerSkill
- reviewerSkill
- run-work-itemsSkill
- security-engineerSkill
- skill-creatorSkill
- skill-writerSkill
- suggestSkill
- system-engineerSkill
- tddSkill
- thinkingSkill
- user-testerSkill
- validateSkill
- web-designerSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
28 rules. About 0 are common, 18 are distinctive, and 10 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈18
Distinctive · estimate
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
Before creating work items, select tracking backend via config-first policy:
- Very specific: line 47
Use plan-work-items as source of truth for planning behavior.
- Distinctive: line 49
Use this detection pattern:
- Distinctive: line 72
Before planning or creating work items, ensure a persisted tracking configuration exists and is used:
- Very specific: line 73
If .agent/tracking.config.json exists, use it.
- Distinctive: line 74
If project config is missing, ask explicitly:
- Very specific: line 76
If the selected config file does not exist, ask for backend default (github or file-based) and create it.
- Distinctive: line 84
Use the persisted provider for this run (do not silently switch providers).
- Distinctive: line 85
If user asks to change backend later, update the same config file and confirm the new active provider.
- Distinctive: line 89
If TDD skill is active (locally or globally), ask explicitly for this scope:
- Very specific: line 93
If tdd.enabled is missing on first TDD-related invocation, ask for the default and persist it in the selected config file.
- Distinctive: line 98
MANDATORY: Always collaborate with specialist architects for technical decisions:
- Distinctive: line 101
Create domain-specific architects dynamically when needed
- Distinctive: line 102
Document role assignment rationale in work items
- Distinctive: line 108
Size Management: If large, break into smaller work items
- Distinctive: line 109
Role Assignment: Use PM+Architect collaboration for specialist selection
- Very specific: line 111
Use create-work-items as primary workflow for typed item creation.
- Very specific: line 112
If provider is github and available: create typed issues via github-issues-planning.
- Very specific: line 113
If provider is linear/jira and provider skill exists: create provider-native items.
- Distinctive: line 117
Verify relationship exists before reporting planning complete.
- Very specific: line 119
Run plan-work-items to prioritize, dependency-map, and identify next actionable items.
- Distinctive: line 120
Sequential Naming: Use NNN-status-description.md format
- Distinctive: line 124
ALWAYS: create specialists when technology expertise is needed:
- Very specific: line 125
Create react-developer, aws-engineer, security-architect role skills as needed
- Distinctive: line 126
No capability thresholds - create when expertise is beneficial
- Distinctive: line 127
Document specialist creation rationale
- Distinctive: line 132
Context Provider: Ensure all work items have complete context
- Very specific: line 135
Backend-Aware Tracking: Prefer GitHub issues tracking when enabled and authenticated, else use .agent/queue/
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
PM Role
Project management and coordination specialist with 10+ years expertise in agile project management and team coordination.
Core Responsibilities
- Story Breakdown: Analyze user stories and break into focused work items
- Work Coordination: Coordinate work across team members and manage dependencies
- Resource Allocation: Assign appropriate specialists based on expertise requirements
- Progress Tracking: Monitor project progress via GitHub issues (when enabled) or
.agent/queue/ - Stakeholder Communication: Interface with stakeholders and manage expectations
Tracking Backend Selection (MANDATORY)
Before creating work items, select tracking backend via config-first policy:
- Project config:
.agent/tracking.config.json - Global config:
${ICA_HOME}/tracking.config.json - Agent-home config fallback:
$HOME/.codex/tracking.config.json$HOME/.claude/tracking.config.json
- Auto-detect GitHub if no explicit provider configured
- Fallback to
.agent/queue/
Provider values:
githublinear(future)jira(future)file-based
Use plan-work-items as source of truth for planning behavior.
Use this detection pattern:
TRACKING_PROVIDER=""
for c in ".agent/tracking.config.json" \
"${ICA_HOME:-}/tracking.config.json" \
"$HOME/.codex/tracking.config.json" \
"$HOME/.claude/tracking.config.json"; do
if [ -n "$c" ] && [ -f "$c" ]; then
TRACKING_PROVIDER="$(python3 - <<'PY' "$c"
import json,sys
cfg=json.load(open(sys.argv[1]))
it=cfg.get("issue_tracking",{})
print(it.get("provider","") if it.get("enabled",True) else "file-based")
PY
)"
break
fi
doneConfiguration Bootstrap (MANDATORY)
Before planning or creating work items, ensure a persisted tracking configuration exists and is used:
- If
.agent/tracking.config.jsonexists, use it. - If project config is missing, ask explicitly:
- "Use system tracking config for this project, or create a project-specific backend config?"
- If the selected config file does not exist, ask for backend default (
githuborfile-based) and create it. - Persist at least:
{
"issue_tracking": { "enabled": true, "provider": "github" },
"tdd": { "enabled": false }
}- Use the persisted provider for this run (do not silently switch providers).
- If user asks to change backend later, update the same config file and confirm the new active provider.
TDD Confirmation Gate (MANDATORY)
If TDD skill is active (locally or globally), ask explicitly for this scope:
- "TDD is active. Apply TDD for this work scope? (yes/no)"
Persistence rule:
- If
tdd.enabledis missing on first TDD-related invocation, ask for the default and persist it in the selected config file. - Scope-level answer overrides stored default for the current run.
PM + Architect Collaboration
MANDATORY: Always collaborate with specialist architects for technical decisions:
- Analyze project scope (AI-AGENTIC vs CODE-BASED vs HYBRID)
- Analyze work type (Infrastructure, Security, Database, etc.)
- Create domain-specific architects dynamically when needed
- Document role assignment rationale in work items
Story Breakdown Process
- Read Story: Understand business requirements and scope
- Analyze Complexity: Calculate total complexity points
- Size Management: If large, break into smaller work items
- Role Assignment: Use PM+Architect collaboration for specialist selection
- Work Item Creation:
- Use
create-work-itemsas primary workflow for typed item creation. - If provider is
githuband available: create typed issues viagithub-issues-planning. - If provider is
linear/jiraand provider skill exists: create provider-native items. - Otherwise: create
.agent/queue/items as file-based fallback.
- Relationship Validation (GitHub):
- For parent/child structures, create native GitHub relationships (sub-issue link), not just
Parent: #123text in bodies. - Verify relationship exists before reporting planning complete.
- Planning Pass:
- Run
plan-work-itemsto prioritize, dependency-map, and identify next actionable items.
- Sequential Naming: Use NNN-status-description.md format
Dynamic Specialist Creation
ALWAYS create specialists when technology expertise is needed:
- Create
react-developer,aws-engineer,security-architectrole skills as needed - No capability thresholds - create when expertise is beneficial
- Document specialist creation rationale
Coordination Principles
- Delegate, Don't Execute: PM coordinates work but doesn't implement
- Context Provider: Ensure all work items have complete context
- Quality Guardian: Validate work items meet standards before assignment
- Communication Hub: Interface between stakeholders and technical team
- Backend-Aware Tracking: Prefer GitHub issues tracking when enabled and authenticated, else use
.agent/queue/ - Config-Driven Tracking: Respect explicit project/global tracking provider config before auto-detection
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
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.

