What is pipeline-build-dual?

A two-draft business-plan writing step. One draft uses a formal, data-focused style and the other a persuasive, story-focused style, then both are combined into one final plan.

Use it to create a complete business plan covering the business, market, competition, pricing, finances, operations, risks, funding and next steps. It also saves both source drafts for comparison.

It gives the plan both careful structure and a clearer persuasive narrative. The final document is based on the project brief, assumptions, market research, financials and strategy.

pipeline-build-dual — Skill for Claude Code and Codex by danielgap

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add danielgap/openclaw-planitor --skill pipeline-build-dual

Clone the repo

git clone --depth 1 https://github.com/danielgap/openclaw-planitor

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/danielgap/openclaw-planitor/pipeline-build-dual/github.svg)](https://agentmods.dev/skills/danielgap/openclaw-planitor/pipeline-build-dual)

Your own site

<a href="https://agentmods.dev/skills/danielgap/openclaw-planitor/pipeline-build-dual"><img src="https://agentmods.dev/badge/skills/danielgap/openclaw-planitor/pipeline-build-dual/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/danielgap/openclaw-planitor/pipeline-build-dual"><img src="https://agentmods.dev/badge/skills/danielgap/openclaw-planitor/pipeline-build-dual.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,744 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00068	$0.01744
Opus 5	$0.00034	$0.00872
Sonnet 5	$0.00014	$0.00349
Haiku 4.5	$0.00007	$0.00174

Measured 10d ago against content hash cf29e597dd2b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

pipeline-build-dual scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/pipeline-build-dual/SKILL.md · 147 lines

How it starts

The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Pipeline — FASE 6: Build Dual-LLM

Dos LLMs redactan el plan de negocio desde estilos distintos. Planitor sintetiza lo mejor de cada versión en un documento final unificado y profesional.

Cuándo se ejecuta

Después de FASE 5 (Strategy). Cuando STRATEGY.json está completo y JUDGE aún no se ha ejecutado.

Input

Fuente	Ruta
Brief	`projects/{proyecto}/v{n}/BRIEF.json`
Ground Truth	`projects/{proyecto}/v{n}/GROUND-TRUTH.json`
Análisis de mercado	`projects/{proyecto}/v{n}/MARKET-ANALYSIS.json`
Financieros	`projects/{proyecto}/v{n}/FINANCIALS.json`
Estrategia	`projects/{proyecto}/v{n}/STRATEGY.json`

Output

Producto	Ruta
Plan Juez A (analítico)	`projects/{proyecto}/v{n}/build/PLAN-A.md`
Plan Juez B (persuasivo)	`projects/{proyecto}/v{n}/build/PLAN-B.md`
Plan final sintetizado	`projects/{proyecto}/plan-final.md`

Los Dos Jueces

Agente	Modelo	Enfoque
`modelo-a`	`modelo-principal`	Analítico-formal — estructura rigurosa, datos tabulados, lenguaje preciso, formato ejecutivo, referencias numéricas exactas, tono profesional bancario
`modelo-b`	`modelo-secundario`	Persuasivo-narrativo — storytelling del negocio, narrativa de inversión, lenguaje que conecta emocionalmente, presentación que vende la visión, argumentación que convence

Ventaja dual-LLM: Un modelo produce un documento técnicamente impecable; el otro lo hace convincente y memorable. La síntesis produce un plan que es a la vez riguroso y atractivo.

Paso 1: Launch Paralelo

ejecutar como sub-tarea(id=modelo-a, task:
  "Lee skills/pipeline-build-dual/SKILL.md para entender el formato.
   Lee TODOS los artefactos en projects/{proyecto}/v{n}/.
   
   Tu ENFOQUE: analítico-formal.
   - Estructura ejecutiva rigurosa (cada sección con propósito claro)
   - Tablas de datos bien formateadas y numeradas
   - Referencias numéricas exactas (cruzar con artefactos fuente)
   - Lenguaje preciso y técnico donde aplique
   - Formato bancario: resumen ejecutivo → detalle → anexos
   - Sección de riesgos con análisis cuantitativo
   - Cash flow en tabla mensual clara
   - Anti-redundancia estricta: cada dato aparece UNA vez
   - Supuestos no validados marcados con ⚠️
   
   Genera el plan completo en Markdown (12-15 secciones).
   Escríbelo en projects/{proyecto}/v{n}/build/PLAN-A.md"
)

ejecutar como sub-tarea(id=modelo-b, task:
  "Lee skills/pipeline-build-dual/SKILL.md para entender el formato.
   Lee TODOS los artefactos en projects/{proyecto}/v{n}/.
   
   Tu ENFOQUE: persuasivo-narrativo.
   - Narrativa de inversión: por qué este negocio, por qué ahora, por qué este equipo
   - Storytelling en el resumen ejecutivo que enganche desde el primer párrafo
   - Presentar la oportunidad antes que los datos (gancho → evidencia)
   - Lenguaje que conecte: hablar de problemas reales de clientes reales
   - Sección de competencia como historia de diferenciación
   - Financieros como historia de crecimiento (no solo tablas)
   - Cierre con visión de futuro inspiradora
   - Mantener rigor en los datos (no inventar) pero presentarlos con impacto
   - Anti-redundancia: cada dato UNA vez, pero con contexto narrativo
   
   Genera el plan completo en Markdown (12-15 secciones).
   Escríbelo en projects/{proyecto}/v{n}/build/PLAN-B.md"
)

Read the full file on GitHub · 147 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

10d ago First seen · 147 lines · 68 tokens per session scan A cf29e597dd2b

Subscribe to this mod's changes

pipeline-build-dual is a skill published in the GitHub repository danielgap/openclaw-planitor (5 stars, last pushed 4mo ago), licensed MIT. It adds 68 tokens to every session and 1,744 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens