Provides project management tool abstraction layer. Auto-loads when working with work items, epics, features, tasks, sprints, or backlogs. Detects PM tool (Linear, Jira, GitHub Projects, markdown) from project configuration and loads appropriate adapter for seamless operations across different PM systems.
Resources
2Install
npx skillscat add memyselfandm/cconami/pm-context Install via the SkillsCat registry.
Project Management Context
Provides a unified interface for project management operations across different tools. This skill auto-loads when Claude detects work related to project management.
PM Tool Detection
Detect the project's PM tool in this order:
CLAUDE.md configuration:
## Project Management pm_tool: linear pm_team: ChronicleSettings file (
.claude/settings.json):{ "pm": { "tool": "jira", "project": "PROJ", "api_url": "https://company.atlassian.net" } }File detection:
.linear/directory → Linear.jira.d/orjira.config→ Jira.github/with projects → GitHub ProjectsBACKLOG.mdorbacklog.md→ Markdown
Default: Markdown (no external tool required)
Loading the Appropriate Adapter
Once detected, load the corresponding adapter:
| Tool | Adapter File | CLI |
|---|---|---|
| Linear | adapters/linear.md | linctl |
| Jira | adapters/jira.md | jira |
| GitHub | adapters/github.md | gh |
| Markdown | adapters/markdown.md | filesystem |
Operations Interface
All adapters implement the operations defined in interface.md. Use these generic operations in skills rather than tool-specific commands.
Terminology
Use generic terminology in all skill interactions:
| Generic Term | Description |
|---|---|
| work item | Any trackable unit (issue, ticket, task) |
| epic | Large body of work containing features |
| feature | Discrete capability within an epic |
| task | Atomic implementation unit |
| sprint | Time-boxed execution container |
| backlog | Prioritized list of work items |
| project | Container for related work |
Usage in Skills
Skills should:
- Call pm-context to detect the active PM tool
- Load the appropriate adapter
- Use interface operations, not direct CLI calls
- Use generic terminology in outputs
Example pattern:
## Step 1: Get Work Item Context
Use pm-context to fetch the work item:
- Detect PM tool from project config
- Load [interface.md](../pm-context/interface.md) for operation spec
- Call `get_item(item_id)` via the appropriate adapter