pm

pure-magic

Spec-driven project management for Claude Code. Write specs with AI, generate GitHub Issues, track delivery, all from your PM workspace.

How it works

1. Write a spec with AI as partner (/pm:spec)
2. Break it into tasks with quality gates enforced (/pm:parse)
3. Create standalone tickets for bugs and small requests (/pm:ticket)
4. Review locally before anything goes to GitHub
5. Sync to GitHub Issues with one command (/pm:sync)
6. Track delivery including PR status (/pm:status)

Then the dev team picks up the GitHub Issue, plans with Claude Code (optional), implements, opens a PR. Everything connects through GitHub Issues, no shared files needed.

Install

https://github.com/user-attachments/assets/5a069547-2561-4d50-ab16-734d1eb45c04

1. Open Claude Desktop
2. Click + in the prompt area
3. Go to Plugins
4. Click Add plugin
5. Go to the Personal tab
6. Click +
7. Select Add marketplace from GitHub
8. Paste this URL: https://github.com/barbicorro/pure-magic
9. You will see the pm plugin appear - click Install
10. Restart Claude. The plugin activates automatically on your next session.

That is it!

Setup per project

Each project needs a pm-config.md file. This tells pure-magic which GitHub repo to use, who is on the team, and a few other settings.

Option A: Create it manually

Create a new file called pm-config.md inside your project folder and paste this in:

---
project: your-project-name
github_repo: owner/repo-name
team:
  pm: Your Name
  devs: []
---

Replace your-project-name, owner/repo-name, and Your Name with your own details.

Option B: Copy the template (requires terminal)

cp ~/.claude/pm/templates/pm-config.md <your-project>/pm-config.md

Then open the file and fill in your details.

Skills

Skill	What it does
/pm:spec <project> <feature>	Interview + write a spec
/pm:parse <project> <feature>	Break a spec into tasks
/pm:ticket <project> <title>	Create a standalone ticket
/pm:interview <project> <segment>	Create a customer interview guide
/pm:research <project> <topic>	Strategic product research report
/pm:sync <project> <target>	Push to GitHub Issues
/pm:status [project]	Dashboard with PR delivery status
/pm:validate <file>	Validate a file against quality standards

File structure

pure-magic/                     # plugin source repo
  .claude-plugin/
    plugin.json                 # plugin manifest (name: pm)
  skills/
    spec/SKILL.md
    parse/SKILL.md
    ticket/SKILL.md
    interview/SKILL.md
    outcome-brief/SKILL.md
    research/SKILL.md
    sync/SKILL.md
    status/SKILL.md
    validate/SKILL.md
  agents/
    spec-reviewer.md
    product-researcher.md
  rules/                        # installed once to ~/.claude/pm/rules/ on first use
  templates/                    # installed once to ~/.claude/pm/templates/ on first use
  hooks/
    hooks.json                  # SessionStart hook
  scripts/
    ensure-workspace.sh         # installs rules + templates to ~/.claude/pm/ (once per version)

your-workspace/
  .claude/
    overrides/
      rules/                    # project-specific rule overrides (you create these)
      templates/                # project-specific template overrides (you create these)
  project-name/
    CLAUDE.md                   # your product context (you write this)
    pm-config.md                # project config (github repo, team, labels)
    specs/                      # spec documents
    tasks/                      # task breakdowns
    tickets/                    # standalone tickets
    outcome-briefs/             # outcome brief analyses
    research/                   # strategic research reports

Customizing for your team

• pm-config.md: set your GitHub repo, team names, label preferences, branch prefix
• CLAUDE.md: your product context flows in automatically through Claude Code's context hierarchy

No code changes needed. Everything is markdown.

Overriding rules and templates per project

To customize rules or templates for one project without affecting others, create an overrides file:

# Override a rule for this project only
cp ~/.claude/pm/rules/task-quality.md .claude/overrides/rules/task-quality.md

# Override a template for this project only
cp ~/.claude/pm/templates/task.md .claude/overrides/templates/task.md

Skills check .claude/overrides/ first. If an override file exists, it is used instead of the global default. Delete the override file to go back to the global default.

The overrides directories are not created automatically. Create them when you need them.

Migrating from 0.8.x

The SessionStart hook no longer writes to your workspace .claude/ directory. If you ran a previous version, clean up the leftover copies: