claude

IDEA-TO-PRODUCTION — Marketplace front door, arrival layer & meta-commands

The FRONT DOOR, ARRIVAL layer, and meta-layer of the marketplace — the marketplace-level surface the specialist plugins never had. /i2p:help browses the powers you have now, grouped by the DISCOVER ▸ IDEATE ▸ BUILD ▸ DESIGN ▸ SECURE ▸ PUBLISH value flow (listing only what is installed); /i2p:review fans out EVERY installed reviewer — code (deliver), design (design), rendered docs (publish), security (secure) — into ONE adversarial verdict in I2P_REVIEW.md; /i2p:check consolidates every plugin's readiness into one table; /i2p:flow maps where each plugin sits and the next command to run; /i2p:focus declares the active lifecycle phase for context routing so out-of-phase skills stay dormant ('focus, don't uninstall'), broadcast by a SessionStart hook so it survives /clear. It also GREETS whoever opens a repo: a SessionStart hook renders a maintainer-authored .claude/welcome.md (/i2p:define-welcome authors it), and /i2p:statusline turns on the rich two-line idea-to-production status line (context & rate-limit gauges, the product-lifecycle phase, a ⚔ reviewer-catch tally), offered once on first activation. Introduces itself on session start and surfaces occasional ≤25-word tips. A thin orchestrator that delegates to the specialists by capability and never re-implements them. Carries the KAIZEN self-improvement covenant.

0 on GitHubby whatbirdisthatv1.4.0MIT OR Apache-2.0updated 2 months agoworkflow
/

Plugin i2p from marketplace idea-to-production in agentic-underground/idea-to-production. Commands read from the repo's manifest — 1 month ago.

This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.

What it installs

