bp-doc-exporter

Generates final RFC, bug report, and audit documents from templates and persisted intermediates.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/nico0695/ai-tools --skill bp-doc-exporter-nico0695
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bp-doc-exporter
Source: https://github.com/nico0695/ai-tools/tree/main/sdd/blueprint-harness/skills/bp-doc-exporter
Command: npx skills add https://github.com/nico0695/ai-tools --skill bp-doc-exporter-nico0695

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? In a multi-phase blueprint workflow, analysis results live scattered across intermediate files and state records. This Skill consolidates those persisted intermediates into a single final document (RFC, bug report, or audit) written from a user-owned template, and manages the document's digest status lifecycle. ## Core Features & Use Cases - Template-Based Export: Fills only the existing sections of a user-owned template in bp-workspace/templates/ with content sourced exclusively from the objective's intermediates (interview notes, analysis, alternatives) and recorded decisions. - Digest Status Management: Updates only the digest status line of an existing final artifact (draft to approved, approved to handed-off, or superseded) when the orchestrator confirms a checkpoint, leaving the body untouched. - Strict Write Boundary: Writes only the final artifacts it owns (ideas/rfc-{slug}.md, bugs/bug-{slug}.md, audits/audit-{slug}.md) and returns state mutations instead of touching state or index files. - Use Case: After an orchestrated analysis phase completes, the orchestrator delegates the export phase to this worker, which produces a word-budget-compliant RFC with every claim classified as fact, inference, or unknown, and recommends an artifact_approval checkpoint. ## Quick Start Delegate the export phase to bp-doc-exporter with an envelope specifying the objective, artifact type, template path, and intermediate paths so it writes the final document into bp-workspace.

Frequently Asked Questions about bp-doc-exporter

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

FAQPage Schema
How do I generate a final RFC document from analysis intermediates?▼

Delegate the export phase with an envelope naming the objective, artifact type, template path, and intermediate paths. The worker fills the template's existing sections from interview notes, analysis, and alternatives, then writes the RFC with a draft digest status.

How does the artifact digest status lifecycle work?▼

Exports start as draft, except audits which are born approved. The update-status mode transitions draft to approved after artifact approval, approved to handed-off after handoff, or to superseded when replaced, changing only the digest status and updated fields.

Can this worker modify state.yaml or index.yaml files?▼

No. The worker never writes state, index, intermediates, or templates. It returns state_mutations in its result envelope so the orchestrator applies the artifacts{} update itself.

What happens when a template section has no source content?▼

The section is filled with "Not established" rather than invented content, and the result is marked partial with the unfilled sections listed. Missing templates or required intermediates produce a blocked result naming the missing file.

What are the limitations of the export worker?▼

It cannot re-analyze the repository, read repo files, invent sections or findings, or infer bug severity, which must come from the orchestrator's envelope. It writes only its three owned final-artifact paths inside bp-workspace.