project-manager
Installation
SKILL.md
Project Manager
Use this skill for repo-local project management.
Automation Preference
- Prefer Node scripts for repo-local automation.
- If a script needs dependencies, add them as repo
devDependenciesand invoke them throughpnpmornode. - Avoid Python for repo-local skill automation unless a Python-native library is clearly worth the extra runtime dependency.
Canonical Locations
- Treat GitHub Issues and PRs as the public source of truth.
- Treat
.local/work-items.yamlas a derived repo-local cross-reference map that can be regenerated from the project board. - Put temporary issue writeups only in
.local/issue-drafts/. - Do not create parallel scratch directories or alternate tracker files for the same purpose.
- Read repo-specific values from
.agents/project-manager.config.jsonbefore taking action.
Expected config shape:
Related skills
More from pwrdrvr/ghcrawl
ghcrawl
Use the local ghcrawl CLI to inspect duplicate clusters and issue/PR summaries from the existing ghcrawl dataset, and refresh one repo only when the user explicitly asks. Use when a user wants to triage related issues or PRs, inspect semantic clusters, or run ghcrawl's staged refresh pipeline.
11release
Plan and publish a GitHub Release in a tag-driven repository. Use when a user asks to cut, prepare, or publish a software release, propose the next vX.Y.Z tag, draft better release notes from PRs and direct commits since the last release, update CHANGELOG.md, create the tag pinned to an exact commit, and watch the publish workflow.
1