pm-context

Auto-detect the active PM tool and load the correct adapter.

8|1|Updated Aug 12, 2025
One-click install
npx skills add https://github.com/memyselfandm/cconami --skill pm-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-context
Source: https://github.com/memyselfandm/cconami/tree/main/apps/dot-claude/skills/pm-context
Command: npx skills add https://github.com/memyselfandm/cconami --skill pm-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unify project management work across tools by auto-detecting and loading the correct PM adapter, enabling consistent operations regardless of the PM system in use.

Core Features & Use Cases

  • Auto-detection of PM tool from project configuration (CLAUDE.md or .claude/settings.json) and automatic adapter loading.
  • Tool-agnostic operations interface that provides a single, generic set of PM actions (work items, epics, features, tasks, sprints, backlog) across Linear, Jira, GitHub Projects, and markdown backlogs.
  • Cross-tool portability supports multi-tool environments where teams switch between tools without changing skill logic.

Quick Start

Configure your project with a pm_tool and optional identifiers, then instruct the assistant to manage items and the skill will auto-load the correct adapter for immediate cross-tool work.

Frequently Asked Questions about pm-context

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

FAQPage Schema
How do I manage work items across multiple project management tools like Linear and Jira?

Unify project management across tools by configuring a pm_tool setting in CLAUDE.md or settings.json. The auto-detection mechanism loads the correct adapter, providing a tool-agnostic interface for managing work items across Linear and Jira.

What is the best way to unify markdown backlogs with GitHub Projects sprints?

Unify markdown backlogs with GitHub Projects by specifying the tools in your project configuration. The adapter applies a generic interface for PM operations, allowing consistent management of sprints and backlogs across both formats.

Does this adapter approach require manual switching for cross-tool PM operations?

No, cross-tool PM operations do not require manual switching. The adapter auto-detects the active PM tool from project configuration and exposes a generic interface, allowing teams to switch between tools without changing skill logic.

How do I configure my project to auto-detect the active PM tool?

Configure auto-detection by adding a pm_tool specification and optional identifiers to CLAUDE.md or .claude/settings.json. This setup enables automatic adapter loading for immediate tool-agnostic operations on epics, features, and tasks.

Can I use a single interface for PM operations across epics, features, and tasks?

Yes, you can use a single interface for PM operations across epics, features, and tasks. The tool-agnostic operations interface provides a generic set of PM actions that apply uniformly across Linear, Jira, GitHub Projects, and markdown backlogs.