PM Workflows with Claude

From one-time setup to repeatable workflows — how to turn Claude Code into a persistent PM teammate using CLAUDE.md, parallel agents, and custom skills.

The single most powerful thing a PM can do: Create a CLAUDE.md file in each project folder. Fifteen minutes of setup saves hours of repetition.

The CLAUDE.md System

CLAUDE.md is a plain text file containing permanent instructions that Claude reads automatically every time you work in that folder. Think of it as giving Claude a project briefing once, then never having to repeat yourself.

1

Create the File

Create a file called CLAUDE.md in your project root. This is a one-time 15-minute investment.
2

Add Your Context

# Project: [Your Product Name]

## Product Context
[2-3 sentences: what it is, who it's for]

## Current Focus
[Current quarter/milestone you're working toward]

## Competitors
[Names and URLs of main competitors]

## How to Help Me
- When analyzing feedback, categorize as: Feature Request, Bug, UX Issue, Billing
- When writing PRDs, use our template in /templates/prd-template.md
- When comparing competitors, focus on: pricing, AI features, mobile experience
- Always write in [British/American] English

## What We Are NOT Building
[Hard constraints or strategic no-go areas]
3

Work Normally

Every Claude Code session in that folder automatically knows your product context, competitors, preferences, and templates. No re-explaining. No context loss.

This is the difference between Claude as a one-off tool and Claude as a persistent team member.

Workflow A: Monthly Competitive Review

  1. Create a competitive-analysis/ folder
  2. Add competitors.md listing each competitor and their URL
  3. Add analysis-template.md with sections: Pricing changes, New features, Messaging updates, Notable news
  4. Add CLAUDE.md with:
# Competitive Analysis

## Instructions
When I say "analyze competitors":
1. Visit each competitor website in competitors.md
2. Check their pricing page and changelog
3. Fill out the analysis template for each
4. Create a summary comparison table
5. Save everything in a folder named with today's date

Open terminal, navigate to the folder, type claude, and say:

analyze competitors

That’s it. Claude reads the instructions, processes each competitor, fills the template, and saves a dated report.

Time without Claude: 4 hours. Time with Claude Code: 10 minutes/month (after 15-minute one-time setup).

Workflow B: Batch User Interview Analysis

1

Prepare

Dump all interview transcripts into a /user-interviews/ folder. Any format works — TXT, MD, DOCX.
2

Process

In Claude Code, say:

Process all files in /user-interviews using parallel agents.
For each transcript:
- Extract pain points
- Identify feature requests
- Note emotional moments (frustration, delight)
- Categorize themes

Combine findings into a summary with frequency counts.
3

Review

Claude processes multiple files simultaneously, then combines findings into a single synthesis document with frequency counts and theme categorization.

Time without Claude: 3 hours for 10 interviews. Time with Claude Code: 5 minutes.

The key phrase: “using parallel agents” tells Claude Code to process multiple files simultaneously rather than one at a time. For 10 transcripts, this compresses 3 hours into 5 minutes.

Workflow C: PRD from Meeting Notes

1

Gather

Drop meeting notes, Slack export, and any relevant research docs into a folder.
2

Generate

Say:

Read all files in this folder.
Generate a PRD for the feature we discussed, using our template.
Flag any assumptions I should validate before engineering review.
3

Review

Claude reads everything, cross-references across documents, generates the PRD, and explicitly calls out where it made assumptions. It also flags when documents contradict each other.

Advanced: Parallel Agents

ScenarioWithout ParallelWith Parallel
15 interview transcripts~45 min (sequential)~5 min
8 competitor analyses~30 min~5 min
20 support ticket categories~20 min~3 min

Advanced: Custom Sub-Agents (Triple-Lens Review)

Analyze a feature spec from three perspectives simultaneously:

Analyze this feature spec from three perspectives:

1. As an Engineer Agent: flag technical complexity and implementation risk
2. As a UX Agent: identify friction points and suggest improvements
3. As a Business Agent: evaluate market fit, pricing, competitive positioning

Present each perspective separately, then synthesize a unified recommendation.

This is powerful for pre-launch reviews, go/no-go decisions, investment cases, and architecture decision records.

Advanced: Reusable Skills (Custom Slash Commands)

Claude Code supports custom slash commands — shortcuts that trigger entire workflows:

SkillWhat It Does
/prdGenerate PRD from folder contents
/competitorsRun monthly competitive analysis
/feedbackProcess and categorize user feedback
/sprint-summaryGenerate sprint review from project files
/stakeholder-updateCreate executive summary from recent changes

Skills turn multi-step workflows into one-command operations. Over time, you build a library of PM-specific automations that compound your productivity.