An open-source AI suite for product teams.
A toolkit I built to run product delivery operations: Claude skills, Jira and Confluence templates, and Zapier workflows that handle cadence, readiness and reporting so a product team gets consistent quality without adding headcount. It is open source and documented below.
Senior leadership carrying the work.
Most product companies of a certain stage have an invisible drag on their senior leadership. Standups, ceremonies, sprint cadence, performance visibility, none of it owned by anyone.
This is not a people problem. It is a structural problem. The team has grown past the point where senior leaders can absorb the work as overhead.
Every hour the Head of Product spends chasing sprint status is an hour not spent on roadmap quality. Every hour the Head of Engineering spends mediating between squads is an hour not spent on architecture.
From side-of-desk to discrete function.
Product operations is not a tax on senior leadership. It is a discrete function with its own operating standards. The function heads keep the judgment. The system handles the cadence, the visibility, and the standards, giving the whole team something consistent to work against.
The Toolkit
The system is built from four pillars: Discovery, Delivery, Cadence, Learning. The toolkit sits inside it. Ten tools across four pillars, each documented in full.
A quality gate for PRDs: PASS/FAIL against six criteria with a concrete fix for each failure.
View on GitHub →System Design
Every tool starts from a human intent signal. Claude handles structure. Zapier handles routing. Systems of record hold the work. The human reviews before anything writes back.
| Layer | Tool |
|---|---|
| Intake | Paste, upload, or Slack command |
| Intelligence | Claude Project skills |
| Approval | Human review step (mandatory before any write) |
| Orchestration | Zapier |
| Execution | Jira |
| Knowledge | Confluence or Notion |
| Confirmation | Slack |
Enforced standards across the product team.
Skills are prompt files that tell Claude exactly how to behave for a specific product task. Every member of the team uses the same skills. Every skill enforces the same quality standard. When a skill is updated, every team member benefits immediately.
| Skill | What it enforces |
|---|---|
feature-pre-mortem | Gaps, risks, and assumptions surfaced from early product material before commitment |
prd-critique-writer | Six quality criteria, problem definition, target users, scope, metrics, risks, open questions. PASS or FAIL. |
prd-to-tickets | Ticket structure with acceptance criteria, T-shirt sizing, mandatory out-of-scope notes |
weekly-product-update | Stakeholder-ready update format with shipped, in-flight, at-risk, and next |
sprint-retro-synthesiser | Theme clustering with named owners on every action item |
feature-request-intake | Triage criteria, fit, evidence, sizing, before anything enters the backlog |
briefing-interview | Structured brief format covering problem, audience, constraints, success criteria |
branded-html-email | Brand voice rules, component-level Figma reference, accessibility checks |
marketing-copywriter | Team voice rules, claim verification, fact density |
document-review | Gap detection, weak claim flagging, missing evidence checks |
decision-log-auto-capture | Decision format, what, who, when, context, expected impact |
Get started in 60 seconds.
Open Claude and paste:
Fast path (skills only): Create a new Claude Project. Copy CLAUDE.md from github.com/owen-manby/product-ai-tools into Project Instructions. Upload each file from skills/ as Project Knowledge. Done. Templates path: Copy files from jira-templates/ and confluence-templates/ into Jira and Confluence. No setup required. Full automation (Zapier): Import the Zaps from zapier-workflows/ into your Zapier account. Follow the README for credentials. Open the SETUP.md file on GitHub to get started.github.com/owen-manby/product-ai-tools →
Get this running in your org.
Three levels of setup. Start with Level 1. Add more only when you need it.
Claude Project Setup
- Create a new Claude Project named "Product Work"
- Open CLAUDE.md from the repo and paste the full contents into Project Instructions
- Upload each file from the skills/ directory as a separate Project Knowledge file
- Test: paste a real PRD and run /critique, confirm the output follows the six-criteria format
Jira
- Install jira-templates/ticket-template.md as the default description on your Story issue type
- Install jira-templates/bug-template.md as the default description on your Bug issue type
- Install jira-templates/epic-template.md as the default description on your Epic issue type
Confluence
- Create a new Space Template from confluence-templates/prd-template.md
- Create a new Space Template from confluence-templates/decision-log-template.md
- Create a new Space Template from confluence-templates/retro-template.md
Infrastructure
- Zapier account (Pro tier or higher for multi-step zaps)
- Anthropic API key added to Zapier credentials
- Jira API token configured in Zapier
- Confluence API token configured in Zapier (optional, only for weekly update automation)
- Demo Jira project created for testing (free Atlassian Cloud tier is fine)
Slack Channels (Optional)
- #product-tickets, receives Jira ticket confirmations
- #product-updates, receives weekly stakeholder updates
- #product-decisions, receives decision log entries
Workflow Setup
- Import zapier-workflows/prd-to-tickets.json into Zapier
- Import zapier-workflows/weekly-product-update.json into Zapier
- Set your Jira Project Key in the Create Issue node
- Activate the workflows
Validation
- Test: paste a PRD into the Claude Project, run /tickets, copy the JSON
- Trigger the prd-to-tickets Zap with that JSON as the input
- Confirm Jira issues are created with the full ticket template populated
- Confirm Slack receives the confirmation thread