Skills (10)

  • check

    Consolidated marketplace readiness. Use for /i2p:check (or "are all my tools installed?", "check the whole marketplace", "what's missing across the plugins?"). Runs every installed plugin's /check and merges the ✓/✗ results into one table grouped by plugin, then summarises what's missing and how to

  • define-welcome

    Define this repository's welcome experience — the front door someone meets when they open it. Reads the repo, proposes 2-4 "lanes" with decision trees, and writes .claude/welcome.md in the i2p welcome format (phase-stamped in a lifecycle) so the SessionStart hook greets and routes arrivals. Trigger

  • flow

    The value-flow map. Trigger with /i2p:flow (or "show me the value flow", "where does each plugin fit?", "what's my next step?", "draw the pipeline"). Places each installed plugin on the nine-phase DISCOVER-to-OPERATE flow, names the headline command + artefact at each stage, marks dark stages, and t

  • focus

    Declare the active lifecycle PHASE so out-of-phase skills stay dormant — the "focus, don't uninstall" answer to context-pollution. Trigger with /i2p:focus (or "focus on DISCOVER", "set focus to build", "clear focus", "what's my focus?"). Writes .i2p/focus; a SessionStart hook broadcasts it (survives

  • help

    The marketplace's front door. Trigger with /i2p:help (or "what can i2p do?", "what powers do I have now?", "browse the idea-to-production marketplace", "where do I start?"). Renders the three pillars and the nine-phase DISCOVER-to-OPERATE value flow, listing only installed plugins with their headlin

  • lifecycle

    Start and report the idea-to-production PRODUCT LIFECYCLE for a project. Use for /i2p:lifecycle (or "start a product lifecycle", "what phase are we in?", "kick off idea-to-production", "advance the lifecycle"). Reads/writes .i2p/lifecycle.json via scripts/lifecycle.sh and explains the model from kno

  • review

    The marketplace-wide adversarial review. Trigger with /i2p:review (or "review everything", "one verdict from every reviewer"). Fans out every installed specialist reviewer (code, design, rendered docs, security), adversarially verifies the serious findings, and synthesises ONE verdict (PASS/NEEDS_RE

  • self-improve

    Improve the i2p front door itself — fold discoverability feedback into /i2p:help, the tips, and the /i2p:review fan-out, or self-cleave an over-broad element. Trigger with /i2p:self-improve (or "a user couldn't find a power they had — fix the front door", "/i2p:review missed a reviewer it should run

  • statusline-install

    Install (or remove) the idea-to-production status line. Trigger with /i2p:statusline (or "give me the status bar", "turn on the i2p status line", "turn off the status line"). Copies the plugin's renderer to ~/.claude and points settings.json at it (portable across machines), or removes it with `off`

  • statusline-widgets

    Edit the line-break layout of the status line's line-2 widgets so the bar fits your terminal. Trigger with /i2p:statusline-widgets (or "edit the statusline widgets", "make the statusline wrap"). Assigns each widget a break attribute — break-before, break-after, or none (flow inline; the terminal sof

Slash commands (10)

  • /i2p:check

    Consolidated readiness — run every installed idea-to-production plugin's /check and merge the ✓/✗ results into one table by plugin, with a short summary of what's missing and how to install it.

  • /i2p:define-welcome

    Define this repository's welcome experience — read the repo, propose 2–4 conversational "lanes" with concrete decision trees, and write .claude/welcome.md so i2p greets and routes whoever opens it next.

  • /i2p:flow

    Show the idea-to-production value flow — where each installed plugin sits across DISCOVER ▸ IDEATE ▸ DELIVER ▸ DESIGN ▸ BUILD ⇄ ASSURE ⇄ SECURE ▸ PUBLISH ▸ OPERATE ↻ and the next command to run at each stage (Mermaid when available, else markdown).

  • /i2p:focus

    Declare the active lifecycle PHASE for context routing — out-of-phase skills stay dormant ("focus, don't uninstall"). Writes .i2p/focus; a SessionStart hook broadcasts it (survives /clear). Best-effort steering, not a hard gate.

  • /i2p:help

    Browse the idea-to-production marketplace — the powers you have now, grouped by the DISCOVER ▸ IDEATE ▸ DELIVER ▸ DESIGN ▸ BUILD ⇄ ASSURE ⇄ SECURE ▸ PUBLISH ▸ OPERATE ↻ value flow, listing only the plugins currently installed and the next command to run.

  • /i2p:inspect

    Inspect the i2p plugin itself — audit commands, skills, hooks, and knowledge for drift, gaps, and duplication; produce a severity-ranked report.

  • /i2p:lifecycle

    Start or report the idea-to-production PRODUCT LIFECYCLE — DISCOVER ▸ IDEATE ▸ DELIVER ▸ DESIGN ▸ BUILD ⇄ ASSURE ⇄ SECURE ▸ PUBLISH ▸ OPERATE ↻ (nine phases forming a cycle, with the BUILD ⇄ ASSURE ⇄ SECURE loop). Tracks .i2p/lifecycle.json; the status line shows the phase.

  • /i2p:review

    Cross-plugin adversarial review — fan out EVERY installed specialist reviewer (code, design, rendered docs, security) and synthesise ONE verdict (PASS / NEEDS_REVISION / BLOCK) in I2P_REVIEW.md, naming what could not be reviewed.

  • /i2p:statusline-widgets

    Edit the line-break layout of the status line's line-2 widgets so the bar fits your terminal — assign each widget break-before / break-after / none (none flows inline and lets the terminal wrap).

  • /i2p:statusline

    Turn on the idea-to-production status line — a rich two-line ANSI bar (context/rate-limit gauges, the product-lifecycle phase, and the ⚔ reviewer-catch tally). Pass `off` to remove it.

Subagents (1)

  • inspector

    i2p INSPECTOR — on-demand agent that audits the i2p front door plugin it ships in (commands, skills, hooks, knowledge under ${CLAUDE_PLUGIN_ROOT}). Triggered by user command only ("inspect i2p" / "/i2p:inspect"). Builds a fresh critical-analysis persona, reads every file, and produces I2P_INSPECTION

Hooks (14)

  • SessionStart

    bash ${CLAUDE_PLUGIN_ROOT}/hooks/inject-kaizen.sh 2>/dev/null || true

  • SessionStart

    bash ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/phase-pointer.sh 2>/dev/null || true

  • SessionStart

    bash ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/roadmap-routing.sh 2>/dev/null || true

  • SessionStart

    bash ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/focus-routing.sh 2>/dev/null || true

  • SessionStart

    bash ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/mcp-liveness.sh 2>/dev/null || true

  • SessionStart

    bash ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/offer-cache-update.sh 2>/dev/null || true

  • SessionStart

    bash ${CLAUDE_PLUGIN_ROOT}/hooks/inject-welcome.sh 2>/dev/null || true

  • SessionStart

    bash ${CLAUDE_PLUGIN_ROOT}/hooks/offer-welcome.sh 2>/dev/null || true

  • SessionStart

    bash ${CLAUDE_PLUGIN_ROOT}/hooks/offer-doc-alert.sh 2>/dev/null || true

  • SessionStart

    bash ${CLAUDE_PLUGIN_ROOT}/hooks/offer-statusline.sh 2>/dev/null || true

  • SessionStart

    bash ${CLAUDE_PLUGIN_ROOT}/hooks/check-statusline-drift.sh 2>/dev/null || true

  • UserPromptSubmit

    bash ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/tips.sh 2>/dev/null || true

  • PostToolUse

    bash ${CLAUDE_PLUGIN_ROOT}/statusline/count-adversarial-catches.sh 2>/dev/null || true

  • Stop

    bash ${CLAUDE_PLUGIN_ROOT}/statusline/capture-cost.sh 2>/dev/null || true

View source on GitHub

More from agentic-underground/idea-to-production

All 8 plugins →

An opinionated, disciplined, quality-first software production system. A conveyor that carries value from IDEA to PRODUCTION across role-tuned agents and value-stations (IDEA ▶ ROADMAP ▶ PLAN ▶ EARS ▶ FEATURE ▶ TEST ▶ IMPLEMENT ▶ STORY ▶ SHIP), governed by three pillars — knowledge parity, quality-first with a performance-delta gate, and waste elimination (muda·mura·muri) — under an overarching token-efficiency constraint. Emits markdown; uses the secure and publish companions automatically when present.

19 skills · 13 commands · 32 agents · 1 MCP server · hooks

0

Turns project artefacts and markdown into publication-grade output: narrative articles mined from git history and docs, standalone diagrams (Graphviz + a Mermaid-native specialist covering the full diagram taxonomy, theming, and ELK), and print-quality PDFs with embedded, A4-legible figures — all held to standard by an adversarial design-reviewer (typography + data-viz canon) that critiques the rendered artefact in a convergent loop. The PUBLISHING companion deliver hands off to when richer-than-markdown output is wanted — or use it directly on any project.

10 skills · 5 commands · 8 agents · hooks

0

The OPERATE phase owner — what runs a mission AFTER launch. OPERATE keeps the live product alive and improving: it verifies operational readiness at go-live, instruments and watches the four golden signals (observability), runs incident response (severity, incident-command roles, mitigate-first, runbooks, blameless postmortems), keeps a maintenance cadence (dependency upkeep + CVE patching + tech-debt), and closes the build-measure-learn loop by turning production signals into a new opportunity that re-enters DISCOVER (the cyclic re-entry). /operate-gate is the front door — an operational-readiness check at go-live and the steady-state health view with a READY / WATCH / NOT-READY verdict. Grounded in named canon (SRE SLIs/SLOs/error budgets + golden signals, the Incident Command System, build-measure-learn, ITIL-lite). Stands alone on any live project, or advances the idea-to-production lifecycle OPERATE → DISCOVER (↻) when i2p is installed. Composes the secure plugin's scan-dependencies and hands new opportunities to discover/ideate by capability. Carries the KAIZEN self-improvement covenant: every incident becomes a runbook, every alert gap becomes an SLO.

9 skills · 9 commands · 1 agent · hooks

0

The pre-release security gate for any repository. Catches PII, secrets/credentials, and supply-chain risk before they ship. Runs parallel, multi-agent audits across data files, git history, source, and frontend, and consolidates them into a single severity-ranked report with a PASS / REVIEW / BLOCK verdict. Stands alone, or serves as deliver's SECURE gate when both are installed.

6 skills · 6 commands · 1 agent · hooks

0

The DISCOVERY front door of the marketplace — upstream of any code. Set a standing discovery /discovery-goal, then run /market-scan: an adversarially-challenged dialogue over a market parameter taxonomy (problem severity, demand evidence, market size, willingness-to-pay, pricing power, competition, reachability, stack-fit) that proposes, scores, validates, and NARROWS candidate opportunities, killing weak ideas early. Loop it over your goal until one candidate earns a keep verdict — the spark. Hands a validated OPPORTUNITY to the ideate plugin when installed, or emits a structured markdown opportunity brief standalone. Self-improving: downstream feedback sharpens the parameters and scoring over time.

4 skills · 4 commands · 2 agents · 1 MCP server · hooks

0

The REFINEMENT phase of the marketplace. Takes a validated opportunity (from discover) or a raw idea you already have and refines it to knowledge-parity through an adversarially-challenged dialogue, producing the IDEA PACKAGE: precise AGENT-FACING handoff documents (idea brief, subject-matter-understanding seed, first vertical slice, and a handoff contract that satisfies DELIVER's discovery exit criteria) plus rich, illustrated USER-FACING documents (opportunity narrative, parameter scorecard, market/pricing/competition charts, a user-flow, and a mockup screen) rendered by capability — charts via publish, user-flows/mockups via design (design-reviewed) — when installed; degrades to markdown otherwise. Iterated with the user before hand-off, then carried to PRODUCTION by DELIVER. Supersedes DELIVER's inline ideate, which remains as a graceful-degradation fallback. Also runs /ideate:name — a marketing-grade naming studio: a deep discovery interview (audience, brand archetype, name-type appetite, power-adjacency, humour, risk), wide-net generation across the full name-type taxonomy + affix hooks + phonosemantic tuning, a deterministic token-free checker (registries + neighbour/typo-squat proximity + domain/RDAP + cross-language connotation), and a scored challenge (Neumeier 7 / SMILE-SCRATCH / archetype-fit). Self-improving: ambiguities a downstream builder hits flow back to sharpen the question-bank and the package contract.

4 skills · 4 commands · 2 agents · 1 MCP server · hooks

0

Similar plugins

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development

9 skills · 1 command · 8 agents

wshobson/agents 42,461

beads

claudecodex

AI-supervised issue tracker for coding workflows

1 skill · 1 agent · hooks

gastownhall/beads 28,698

MiniMax AI skills library for frontend, fullstack, Android, iOS, shader, GIF sticker, document, presentation, spreadsheet, and multimodal media workflows

18 skills

MiniMax-AI/skills 13,828

worktrunk

claudecodex

Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows. This plugin provides configuration guidance (LLM commit messages, project hooks, worktree paths), automatic activity tracking (🤖/💬 indicators in `wt list` showing active Claude sessions), and a `/wt-diff` pane showing each worktree's changes.

2 skills · hooks

max-sixty/worktrunk 12,481

gsd-core

claude

GSD Core is a meta-prompting, context engineering, and spec-driven development system for AI coding agents.

72 skills · 72 commands · 64 agents · hooks

open-gsd/gsd-core 11,494

Maintain IDEA-TO-PRODUCTION — Marketplace front door, arrival layer & meta-commands?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins8 plugins