Skill Claude CodeCodex
Orchestrate a product idea into a complete, delivery-grade PRD workspace by running the PRD skills with stage gates and automatic feedback loops. Use when the user asks to run the full idea-to-PRD workflow, create a PRD from a rough idea, or coordinate multiple PRD drafting stages. Do not use for editing one isolated…
Skill Claude CodeCodex
Convert a rough product idea, user feedback, or operations request into a structured product problem brief. Use at the very beginning of PRD work. Do not use to write rules, page specs, backend config, or final PRD.
Skill Claude CodeCodex
Define product scope, version boundary, business constraints, non-goals, and stakeholder decisions for a PRD. Use after the idea has been clarified. Do not use for detailed rule tables, page copy, or final PRD compression.
Skill Claude CodeCodex
Convert product descriptions into executable product rules: objects, states, permissions, conditions, thresholds, time windows, conflict handling, and user-visible outcomes. Use when PRD logic needs to become precise. Do not use for broad strategy, UI layout, backend implementation, or final writing polish.
Skill Claude CodeCodex
Build user flows, system judgment flows, state transitions, and exception flows from a product rule model. Use after core rules are defined. Do not use to invent business rules or write UI detail.
Skill Claude CodeCodex
Convert PRD flows into page-level and interaction-level product specs: entry, layout information hierarchy, components, button states, empty states, error states, and user copy. Use after flows are stable. Do not use for visual design, brand style, or backend configuration.
Skill Claude CodeCodex
Identify only the necessary backend, admin, and operations configuration for a PRD. Use when a feature needs operational control, resource configuration, manual handling, or admin visibility. Do not use to automatically add a large admin system to every feature.
Skill Claude CodeCodex
Define success metrics, event tracking needs, and QA acceptance criteria for a PRD. Use after rules, flows, pages, and admin needs are drafted. Do not use to invent unrelated dashboards or vanity metrics.
Skill Claude CodeCodex
Review a PRD draft for historical debt, compatibility issues, abuse risk, cost risk, operational risk, legal/finance/risk-control boundaries, and responsibility gaps. Use before final PRD compression or before engineering review. Do not use for rewriting the whole PRD.
Skill Claude CodeCodex
Compress resolved PRD stage artifacts into a concise delivery-grade PRD for engineering, design, QA, and operations. Use only after stage gates are resolved. Do not use to invent new requirements.
Skill Claude CodeCodex
Create a standalone HTML handoff artifact from completed PRD markdown workspaces. Use when Codex finishes a delivery-grade PRD workflow, needs to turn PRD source files into a human-readable handoff console, or when the user asks for HTML/readability/visual PRD output.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: