inno-pipeline-planner

Translate research ideas into structured briefs and staged task pipelines.

1.0k|117|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/OpenLAIR/dr-claw --skill inno-pipeline-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: inno-pipeline-planner
Source: https://github.com/OpenLAIR/dr-claw/tree/main/skills/inno-pipeline-planner
Command: npx skills add https://github.com/OpenLAIR/dr-claw --skill inno-pipeline-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps researchers turn vague ideas into a concrete, executable research brief and a staged task pipeline, enabling a repeatable, shareable planning workflow.

Core Features & Use Cases

  • Interactive briefing: guides a conversation to surface topic, goals, and constraints.
  • Generates: .pipeline/docs/research_brief.json and .pipeline/tasks/tasks.json aligned to the project.
  • Loads and respects schemas from the references directory to ensure contract-compliant outputs.
  • Supports starting from different stages (survey, ideation, experiment, publication, promotion) and auto-selects the appropriate tasks while preserving user-provided context.
  • Encourages safe, non-fabricated content and guards against scope creep by enforcing project boundaries.

Quick Start

Start by describing your research idea and objectives, and let the planner generate the initial brief and the staged task pipeline.

Frequently Asked Questions about inno-pipeline-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a vague research idea into a structured execution plan?

You can structure your research pipeline by generating a staged task pipeline that auto-selects appropriate tasks based on your project stage. The planner supports starting from survey, ideation, experiment, publication, or promotion stages while preserving your context.

What is a research brief and why do I need one for task automation?

The planning workflow produces a research_brief.json file and a tasks.json file. These files are generated in the .pipeline/docs and .pipeline directories respectively, providing a repeatable and shareable execution plan for your project.

Do I need to prepare specific schemas before planning a research pipeline?

You do not need to create schemas yourself, but the planner loads and respects existing schemas from the references directory. This ensures the generated research brief and staged tasks are fully contract-compliant before execution begins.

What's the best way to prevent scope creep when generating research tasks?

Yes, you can regenerate tasks for an existing research brief. The planner applies to new projects or when existing briefs and tasks need regeneration, starting from the initial stage to produce a complete execution plan.