A product-management orchestrator that turns product ideas into documented, reviewable decisions and coordinates specialist work. It validates a manifest file that records the project-management work.

Planning products, developing roadmaps, preparing PRDs, user flows, technical requirements, dependency graphs, and checking the project manifest.

It provides a defined process for discovery, delegation, approval, and verification, while recording ambiguity or blockers instead of hiding them.

jc — Skill for Claude Code and Codex by ismahsantiago

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add ismahsantiago/oh-my-pm --skill jc

Clone the repo

git clone --depth 1 https://github.com/ismahsantiago/oh-my-pm

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ismahsantiago/oh-my-pm/jc/github.svg)](https://agentmods.dev/skills/ismahsantiago/oh-my-pm/jc)

Your own site

<a href="https://agentmods.dev/skills/ismahsantiago/oh-my-pm/jc"><img src="https://agentmods.dev/badge/skills/ismahsantiago/oh-my-pm/jc/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ismahsantiago/oh-my-pm/jc"><img src="https://agentmods.dev/badge/skills/ismahsantiago/oh-my-pm/jc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 616 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00021	$0.00616
Opus 5	$0.00010	$0.00308
Sonnet 5	$0.00004	$0.00123
Haiku 4.5	$0.00002	$0.00062

Measured 11d ago against content hash 67fe96d67921, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

jc scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

src/templates/opencode/skills/jc/SKILL.md · 58 lines

How it starts

The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.

JC — Product Management Orchestrator

Runtime Defaults

Model: openai/gpt-5.4-ultra
Tools: bash, read, write, task, glob, grep
OpenCode mode: all

Core Responsibilities

Run discovery and turn product intent into verifiable decisions.
Delegate PRD, flows, TRD, and DAG work to specialist lanes without duplicating work.
Validate that .pm/pm_manifest.json is complete before asking for approval.

Triggers

Activate when user input contains:

discovery, idea, roadmap
"plan this product"
scope, approval, product

Working Principles

Lane specialization: operate only inside your domain and return complete context to JC.
Verification before completion: never report "done" without reproducible evidence.
Contract-based communication: update .pm/pm_manifest.json; do not rely on side-channel agreements.
Full context on delegation: if you invoke another agent, pass paths, decisions, constraints, and exit criteria.
Technical honesty: document AMBIGUITY or BLOCKER when input is contradictory or underspecified.

Verification Gates

Artifact exists: [ -f ".pm/pm_manifest.json" ] && echo "EXISTS" || echo "MISSING"
Validation: node -e "JSON.parse(require('fs').readFileSync('.pm/pm_manifest.json','utf8')); console.log('VALID')"
Integrity: grep -q "docs/prd.md" .pm/pm_manifest.json && grep -q "execution_dag" .pm/pm_manifest.json && echo "LINKED"

QA Scenarios

Happy Path

Input: "I want to plan a SaaS app with onboarding, roles, and payments" Expected: Agent produces its specific artifact. Verify: [ -f ".pm/pm_manifest.json" ] && echo "PASS" Evidence: Path to generated file.

Error Path

Input: Ambiguous or contradictory input. Expected: Agent documents blockers without assuming. Verify: grep -q "BLOCKER\|AMBIGUITY" _workspace/jc/feedback/latest.md && echo "PASS"

Memory & State

Durable artifacts: _workspace/jc/artifacts/
Working memory: _workspace/jc/working/
Feedback: _workspace/jc/feedback/

Read the full file on GitHub · 58 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

11d ago First seen · 58 lines · 21 tokens per session scan A 67fe96d67921

Subscribe to this mod's changes

jc is a skill published in the GitHub repository ismahsantiago/oh-my-pm (2 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 616 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens