project-management

Manages GitHub Project v2 boards, milestones, issues, and delivery phases for the ChrisShop monorepo.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/jacobmiller22/chrishop --skill project-management-jacobmiller22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-management
Source: https://github.com/jacobmiller22/chrishop/tree/main/.agents/skills/project-management
Command: npx skills add https://github.com/jacobmiller22/chrishop --skill project-management-jacobmiller22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating multi-phase software delivery across GitHub Issues, Milestones, and Project v2 boards requires constant manual status updates, dependency checks, and priority governance that slow down engineering teams and let backlog drift go unnoticed. ## Core Features & Use Cases - Issue Lifecycle Automation: Move issues through Backlog, In Progress, In Review, and Done with label updates, progress comments, and PR linking via gh CLI commands. - Dependency & Priority Governance: Enforce prerequisite verification before starting stories and require explicit priority labels on every issue before dispatch. - Adversarial Roadmap Audits: Run on-demand audits (pnpm run audit:roadmap) that detect architectural drift, orphaned issues, missing priorities, and lifecycle sync problems. - Use Case: An AI agent acting as Technical Project Manager finishes a story, creates a PR targeting staging with Fixes #42, posts a completion comment with verification links, and closes the issue only after the PR merges. ## Quick Start Ask the agent to run a roadmap audit and report the top shovel-ready stories, blockers, and milestone progress for the ChrisShop project.

Frequently Asked Questions about project-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub Project board status updates with issues and PRs?

Link every pull request to its issue using `Fixes #<IssueNumber>` in the PR body so board-sync automation moves cards through In Progress, In Review, and Done. Update labels with `gh issue edit` and post progress comments at key milestones.

How to audit a GitHub backlog for orphaned issues and missing priorities?

Run `pnpm run audit:roadmap` to inspect live GitHub API state for issues without milestones, missing priority labels, and lifecycle mismatches. Use `--strict` mode to fail CI when drift or governance violations are found.

When should a GitHub issue be closed after its pull request merges?

Close the issue only after confirming the associated PR is merged via `gh pr view <PR_NUMBER> --json state,merged`. Issues with `status:completed` whose PRs are still open must remain open until merge is verified.

How do I verify story dependencies before starting development work?

Check task.md or implementation_plan.md for prerequisite stories and confirm each dependency is marked complete or closed on GitHub. If a dependency is blocked, report the blocker before proceeding rather than starting work.

What priority labels should GitHub issues use for sprint planning?

Use four explicit tiers: priority:critical for showstoppers, priority:high for critical-path blockers, priority:medium for standard phase tasks, and priority:low for deferred enhancements. Every issue must carry one before dispatch to agents.