AI Product Development OS
akshatk7/ai-product-development-os
SO de produto que conecta conhecimento e age proativamente
Ver no GitHubSistema operacional plug-and-play para times de produto que estrutura conhecimento distribuído em Docs, Slack e Notion, conectando-o automaticamente e agindo sobre ele proativamente. Inclui 11 skills auto-aprimoráveis, 5 agents, comandos PM e camada estratégica com templates de ciclo de vida de projetos.
Instalação
npx convez-ai akshatk7/ai-product-development-os1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Centralizar contexto de projeto disperso em múltiplas plataformas
- Detectar automaticamente decisões contraditórias e status obsoletos
- Manter hipóteses estratégicas vivas com evidência e revisão contínua
- Informar novos briefs com aprendizados de projetos anteriores
Veredito

Template robusto que transforma repositório em sistema vivo de product ops. Exige investimento inicial em estruturação, mas compensa com cross-referência automática e detecção proativa de problemas — ideal para times maduro que já têm processo documentado.
README
A tradução para o português deste README ainda está na fila.
AI Product Development OS
A plug-and-play operating system for product development teams. Clone this repo, fill in your team's context, and start shipping faster.
This is a template repo — clone it, don't contribute to it.
git clone https://github.com/akshatk7/ai-product-development-os.git my-team-knowledge-base cd my-team-knowledge-base rm -rf .git && git initThen create your own repo on GitHub and push:
git remote add origin https://github.com/<your-org>/<your-team-repo>.git git add -A && git commit -m "Initialize from AI Product Development OS template" git push -u origin mainAll your changes go in your repo — not here.
Questions or feedback? Open an issue.
This Is Not a File Cabinet
Product teams usually have context scattered across Google Docs, Slack threads, Figma files, meeting notes, and people's heads. The natural instinct is to organize it — create a wiki, a shared drive, a Notion workspace. That helps, but it's still passive storage. You put things in, you take things out.
This repo is different. Yes, it structures your team's knowledge. But more importantly, it connects that knowledge, acts on it proactively, and gets smarter the more you use it. The value compounds over time.
Here's what that means concretely:
It cross-references everything automatically
When you start writing a brief for a new project, the system doesn't wait for you to remember what happened in past projects. It automatically:
- Reads
projects/INDEX.mdto find related past projects - Pulls their research findings (
truths.md), decisions (decisions.md), and context - Checks
data-science/INDEX.mdfor relevant analyses (if the data-science add-on is enabled) - Reads
product/review-taste.mdto surface what leadership has pushed on before - Reads
strategy/beliefs.mdto ground the brief in the team's current hypotheses
No one asked it to do this. It's wired to do it by default. Every new piece of work is informed by everything that came before.
It flags problems before you notice them
The system doesn't wait for you to ask "is anything stale?" It proactively catches:
- Stale project statuses — a project hasn't been updated in 14+ days but is actively discussed in Slack
- Decision contradictions — Project A decided X, Project B decided the opposite, and nobody noticed
- Unresolved TBDs — open questions older than 2 weeks that might have already been answered in a meeting or Slack thread
- Source mismatches — the repo says a project is in "Design" phase, but the tracker says "Coding"
- Unchallenged beliefs — a strategic hypothesis hasn't been re-evaluated in 30+ days
The strategy layer is the real unlock
strategy/beliefs.md isn't a document you write once. It's a living hypothesis register — what the team believes about customers, product, and market, with confidence levels, evidence chains, and challenge dates.
The key: every workflow reads and updates it. Digest a meeting? Check if anything confirms or challenges a belief. Morning sync? Same. Customer feedback scan? Cross-reference signals. Design review? Same. Over time, this creates institutional memory of what the team thinks and why — something that normally lives only in people's heads and vanishes when they leave.
It gets smarter every time you use it
Every automated skill maintains two files:
gotchas.md— failure patterns from past runs ("last time I misrouted a design note to CONTEXT.md")runs.log— execution history with outcomes
Before each run, the skill reads both files. After each run, it updates them. The morning sync that made a mistake on Day 1 learns not to repeat it on Day 2. These are self-improving loops — the system literally debugs itself.
It connects to where your team already works
The OS integrates with the tools your team uses daily — not as a one-way import, but as a two-way connection that routes information to the right place:
| Integration | What It Does | How It Connects Back |
|---|---|---|
| Slack | Morning scan, customer feedback scan, channel auto-discovery | Routes findings to project files, flags strategy implications |
| Meeting tools (Granola, Otter, etc.) | Pulls transcripts automatically | Digests route to meeting notes + project updates + decisions + strategy |
| Project trackers (Jira, Linear, GitHub Issues) | Bidirectional task sync | Mermaid diagrams in repo stay in sync with your tracker |
| Google Docs | Source of truth for briefs/PRDs | CONTEXT.md snapshots with links back to the living doc |
| Google Sheets | Roadmap tracking | Weekly status reconciles spreadsheet against repo state |
| Figma | Design files | designs.md links with flow descriptions |
| Data warehouse (Snowflake, etc.) | Customer call analysis, data queries | Speaker-aware transcript scanning with signal detection |
Knowledge compounds, not just accumulates
The difference between a wiki and this system:
- Decisions track supersession chains — old decisions are struck through with pointers to what replaced them. You can traverse the evolution.
- Beliefs build evidence chains that grow over time. Each piece of data strengthens or weakens a hypothesis.
review-taste.mdcaptures leadership feedback patterns extracted after each review. After 5 reviews, you know what leadership will push on before they say it.truths.mdaccumulates system behaviors the team discovers over time — the tribal knowledge that usually lives in one engineer's head.- Customer intelligence builds thematic signal libraries — not just "we got feedback," but patterns across channels, call transcripts, and time periods.
Every new piece of information gets checked against everything else and updates stale context. That's compounding, not accumulation.
What's Inside
Four layers work together
- Shared context —
team/,product/,roadmap/give anyone full context about the team, the product, and where things stand - Strategy —
strategy/captures what the team believes and why, competitive landscape, and open strategic questions — integrated into every workflow - Project lifecycle —
projects/uses templates to move work from brief → design → RFC → code → launch with standardized artifacts at each phase - Automation — Skills, agents, and rules turn structured context into action
11 automated skills (core)
| Skill | What It Does |
|---|---|
| Morning sync | Scans Slack channels + meetings from the previous day, proposes targeted repo updates, catches stale projects |
| Meeting digestion | Parses transcripts, extracts decisions/actions, routes to correct project files and strategy layer |
| Brief starter | Auto-gathers context from past projects, customer feedback, review patterns before you start writing |
| Ship review prep | Validates project readiness: artifact completeness, open TBDs, cross-project dependency risks |
| Open question audit | Finds unresolved TBDs across all projects, searches for evidence they've been answered elsewhere |
| Task management | Keeps Mermaid task diagrams in sync with Jira/Linear, auto-unblocks dependents when tasks complete |
| PR review | Reviews pull requests against your team's learned review patterns — safety, performance, scope, edge cases |
| Bug bash | Structured pre-launch bug bash workflow: scope, scenarios, triage, severity rubric |
| Causal analysis | Walks through causal-inference setups (DiD, synthetic control, IV) with assumption checks |
| Power analysis | Pre-experiment sample-size and MDE calculations with sensitivity tables |
| SQL validation | Validates analytics SQL against schema, common-error patterns, and result sanity checks |
Plus four opt-in skills under add-ons/skills/ — customer-feedback-scan, call-transcript-scan, figma-screenshots, investigate-alert — enable by moving them into .claude/skills/.
5 specialized agents
| Agent | What It Does |
|---|---|
| Brief reviewer | Reviews your draft against leadership review patterns from review-taste.md — predicts what they'll push on |
| Decision auditor | Cross-checks all project decisions for contradictions, stale TBDs, and cascade risks |
| Project analyst | Answers any question about a project by cross-referencing all its files + related projects |
| Repo navigator | Interactive onboarding — walks new team members through the system |
| Monthly audit | Scheduled health pass: stale statuses, INDEX drift, orphan files, decision contradictions, belief lifecycle |
4 PM workflow commands
| Command | What It Does |
|---|---|
/prep-meeting <topic> | Pulls relevant project files, decisions, and open questions into a tight pre-read |
/debrief-thread <url> | Turns a Slack thread into routed updates, decisions, and action items |
/generate-launch-email | Drafts a launch email from project artifacts (brief, decisions, designs, results) |
/review-launch-email | Critiques a launch email draft against leadership review patterns |
Opt-in add-ons
Patterns that don't apply to every team ship under add-ons/ — engineering (oncall, post-mortems), data-science (folder structure, INDEX, conventions), leadership-forum prep, repo-wide memories, and four skills (above). Each is a self-contained directory; enable by moving it to its target location. See add-ons/README.md.
3 structural guardrails
.cursorrules— AI contributor rules with a routing table for where content goes- Pre-commit hook — Blocks unauthorized files at the repo root
- CI hygiene check — Warns on structural drift in pull requests
Who Is This For
- Product managers who want a system that thinks with them, not just stores for them
- Engineers who want clear RFCs, decision logs, runbooks, and data findings per project
- Designers who want design specs living alongside product and eng context
- Data scientists who want analysis outputs that feed back into product decisions
- New team members who need to get up to speed in hours, not weeks
How to Start
- Clone this repo (see instructions at the top)
- Create your own repo on GitHub and push
- Follow
QUICKSTART.mdfor step-by-step setup - Customize using
CUSTOMIZE.mdto adapt to your tools and workflow
Your clone becomes your team's knowledge base and will diverge from here. That's expected and encouraged.
See CLAUDE.md for the full system overview once you're set up.
Repo Structure at a Glance
├── strategy/ # Beliefs, competitive intel, open questions
├── product/ # Overview, metrics, terminology, review patterns
├── team/ # People, rituals, channels
├── roadmap/ # Sources, tracking, strategic initiatives
├── projects/ # One folder per project with full lifecycle artifacts
│ ├── _template/ # Copy to start a new project
│ └── _example/ # Fully worked example
├── meetings/ # Recurring sync notes with routing workflows
├── design/ # Design conventions and contribution guide
├── customer-intelligence/ # Feedback scans, call analyses, deep dives
├── config/ # repo-hygiene.json + workflow configs (single source of truth)
├── reference-docs/ # Static reference materials
├── add-ons/ # Opt-in patterns — engineering, data-science,
│ # leadership-forum, memories, and four extra skills
└── .claude/
├── skills/ # 11 automated workflows (each self-improving)
├── agents/ # 5 specialized agents
├── commands/ # 4 PM workflow commands
└── rules/ # Context-triggered conventions
If you're using this, star the repo — it helps track adoption and prioritize improvements.
Credits
Created and maintained by Akshat Khandelwal.