菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ForceInjection/domain-driven-design-skills --skill use-pmc命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Conduct deep academic research for philosophy, neuroscience, cognitive science, and theoretical computer science (computability, complexity, AI theory, logic). Use when user asks to: research academic topics, find scholarly papers, conduct literature reviews, analyze citations, synthesize research findings, explore philosophical arguments, investigate consciousness/cognition, study computability/decidability/Turing machines, or analyze academic debates. Triggers on: 'research papers', 'literature review', 'academic sources', 'scholarly articles', 'philosophy of mind', 'computability theory', 'neuroscience studies', 'find papers on', 'what does the research say'.
Create clear action plans with steps, success criteria, and risk awareness. Use before implementing features, making changes, starting projects, or anytime you need a roadmap to success. Triggers on "plan this", "how should we approach", "what's the strategy", "steps to complete", or when facing complex multi-step work.
Add keyboard navigation to a feature using CommandRegistryService. Use when implementing keyboard shortcuts, vim-style navigation, or hotkeys for a page or component.
基于 SOC 职业分类
正在显示 SKILL.md
| 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. |
PMC is a workflow orchestration CLI for Claude Code. It manages project planning, ticket implementation, and documentation sync.
| 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 |
PMC must be available from the repository root:
cd <repo-root> # Parent directory of .claude/
uv sync
pmc list
# 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.
| 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=... |
# 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
# 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
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
pmc status # Current execution status
pmc status --ticket T00001 # Status for specific ticket
pmc tasks # List running agents
Before running a new or modified workflow:
pmc validate <workflow-name>
pmc validate <workflow-name> --check-deps # Check sub-workflow dependencies
| 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 |
Use PMC workflows when:
pm.init-project sets up docs structure from PRDpm.analyze-gaps finds discrepanciespm.sync-prd and pm.sync-planning fix documentationpmc new scaffolds with templatespmc list # Check available workflows
pmc validate path/to/workflow.json # Verify specific file
If running from a different directory, specify working_dir:
pmc run pm.init-project -i working_dir=/path/to/project
Check sub-workflow dependencies exist:
pmc validate my.workflow --check-deps
pmc run my.workflow -v --log-file ./pmc.log
working_dir to current directorydocs/1-prd/ has requirements before pm.init-projectpmc validate for custom workflows99-discrepancies.md after pm.analyze-gaps