idea-to-production

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. 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.

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.

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.

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.

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.

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.

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 deliver's frontend design-system and publish's graphics by capability; degrades to markdown when absent. Uses the host-provided chrome-devtools MCP (ONE BROWSER — bundles none) for live review.

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.