pipeline-build-dual

Coordinate dual-LLM outputs to generate a unified business plan from JSON inputs.

4|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/danielgap/openclaw-planitor --skill pipeline-build-dual
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pipeline-build-dual
Source: https://github.com/danielgap/openclaw-planitor/tree/main/skills/pipeline-build-dual
Command: npx skills add https://github.com/danielgap/openclaw-planitor --skill pipeline-build-dual

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates dual-LLM workflows to produce a unified business plan that combines analytical rigor with persuasive narrative.

Core Features & Use Cases

  • Dual-LLM orchestration: runs two distinct prompts (analytical and creative) to generate complementary sections of the plan.
  • Synthesis & provenance: Planitor merges both outputs into a single coherent final document with source-truth checks.
  • Artifact generation: outputs PLAN-A.md, PLAN-B.md, and plan-final.md from inputs BRIEF.json, GROUND-TRUTH.json, MARKET-ANALYSIS.json, FINANCIALS.json, and STRATEGY.json.
  • Validation & guardrails: cross-checks figures against sources and flags unvalidated assumptions.

Quick Start

Generate the final unified business plan from inputs available after Phase 5 using the dual-LLM workflow.

Frequently Asked Questions about pipeline-build-dual

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

FAQPage Schema
How do I synthesize dual-LLM outputs into a cohesive final business plan?

To synthesize dual-LLM outputs into a cohesive final business plan, coordinate analytical and persuasive prompts to generate complementary sections. Merge these outputs with source-truth checks and strict anti-redundancy to ensure alignment across your final document.

What is dual-LLM orchestration for business planning?

Dual-LLM orchestration for business planning runs two distinct analytical and creative prompts to generate complementary sections. It merges these outputs into a single coherent final document while applying provenance checks to validate source data.

How do I generate a unified business plan from JSON source files?

Generate a unified business plan by assembling BRIEF.json, GROUND-TRUTH.json, MARKET-ANALYSIS.json, FINANCIALS.json, and STRATEGY.json. The dual-LLM workflow processes these inputs to output PLAN-A.md, PLAN-B.md, and the merged plan-final.md.

Does generating a final business plan require provenance checks?

Generating a final business plan requires provenance checks and validation guardrails to cross-check figures against your source JSON files. This strict anti-redundancy process flags unvalidated assumptions to ensure source-truth alignment.

When should I use dual-LLM synthesis for strategy documentation?

Use dual-LLM synthesis for strategy documentation when a project requires combining analytical rigor with persuasive narrative. It is applicable during later phases to merge separate analytical and creative plan drafts into one cohesive final strategy.

What's the best way to prevent unvalidated assumptions in a final business plan?

The best way to prevent unvalidated assumptions in a final business plan is applying validation guardrails during dual-LLM synthesis. Cross-check figures against GROUND-TRUTH.json and FINANCIALS.json to flag inconsistencies and enforce strict anti-redundancy.