Create tickets — Draft well-structured tickets with acceptance criteria from conversations
Analyze tickets — Review for completeness, clarity, gaps, and dependencies
Propose amendments — Suggest improvements based on code context or new information
Identify gaps — Find missing coverage when breaking down epics
Generate questions — Create structured refinement session discussion points
Plan work — Suggest parallelization strategies and dependency analysis

Supported PM Systems

Linear — Full support via Linear MCP server
GitHub Issues — Full support via GitHub CLI (gh)
Local Markdown — File-based tickets in docs/tickets/
Future systems (Jira, Azure Boards, etc.) via extensible connector framework

Setup

1. Install the Plugin

This skill is part of the pm-assistant plugin available in the Claude Code Plugin Marketplace.

To install, use the marketplace installation command or manually install the plugin from the marketplace.

2. Configure Your PM System

For Linear:

Follow the Linear MCP documentation to set up the MCP server
Authenticate with Linear
Add CLAUDE.md configuration (see step 3)

For GitHub Issues:

Install GitHub CLI: https://cli.github.com/ or brew install gh
Authenticate: gh auth login
Verify git remote: git remote get-url origin (must be a GitHub repository)
Add CLAUDE.md configuration (see step 3)

For Local Markdown:

Create tickets directory: mkdir -p docs/tickets
Initialize counter: echo "1" > docs/tickets/.ticket_counter
Add CLAUDE.md configuration (see step 3)

3. Add Project Context (Required)

Create CLAUDE.md in your project root to declare which PM system to use:

Example for Linear:

# CLAUDE.md

## Project Management
- **System**: Linear
- **Team Prefix**: PROD
- **Project**: Backend Services

Example for GitHub Issues:

# CLAUDE.md

## Project Management
- **System**: GitHub-Issues

Note: Repository is auto-detected from git remote origin.

Example for Local Markdown:

# CLAUDE.md

## Project Management
- **System**: Local-Markdown
- **Directory**: docs/tickets

The skill will use these settings for all operations in the project.

How to Use

Simply describe what you need with tickets. The Skill activates automatically and works with your configured PM system:

Review the tickets for this sprint and identify any gaps

Create a ticket for implementing dark mode with acceptance criteria

What are the dependencies between PROD-100 and PROD-110?

Generate questions for our refinement session on the payment feature

Suggest improvements to this epic based on the code review

The Skill will:

Fetch relevant tickets from your PM system (Linear, GitHub Issues, or Local Markdown)
Analyze them using proven patterns
Present findings or proposals for review
Wait for your explicit confirmation before making changes
Apply updates and report results

Documentation

SKILL.md — Complete workflow guide and patterns
assets/ticket_template.md — Ready-to-use templates
references/ticket_structure_guide.md — Quality standards (system-agnostic)
references/analysis_patterns.md — Six analysis workflows with examples
references/refinement_session_guide.md — Refinement best practices
connectors/linear.md — Linear MCP API reference and operations
connectors/local-markdown.md — Local Markdown connector documentation
- connectors/local-markdown/setup.md — Setup instructions for local markdown
connectors/README.md — Connector interface and extensibility guide

Key Principles

✅ Extensible architecture — PM system-specific code isolated in connectors; supports Linear, GitHub Issues, and Local Markdown ✅ Always proposes before acting — Shows changes for your review ✅ Requires explicit confirmation — Never assumes approval ✅ Specific and quoted — References exact text when identifying issues ✅ Explains rationale — Shows why changes matter ✅ Reusable patterns — Analysis and refinement workflows system-agnostic

Troubleshooting

Problem	Solution
Skill not activating	Explicitly ask: "Use the product-manager skill to review these tickets..."
Team/project not found (Linear)	Add `CLAUDE.md` file with Linear team and project (see Setup step 3)
Can't find tickets (Linear)	Verify Linear is configured correctly in CLAUDE.md and MCP server is authenticated
Repository not detected (GitHub)	Verify git remote origin exists and is a GitHub URL: `git remote get-url origin`
`gh` command not found (GitHub)	Install GitHub CLI: https://cli.github.com/ or `brew install gh`
Not authenticated (GitHub)	Run `gh auth login` to authenticate with GitHub
Tickets directory not found (Local Markdown)	Create directory specified in CLAUDE.md: `mkdir -p docs/tickets`
System not declared	Add `CLAUDE.md` with `System` field set to Linear, GitHub-Issues, or Local-Markdown

See SKILL.md for comprehensive documentation and workflow examples.