From IDEA-TO-PRODUCTION — Marketplace front door & meta-commands
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/i2p:helpinheritThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
One place to answer "I installed this suite — **what can I do now, and where do I start?**" The honest
One place to answer "I installed this suite — what can I do now, and where do I start?" The honest job here is knowledge-parity: close the gap between the powers a user has and the powers they know about. Describe only what is actually installed.
Stance — show, don't oversell. List installed plugins as live powers; list absent ones only as "add it to unlock …". Never imply you can run a command from a plugin that isn't present.
Judge which idea-to-production plugins are active from the skills and commands available to you this
session — this is the marketplace's established capability-detection pattern. Do not shell out or
probe the filesystem. The plugins to look for:
| Plugin | Stage | Headline commands |
|---|---|---|
| market-scanner | DISCOVER | /discovery-goal, /market-scan |
| ideator | IDEATE | /ideate |
| atelier | DESIGN (+ usability cross-cuts) | /ui-review, /mockup |
| foundry | BUILD + ASSURE (quality gate) | /foundry, /pr-review, /coverage-loop, /roadmapper… |
| sentinel | SECURE (security gate) | /security-gate, /secret-scan, /pii-audit, /dependency-audit |
| pressroom | PUBLISH | /publish, /pressroom:design-review |
| mission-control | OPERATE | (add to unlock — observe, respond to incidents, iterate the live product) |
| i2p | front door | /i2p-help, /i2p-review, /i2p-check, /i2p-flow, /i2p-lifecycle |
| concierge | arrival | /concierge:define-welcome, /concierge:statusline |
Keep it scannable — a menu, not an essay:
knowledge/covenant.md.<plugin> to unlock …"./i2p-review (one verdict from every reviewer), /i2p-check (consolidated
readiness), /i2p-flow (the flow + your next command), /i2p-lifecycle (start/track the lifecycle).README.md; plugins/foundry/knowledge/glossary.md (every term);
plugins/foundry/VALUE_FLOW.md (the system).Always include a short Product Lifecycle section, because it is the spine the whole suite is organised
around. Summarise the model from ../../knowledge/product-lifecycle.md:
idea-to-production is the creation arc of a product — it begins with the search for an idea and carries it into OPERATE (realised, live, and kept alive). Eight phases forming a cycle, each owned by one plugin: DISCOVER ① (market-scanner) → IDEATE ② (ideator) → DESIGN ③ (atelier) → BUILD ④ (foundry) → ASSURE ⑤ (foundry — quality V&V) → SECURE ⑥ (sentinel — security) → PUBLISH ⑦ (pressroom) → OPERATE ⑧ (mission-control — observe, respond, iterate) ↻ loops back to DISCOVER. ASSURE and SECURE are separate first-class gates (quality ≠ security). Three concerns cross-cut every phase: usability (atelier), quality (foundry — built-in not inspected-in), security (sentinel — baked in from the start). (The marketing market life cycle — introduction→growth→maturity→decline — runs alongside OPERATE.)
Then offer to kick one off: ask if they'd like to start a product lifecycle for this project. If yes,
run /i2p-lifecycle init (sets phase DISCOVER) and route them to the first installed owner
(/market-scan, or /ideate if they already have a validated idea). If a .i2p/lifecycle.json already
exists, report the current phase instead and offer advance. Mention that the status line shows the
live phase — offer /concierge:statusline if it isn't enabled.
If $ARGUMENTS names a stage or plugin (design, atelier, security…), zoom in: that plugin's
commands, what each produces, and a "next command" suggestion. Otherwise show the whole menu.
Inherits the front door covenant (knowledge/covenant.md). When a user couldn't find a power they had,
that is a gap in this menu — add the missing line or a tip, fixed upstream once, so every future
/i2p-help surfaces 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.