- Home
- Skills
- Workflow Automation
- PM Workflow for Claude Code
PM Workflow for Claude Code
A systematic five-step PM lifecycle for Claude Code: audit, plan, write stories, build and release, with you approving every step that matters.
$18
Works with the AI Agents you already use
PM Workflow for Claude Code
Example session with this skill installed
Use my Agensi skill "PM Workflow for Claude Code" to produce a plan (mini PRD) for adding online pre-orders and card payments to our bakery's existing website. The code audit is in docs/audit/crumb-web-audit.md, and Ana's notes from two weeks of the paper order book are in docs/order-book-notes.md.
- Read your context and instructions
- Compiled the pm workflow
Example output from a fictional project: Crumb, a neighbourhood bakery.
The plan and feature matrix for Crumb pre-orders are ready for your approval.
Plan summary
- Problem: regulars phone to reserve bread, orders are kept on paper, and some get lost.
- Users: local customers, and two staff at the counter.
Sources: the crumb-web audit (the site has a menu but no ordering, payment or admin) and Ana's order-book notes (about 120 reservations a week, most for Saturday; not a full count, because some counter phone orders weren't written down).
- Goal: customers pre-order and pay online for a pickup time they choose.
- Success: 150 paid pre-orders a week by 2026-12-15, and no phone reservations after 7am by 2026-11-15.
- Not in scope: delivery, wholesale orders, a mobile app.
- Risk level: Live, because customers pay by card and share their name and email.
- Open question (blocking): which payment provider will you use?
Plan draft: docs/project-plan.md
Feature matrix: Crumb pre-orders — feature matrix (Google Sheet)
Feature matrix
| ID | Feature | Source | Priority | Phase | Depends on |
|---|---|---|---|---|---|
| 1.1 | Menu from the database | audit | Must | Phase 1 | — |
| 1.2 | Daily availability | the user | Must | Phase 1 | 1.1 |
| 2.1 | Basket | the user | Must | Phase 1 | 1.1 |
| 2.2 | Card payment | the user | Must | Phase 1 | 2.1 |
| 2.3 | Pickup time slots | the user | Must | Phase 1 | 2.1 |
| 2.4 | Confirmation email | the user | Should | Phase 1 | 2.2 |
| 3.1 | Today's orders | the user | Must | Phase 1 | 2.2, 2.3 |
| 3.2 | Mark as collected | stakeholder | Should | Phase 1 | 3.1 |
| 3.3 | Sold-out switch | stakeholder | Could | Phase 2 | 1.2 |
| 4.1 | Customer accounts | the user | Should | Phase 2 | 2.2 |
| 4.2 | Repeat last order | competitor | Could | Phase 2 | 4.1 |
| 4.3 | Loyalty stamps | stakeholder | Won't | — | — |
12 features: 6 Must, 3 Should, 2 Could, 1 Won't. 8 in Phase 1, 3 in Phase 2.
Next steps
- Read the plan, and tell me about any changes to priorities or phases. Those decisions are yours.
- Approve it, and I'll commit the plan and open a pull request on one yes from you.
- Merge the pull request.
- Add a
DESIGN.md, because UI stories wait for one. I can draft it from your brand or existing pages. - Ask for the story for feature 1.1.
Connects securely to your tools. The creator never sees your data.
About this skill
You don't need to write code to run a product build, but you do need to stay in control of it. This skill pack lets a Product Manager or founder run Claude Code like a small engineering team, through five steps: audit, plan, story, build and release. You make the product decisions; Claude decides how to build, and stops to ask whenever a decision is yours.
What it does
- Code Audit maps an existing repo in plain English: what exists, what is missing, and any security concerns. It changes nothing except saving its report.
- Project Plan sets your repo up, writes a short PRD, and creates a feature matrix in Google Sheets or Linear.
- Story turns a feature into a testable story with clear acceptance criteria.
- Build Feature plans the work for your approval, writes the code and tests, has it independently reviewed by AI, and prepares a pull request with a checklist for you to test.
- Release runs a readiness check, writes the release record and any notes you choose, then guides the deployment or hands it to its owner.
How it works
- Audit each existing repo. Skip this for a brand-new product.
- Plan the project, then merge its pull request.
- Write the story for each feature, in build order, and approve it.
- Build the feature. You approve the plan and the pull request; everything in between is Claude's job.
- Merge it yourself or through a developer. If comments come back or a test fails, ask Claude to build it again and it reads the feedback itself.
- Release the phase once its features have merged.
Built to the risk you're taking
You set each project's risk level: Prototype, Pilot or Live. It decides how much security review, testing and rollback planning each step asks for, so a prototype moves fast and a live product gets the care it needs.
Why this beats prompting it yourself
Asked directly, Claude builds however it sees fit and you see the result. With these skills, no feature is built without an approved story, and each one arrives as a reviewed pull request. Decisions are recorded with who made them and why, and project records carry the work from one session to the next.
Use cases
- Building a new product without writing code
- Understanding an unfamiliar codebase before planning changes
- Working alongside developers, with every change arriving as a reviewed pull request
- Running a product across several repos, such as a frontend and a backend
- Adding AI features with test examples you approve
Requirements
- Claude Code, ideally in Auto mode
- A GitHub repo and the GitHub CLI (
gh), logged in - Google Drive and Google Sheets connectors, or the Linear connector
- A basic grasp of branches, commits, pushes and pull requests
Known limitations
- Built and tested on macOS. Windows needs Git for Windows.
- Built for Claude Code only.
- UI stories need a
DESIGN.mdin your repo. Claude Code can draft one from your brand or existing pages.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Workflow Automation.
Requires GitHub CLI. Matrix tracking requires Google Sheets or Linear access. UI stories can't be approved until your repo has a DESIGN.md.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 8 days ago
- Accounts
GitHub
Anthropic
Google DriveandGoogle Sheets
orLinear
- Software
GitHub CLI
Git
Permissions
Allowed Hosts
File Scopes
Works inside your repo, and in the parent folder for multi-repo projects. Never reads .env or other secret files. Tested on macOS. Requieres Google Drive + Google Sheets OR Linear for feature matrix and stories. Works best in Claude Code Auto mode, or Accept edits if Auto isn't available. Plan mode won't work, because it hinders Claude from editing files.