use-pmc
Use PMC (Project Manager Claude) CLI for workflow orchestration. Use this skill when running workflows, creating new projects, syncing docs with implementation, or managing project planning.
When & Why to Use This Skill
The use-pmc skill integrates the Project Manager Claude (PMC) CLI to provide comprehensive workflow orchestration and project lifecycle management. It enables Claude to bridge the gap between high-level planning and technical implementation by automating project initialization, synchronizing PRDs with codebases, and managing ticket-based development. This skill is optimized for developers and project managers looking to maintain documentation consistency and streamline AI-driven development workflows.
Use Cases
- Project Initialization: Automatically scaffold new projects and generate structured planning documents from a Product Requirement Document (PRD) using the pm.init-project workflow.
- Documentation Drift Analysis: Identify discrepancies between the actual codebase and the PRD using pm.analyze-gaps to ensure documentation stays up-to-date with implementation.
- Automated Planning & Ticketing: Generate implementation tickets for unbuilt features identified in the PRD through the pm.sync-planning workflow to maintain a clear development roadmap.
- Custom Workflow Orchestration: Create and execute custom CLI-based workflows for repetitive tasks like tech stack scaffolding, status reporting, and multi-agent task coordination.
| name | use-pmc |
|---|---|
| description | Use PMC (Project Manager Claude) CLI for workflow orchestration. Use this skill when running workflows, creating new projects, syncing docs with implementation, or managing project planning. |
Use PMC
PMC is a workflow orchestration CLI for Claude Code. It manages project planning, ticket implementation, and documentation sync.
Reference Documentation
| Reference | When to Read |
|---|---|
references/how-to-use-pmc.md |
Running workflows, CLI commands, available workflows |
references/how-to-create-workflow.md |
Creating custom workflow definitions |
Prerequisites
PMC must be available from the repository root:
cd <repo-root> # Parent directory of .claude/
uv sync
Quick Reference
List Available Workflows
pmc list
Run a Workflow
# By registry name (working_dir defaults to current directory)
pmc run <workflow-name>
# Explicit working_dir (if running from different location)
pmc run <workflow-name> -i working_dir=/path/to/project
# With verbose output
pmc run <workflow-name> -v
# Dry run (preview without executing)
pmc run <workflow-name> --dry-run
Note: working_dir defaults to . (current directory) when not specified.
Common Workflows
| Workflow | Purpose | Command |
|---|---|---|
pm.init-project |
Initialize planning from PRD | pmc run pm.init-project |
pm.analyze-gaps |
Compare codebase vs PRD | pmc run pm.analyze-gaps |
pm.sync-prd |
Update PRD from implementation | pmc run pm.sync-prd |
pm.sync-planning |
Create tickets for unbuilt features | pmc run pm.sync-planning |
scaffold.workflow |
Bootstrap new projects | pmc run scaffold.workflow -i project_name=... -i target_dir=... |
Typical Workflows
Initialize New Project
# 1. Create project structure
pmc new my-project --stack python-uv
# 2. Add PRD documents to docs/1-prd/
# 3. Initialize planning from PRD
pmc run pm.init-project -i working_dir=./my-project
Sync Documentation with Implementation
# 1. Analyze gaps between code and PRD
pmc run pm.analyze-gaps
# 2. Review docs/1-prd/99-discrepancies.md
# 3. Update PRD for implemented features (optional)
pmc run pm.sync-prd
# 4. Create tickets for unbuilt features (optional)
pmc run pm.sync-planning
Project Management
pmc projects list # List registered projects
pmc projects info my-project # Show project details
pmc projects switch my-project # Print cd command
pmc projects stacks # List available tech stacks
Check Status
pmc status # Current execution status
pmc status --ticket T00001 # Status for specific ticket
pmc tasks # List running agents
Workflow Validation
Before running a new or modified workflow:
pmc validate <workflow-name>
pmc validate <workflow-name> --check-deps # Check sub-workflow dependencies
CLI Options
| Option | Description |
|---|---|
-i, --input KEY=VALUE |
Pass input variables |
--dry-run |
Preview without executing |
-v, --verbose |
Show detailed output |
-q, --quiet |
Minimal output |
--log-file PATH |
Write logs to file |
--workflows-dir PATH |
Override workflows directory |
When to Use PMC
Use PMC workflows when:
- Initializing a project -
pm.init-projectsets up docs structure from PRD - Documentation drift -
pm.analyze-gapsfinds discrepancies - Updating docs -
pm.sync-prdandpm.sync-planningfix documentation - Creating new projects -
pmc newscaffolds with templates - Orchestrating ticket work - Supervisor/ticket workflows automate implementation
Troubleshooting
Workflow Not Found
pmc list # Check available workflows
pmc validate path/to/workflow.json # Verify specific file
Missing Inputs
If running from a different directory, specify working_dir:
pmc run pm.init-project -i working_dir=/path/to/project
Dependency Errors
Check sub-workflow dependencies exist:
pmc validate my.workflow --check-deps
View Detailed Logs
pmc run my.workflow -v --log-file ./pmc.log
Critical Rules
- Run from repo root - PMC defaults
working_dirto current directory - Check PRD first - Ensure
docs/1-prd/has requirements beforepm.init-project - Validate before running - Use
pmc validatefor custom workflows - Review discrepancies - Check
99-discrepancies.mdafterpm.analyze-gaps - Specify working_dir explicitly - Only needed when running from a different location