skills/ideas-pipeline/SKILL.md (3370 bytes)
1 --- 2 name: ideas-pipeline 3 description: Build the next ideamine idea, or a given id, through the agent pipeline that ships with ideamine (research, storyboard, plan, engineers, test, validate). For big ideas. New ideas are triaged first. 4 argument-hint: "[id]" 5 disable-model-invocation: true 6 allowed-tools: mcp__plugin_ideamine_ideamine__idea_next, mcp__plugin_ideamine_ideamine__idea_update, mcp__plugin_ideamine_ideamine__idea_triage 7 --- 8 9 Run one idea through the agent pipeline. Requested idea: $ARGUMENTS (empty means the next idea in the queue). 10 11 The pipeline is the `pipeline` skill of this plugin (`ideamine:pipeline` in the skill list), with its seven agents in the `agents` folder of the plugin. 12 13 The user saves ideas from any session. The triage pairs each idea with its project folder when one fits. Else the project of an idea is only the folder where the user saved it, and that folder can be wrong or gone. Judge by the text of the idea which idea fits this chat, and where it belongs. 14 15 1. Call `idea_next` with `triage: true`. Pass `id` if an id is given. The tool triages new ideas first. If it says that the queue is empty, say so in one line and stop. If the triage failed and no idea came back, call `idea_triage` with no verdicts, judge those ideas, save all verdicts in ONE `idea_triage` call with your model name as `by`, and then call `idea_next` again. 16 2. If no id is given, the tool also returns the whole queue. If an idea in the queue clearly fits this chat (the current project or this conversation), call `idea_next` with its `id`, and take that idea. Else take the first idea. 17 3. Choose the project directory. Use the current project if the idea fits it. Else use the project directory of the idea if it exists and fits the idea (the tool tells if it exists). Else find the project that the idea is about. If you cannot find it, say so in one line and stop. 18 4. Tell the user the title and the directory in one line. Then call `idea_update` with status "doing", `project` set to that directory, and the note "pipeline: started". 19 5. Invoke the `pipeline` skill with this request, in this shape: 20 21 ``` 22 Build idea #<id> from my ideamine archive: <title> 23 <brief> 24 My original note: <text> 25 Project: <directory> 26 27 Progress: ideamine idea #<id> is the record of this run. After each phase and each gate, add one note to it with the ideamine idea_update tool (id <id>, note), or run `ideamine note <id> "pipeline: <phase>"`. Use notes like "pipeline: research done", "pipeline: storyboard approved", "pipeline: plan approved (3 tasks, 2 waves)", "pipeline: wave 1 integrated", "pipeline: round 1 failed: <one line>". 28 When the tester and the validator both pass, call idea_update with status "done" and a one-line note. If the run stops at its iteration cap or escalates, leave the idea in "doing" and add a note that says what failed and where the reports are. 29 ``` 30 31 The pipeline does not know ideamine; these lines tell it what to record. It has two gates where it asks the user for approval; that is expected. 32 6. When the pipeline ends, check the idea with `idea_next` (`id`) or the pipeline's final report. If the pipeline passed and the idea is not yet done, call `idea_update` with status "done" and a one-line note. If work remains, keep status "doing" and write a note that says what remains. Then summarize in 2-3 lines.