Stats
Actions
Tags
From IDEA-TO-PRODUCTION — Marketplace front door & meta-commands
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/i2p:flowinheritThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Answers "where does each plugin fit, and **what do I run next?**" The marketplace is a conveyor that
Answers "where does each plugin fit, and what do I run next?" The marketplace is a conveyor that carries VALUE from IDEA to PRODUCTION; this draws the map with only the parts you have.
DISCOVER ────────▶ IDEATE ─▶ DESIGN ─▶ BUILD ─▶ ASSURE ─▶ SECURE ─▶ PUBLISH ─▶ OPERATE ↻
market-scanner ideator atelier foundry foundry sentinel pressroom mission-
│ (quality) (security) control
/discovery-goal + /ideate /mockup IDEA▶…▶ /pr-review /security /publish observe ·
/market-scan /ui-review SHIP (quality) -gate iterate ↻→DISCOVER
Eight phases forming a cycle — OPERATE's learnings loop back to DISCOVER. ASSURE (foundry,
quality V&V) and SECURE (sentinel, security) are separate first-class gates. Three concerns
cross-cut every phase: usability (atelier/DESIGN), quality (foundry/ASSURE — built-in not
inspected-in), security (sentinel/SECURE — baked in from the start). For each stage, give: the plugin,
its headline command, and the artefact it produces (an OPPORTUNITY → an IDEA package → a
design-reviewed screen → tested code → a quality PASS → a SECURITY-REPORT → an article/PDF → a live,
observed product). Ground the wording in plugins/i2p/knowledge/product-lifecycle.md (canonical),
plugins/foundry/VALUE_FLOW.md, and the marketplace README.md composition diagram.
Place only installed plugins as live stages. Mark each missing plugin's stage as dark:
"▫ DISCOVER — add market-scanner to find what's worth building" / "▫ OPERATE — add mission-control
to observe, respond to incidents, and iterate the live product." A user should see both the path they
have and the path they could unlock.
If $ARGUMENTS names a starting point — "I have a raw idea", "I have a validated opportunity", "I have a
PR to ship" — output the ordered list of commands from there to PRODUCTION, skipping stages whose
plugin is absent (and noting the skip).
flowchart LR and defer rendering to
their engine (so it's legible wherever it lands).Close with a single "your next command" line.
Inherits the front door covenant (knowledge/covenant.md). When the flow gains a stage or a plugin, this
map is the one place that learns it — update once, every /i2p-flow inherits it.
npx claudepluginhub agentic-underground/idea-to-productionGuides test-driven development for Django applications using pytest-django, factory_boy, and Django REST Framework. Covers red-green-refactor workflow, conftest fixtures, and coverage reporting.