The FRONT DOOR of the idea-to-production marketplace — the marketplace-level front door the seven specialist plugins never had. Adds /i2p-help (browse the whole suite's powers, grouped by the DISCOVER ▸ IDEATE ▸ DESIGN ▸ BUILD ▸ ASSURE ▸ SECURE ▸ PUBLISH ▸ OPERATE ↻ value flow), /i2p-review (a cross-plugin adversarial review that fans out EVERY installed reviewer — code, design, docs, security — into one verdict), /i2p-check (consolidated readiness across all installed plugins), and /i2p-flow (where each plugin sits in the flow and the next command to run). Introduces itself on session start and surfaces occasional ≤25-word tips. A thin orchestrator: it delegates to the specialist plugins by capability and never re-implements them. Carries the KAIZEN self-improvement covenant.
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
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.
Show the idea-to-production value flow — where each installed plugin sits across DISCOVER ▸ IDEATE ▸ DESIGN ▸ BUILD ▸ ASSURE ▸ SECURE ▸ PUBLISH ▸ OPERATE ↻ and the next command to run at each stage (Mermaid when available, else markdown).
Browse the idea-to-production marketplace — the powers you have now, grouped by the DISCOVER ▸ IDEATE ▸ DESIGN ▸ BUILD ▸ ASSURE ▸ SECURE ▸ PUBLISH ▸ OPERATE ↻ value flow, listing only the plugins currently installed and the next command to run.
Start or report the idea-to-production PRODUCT LIFECYCLE — DISCOVER ▸ IDEATE ▸ DESIGN ▸ BUILD ▸ ASSURE ▸ SECURE ▸ PUBLISH ▸ OPERATE ↻ (eight phases forming a cycle). Tracks .i2p/lifecycle.json; the status line shows the phase.
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.
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 install it. Thin: it delegates to each plugin's check, it owns no probes of its own.
The value-flow map. Use for /i2p-flow (or "show me the value flow", "where does each plugin fit?", "what's my next step?", "draw the idea-to-production pipeline"). Places each installed plugin on DISCOVER ▸ IDEATE ▸ DESIGN ▸ BUILD ▸ ASSURE ▸ SECURE ▸ PUBLISH ▸ OPERATE, names the headline command and artefact at each stage, marks dark stages, and — given a starting point — traces the ordered path to PRODUCTION. Renders Mermaid when a renderer is present, else markdown.
The marketplace's front door. Use for /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 DISCOVER ▸ IDEATE ▸ DESIGN ▸ BUILD ▸ ASSURE ▸ SECURE ▸ PUBLISH ▸ OPERATE value flow, listing only the plugins currently installed with their headline commands and the next thing to run, then points at the deeper docs. Thin: it describes the specialists, it does not run them.
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 knowledge/product-lifecycle.md. The statusline phase widget reads the same state file.
The marketplace-wide adversarial review. Use for /i2p-review (or "review everything", "full review across all the plugins", "give me one verdict from every reviewer"). Determines scope, fans out EVERY installed specialist reviewer — code (foundry /pr-review), design (atelier /ui-review), rendered docs (pressroom design-review), security (sentinel /security-gate) — adversarially verifies the serious findings, and synthesises ONE verdict (PASS / NEEDS_REVISION / BLOCK) in I2P_REVIEW.md, naming what could not be reviewed. Thin: it composes the specialists, it does not re-implement review logic.
Uses power tools
Uses Bash, Write, or Edit tools
Carry software from the spark of an IDEA to PRODUCTION — nine composable Claude Code plugins, one disciplined, test-first value flow: discover ▸ refine ▸ design ▸ build ▸ assure ▸ secure ▸ publish ▸ operate.
Start here →
/i2p-helpbrowses every power you have ·/i2p-flowshows the pipeline ·/i2p-reviewgives one verdict from every reviewer. The i2p plugin is the front door; concierge greets whoever opens the repo.
A disciplined, test-first conveyor that carries VALUE from IDEA to PRODUCTION, governed by three pillars under one overarching constraint:
| Pillar | also called | in one line |
|---|---|---|
| 🧭 Knowledge-parity | knowledge-alignment | understand the ask completely before acting — recurring questions become written answers, asked once. |
| 🛡️ Quality-first | quality-confidence | quality is built in, not inspected in — every station, strengthened by a performance-delta gate; a gate is never weakened to make progress. |
| ♻️ Waste-elimination | muda · mura · muri | remove waste in every form, including rediscovery — a bug caught in development is far cheaper than one in production. The three Ms: muda (waste), mura (unevenness), muri (overburden). |
Overarching constraint — token-efficiency: thin skills, fat references; define once, reference many; load only what a station needs. And the marketplace is self-improving: when an element learns from a mistake, it folds the fix back into itself — self-cleaving into smaller, sharper parts where needed — and raises a PR so every user inherits the improvement.
Not decoration — these are the ideas the whole system obeys. The philosophical spine is first-principles.md; the operation is VALUE_FLOW.md.
Knowledge-parity · quality-first · waste-elimination — under one token-efficiency constraint.
A failing test written before the code is a location in logical space; one written after is just a description.
Extract the decidable core; dependencies flow one way, inward. pure ⇒ testable ⇒ coordinate-able ⇒ maximally parallel.
Every pass at least halves the distance to perfection; fix upstream once, ship to all.
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 claimnpx claudepluginhub agentic-underground/idea-to-productionThe DISCOVERY front door of the idea-to-production marketplace. MARKET-SCANNER helps a user find a worth-building opportunity before any code exists: 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, and 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 ideator plugin (REFINEMENT) when installed, or emits a structured markdown opportunity brief standalone. Self-improving: downstream ideation/build feedback sharpens the parameters and scoring over time.
The REFINEMENT phase of the idea-to-production marketplace. IDEATOR takes a validated opportunity (from the market-scanner plugin) or a raw idea you already have and refines it to knowledge-parity through an adversarially-challenged dialogue, producing the IDEA PACKAGE: precise, high-clarity AGENT-FACING handoff documents (an idea brief, a subject-matter-understanding seed, the first vertical slice, and a handoff contract that satisfies FOUNDRY's discovery exit criteria) plus rich, illustrated USER-FACING documents (the opportunity narrative, a parameter scorecard, market/pricing/competition charts, a user-flow, and a mockup screen) rendered by capability: charts via pressroom, and user-flows/mockups via atelier /mockup (designed to the canon and design-reviewed before you see them) when installed; degrades to markdown otherwise. The package is iterated with the user before hand-off, then carried to PRODUCTION by FOUNDRY. Self-improving: ambiguities a downstream builder hits flow back to sharpen the question-bank and the package contract. Supersedes FOUNDRY's inline ideator (which remains as a graceful-degradation fallback).
The pre-release security gate for any repository. SENTINEL catches PII, secrets/credentials, and supply-chain risk before they ship. It runs parallel, multi-agent audits across data files, git history, source code, and frontend, then consolidates findings into a single severity-ranked report with an overall PASS / REVIEW / BLOCK verdict. Runs standalone on any project, or serves as the SECURITY gate for the foundry plugin when both are installed. Carries a self-improvement covenant: every missed pattern becomes a rule, every false positive becomes an exclusion.
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 sentinel and pressroom companions automatically when present.
The DESIGN studio — a designer's workshop that both makes and critiques visual work to a commercial-grade standard. /ui-review crawls the navigable routes of any SPA (screenshot + accessibility snapshot per route) and writes a scored, prioritised critique where every finding cites a named principle; /mockup composes polished screens, wireframes, and user-flows and runs them through a convergent designer↔reviewer loop until they clear a design-fitness rubric. The reviewer is a heavyweight expert in the design canon — Gestalt, the UX laws (Fitts/Hick/Miller/Jakob), Nielsen's heuristics, Norman's emotional design, and WCAG 2.2 accessibility. Composes with foundry's frontend design-system and pressroom's graphics by capability; degrades to markdown when absent. Self-improving: design feedback sharpens the canon and the rubric via a PR.
v9.44.1 — Patch release for Gemini environment/version detection and qwen auth gating. Run /octo:setup.
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.
Harness-native ECC plugin for engineering teams - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Comprehensive startup business analysis with market sizing (TAM/SAM/SOM), financial modeling, team planning, and strategic research
Binary reverse engineering, malware analysis, firmware security, and software protection research for authorized security research, CTF competitions, and defensive security