name	innovate
description	Start the Vibe Innovation Framework. Runs entry diagnostic, session planning, ICD initialization, and phase dispatch from the user's current uncertainty level (TRL -2 to 4). Use when the user wants to begin a new innovation project, has only a vague idea or none at all, asks where to start, needs the framework's entry routing, or wants to resume from an existing ICD. Trigger phrases include "start innovation", "ich habe eine Idee", "wo fange ich an", "let us begin", "neues Projekt", "framework run starten", "I want to ideate".
argument-hint	[topic-or-working-name]
user-invocable	true

Read the following files:

Then execute the entry protocol from the Orchestrator:

Language: Ask for the preferred language first, before any other interaction. Present the question in multiple languages (English, German, French, Spanish) so non-native speakers understand. Switch to the chosen language for all further interaction.
Identity: Ask for the team or solo name. Use the name naturally throughout the session.
File availability: Since Claude Code has file system access, verify that the referenced docs exist in .claude/docs/. Inform the user if any are missing.
Context loading: Ask if the user has an existing ICD. If yes, read it. If no, proceed.
Entry diagnostic: Ask the diagnostic questions (starting point and working name, team composition, prior knowledge, success criteria, biggest uncertainty).
TRL mapping: Classify uncertainty and map to TRL using the entry phase table in the Orchestrator.
Session plan: Assemble the phase sequence from the entry TRL through the target exit TRL. Present the plan for confirmation.
ICD initialization: Generate or load the ICD.
Phase dispatch: Start the first phase by loading its dedicated file. Each phase closes when its output contract is satisfied.

Additional context from the user: $ARGUMENTS

name	innovate
description	Start the Vibe Innovation Framework. Runs entry diagnostic, session planning, ICD initialization, and phase dispatch from the user's current uncertainty level (TRL -2 to 4). Use when the user wants to begin a new innovation project, has only a vague idea or none at all, asks where to start, needs the framework's entry routing, or wants to resume from an existing ICD. Trigger phrases include "start innovation", "ich habe eine Idee", "wo fange ich an", "let us begin", "neues Projekt", "framework run starten", "I want to ideate".
argument-hint	[topic-or-working-name]
user-invocable	true

Read the following files:

Then execute the entry protocol from the Orchestrator:

Language: Ask for the preferred language first, before any other interaction. Present the question in multiple languages (English, German, French, Spanish) so non-native speakers understand. Switch to the chosen language for all further interaction.
Identity: Ask for the team or solo name. Use the name naturally throughout the session.
File availability: Since Claude Code has file system access, verify that the referenced docs exist in .claude/docs/. Inform the user if any are missing.
Context loading: Ask if the user has an existing ICD. If yes, read it. If no, proceed.
Entry diagnostic: Ask the diagnostic questions (starting point and working name, team composition, prior knowledge, success criteria, biggest uncertainty).
TRL mapping: Classify uncertainty and map to TRL using the entry phase table in the Orchestrator.
Session plan: Assemble the phase sequence from the entry TRL through the target exit TRL. Present the plan for confirmation.
ICD initialization: Generate or load the ICD.
Phase dispatch: Start the first phase by loading its dedicated file. Each phase closes when its output contract is satisfied.

Additional context from the user: $ARGUMENTS

innovate

Plus depuis ce dépôt