By iam-jonny
Document and meeting intake skills for classifying meeting files, gathering local context, and routing outputs to draft, update, or finalize workflows.
Decide whether meeting or document intake should create a Draft, update an existing artifact, Finalize a shareable artifact, or produce Summary only. Use when Codex needs to route transcripts or notes into product/project documentation workflows.
Discover what product, project, initiative, repository, document set, or stakeholder context is needed before processing meeting notes or document files. Use when a transcript or document cannot be safely summarized, drafted, updated, or finalized without additional context.
Diagnose document and meeting intake requests, ask minimal context questions, gather local documentation candidates, and route to draft, update, finalize, or summary workflows. Use when Codex receives meeting transcripts, notes, PDFs, Word files, Markdown, Notion or Confluence exports, or files detected by folder-monitor-tools.
Search local repositories or documentation folders for relevant context before drafting, updating, or finalizing product or project artifacts. Use when meeting notes reference existing PRDs, BRDs, project plans, architecture docs, decisions, roadmaps, or status documents.
Draft meeting outputs for Slack, email, Markdown, Notion, Confluence, Word outline, or PowerPoint outline from transcripts or notes. Use after meeting type and output mode are known, especially for summaries, decisions, action items, risks, blockers, and follow-up messages.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Local Codex and Claude Code plugin and skill definitions for product management work.
This repository contains local plugins that can be used from Codex and Claude Code.
| Plugin | Purpose |
|---|---|
product-management-tools | Turn messy product inputs into aligned BRDs, PRDs, PBIs, priorities, and roadmaps. |
project-management-tools | Turn messy project inputs into aligned charters, plans, risks, status reports, change decisions, and retrospectives. |
folder-monitor-tools | Detect and triage new local files for downstream document and meeting workflows. |
document-intake-tools | Classify meeting files, gather local context, and route outputs to Draft, Update, Finalize, or Summary workflows. |
product-management-tools provides focused skills for turning messy product
inputs into decision-ready product artifacts and alignment steps:
The plugin is intended to help turn rough product context, strategy notes, stakeholder requests, and draft documents into clearer, more decision-ready artifacts.
The skills are designed to work together in layers:
Common workflow:
meeting notes / paper notes / transcript / stakeholder request
-> product-orchestrator
-> product-intake-synthesize
-> brd-create
-> business-requirements-review
-> artifact-alignment
-> prd-create
-> prd-review
-> stakeholder-review-synthesize
-> pbi-review / pbi-prioritize / roadmap-create
The product management plugin lives at:
plugins/product-management-tools
Its plugin manifest is:
plugins/product-management-tools/.codex-plugin/plugin.json
Codex uses this manifest to discover the plugin name, display metadata, and skills directory.
The project management plugin lives at:
plugins/project-management-tools
Its plugin manifest is:
plugins/project-management-tools/.codex-plugin/plugin.json
This repository also includes a Claude Code marketplace manifest:
.claude-plugin/marketplace.json
The marketplace exposes the product-management-tools plugin from:
plugins/product-management-tools
The Claude Code plugin manifest is:
plugins/product-management-tools/.claude-plugin/plugin.json
After this repository is public, Claude Code users can add the marketplace:
/plugin marketplace add https://github.com/iam-jonny/jonny-agent-skills
Then install a plugin:
/plugin install product-management-tools@jonny-agent-skills
/plugin install project-management-tools@jonny-agent-skills
/plugin install folder-monitor-tools@jonny-agent-skills
/plugin install document-intake-tools@jonny-agent-skills
For local testing from a checkout of this repository:
/plugin marketplace add ./path/to/jonny-agent-skills
/plugin install product-management-tools@jonny-agent-skills
/plugin install project-management-tools@jonny-agent-skills
/plugin install folder-monitor-tools@jonny-agent-skills
/plugin install document-intake-tools@jonny-agent-skills
npx claudepluginhub iam-jonny/jonny-agent-skills --plugin document-intake-toolsProject management skills for turning messy inputs into aligned charters, plans, risks, status reports, change decisions, and retrospectives.
Product management skills for turning messy inputs into aligned BRDs, PRDs, PBIs, priorities, and roadmaps.
Folder monitoring skills and scripts for detecting new local files, triaging them, and routing them to downstream document or meeting workflows.
Comprehensive C4 architecture documentation workflow with bottom-up code analysis, component synthesis, container mapping, and context diagram generation
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Plugin-safe Claude Code distribution of Antigravity Awesome Skills with 1,561 supported skills.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.