inno-pipeline-planner

id	inno-pipeline-planner
name	inno-pipeline-planner
version	1.0.0
description	Guides the user through an interactive conversation to define their research project, then generates research_brief.json and tasks.json.
stages	["ideation"]
tools	["read_file","search_project","write_file"]
summary	Guides the user through an interactive conversation to define their research project, then generates research_brief.json and tasks.json. Use when starting a new project, when no research_brief.json exists, when the user wants to start from...
primaryIntent	research
intents	["research","experiment"]
capabilities	["research-planning","agent-workflow"]
domains	["general"]
keywords	["inno-pipeline-planner","research-planning","agent-workflow","inno","pipeline","planner","guides","user","through","interactive","conversation","define"]
source	builtin
status	verified
upstream	{"repo":"dr-claw","path":"skills/inno-pipeline-planner","revision":"8322dc4ef575affaa374aa7922c0a0971c6db7d7"}
resourceFlags	{"hasReferences":true,"hasScripts":false,"hasTemplates":false,"hasAssets":false,"referenceCount":4,"scriptCount":0,"templateCount":0,"assetCount":0,"optionalScripts":false}

inno-pipeline-planner

Canonical Summary

Guides the user through an interactive conversation to define their research project, then generates research_brief.json and tasks.json. Use when starting a new project, when no research_brief.json exists, when the user wants to start from...

Trigger Rules

Use this skill when the user request matches its research workflow scope. Prefer the bundled resources instead of recreating templates or reference material. Keep outputs traceable to project files, citations, scripts, or upstream evidence.

Resource Use Rules

• Read from references/ only when the current task needs the extra detail.

Execution Contract

• Resolve every relative path from this skill directory first.
• Prefer inspection before mutation when invoking bundled scripts.
• If a required runtime, CLI, credential, or API is unavailable, explain the blocker and continue with the best manual fallback instead of silently skipping the step.
• Do not write generated artifacts back into the skill directory; save them inside the active project workspace.

Upstream Instructions

Inno Pipeline Planner

Run an interactive planning flow that turns user conversation into:

• .pipeline/docs/research_brief.json
• .pipeline/tasks/tasks.json

Keep this file short. Load full schemas and field-level rules from:

• references/pipeline-contract.md (index)

Read only what you need:

• references/generation-rules.md: generation logic, ordering, dependencies, nextActionPrompt
• references/brief-schema.md: .pipeline/docs/research_brief.json contract
• references/tasks-schema.md: .pipeline/tasks/tasks.json contract

Non-negotiables

• Work only inside the current project directory.
• Do not fabricate papers, datasets, metrics, or results.
• Ask follow-up questions when information is vague; do not guess.
• Ask in small batches (2-3 questions), not a long static form.

Workflow

1) Inspect existing pipeline state

Check:

• .pipeline/docs/research_brief.json
• .pipeline/tasks/tasks.json
• instance.json (legacy source)