dbm-publish

Assembles the rewritten DBM package and generates QA artifacts from approved section outputs.

Updated Aug 27, 2026

Search Tags:#validation #qa #publication #assembly #open-items #dbm-publish #knowledge-coverage

Ready to run

npx skills add https://github.com/sgttomas/chirality-piping --skill dbm-publish

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dbm-publish
Source: https://github.com/sgttomas/chirality-piping/tree/main/skills/dbm-publish
Command: npx skills add https://github.com/sgttomas/chirality-piping --skill dbm-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Assembling the full rewritten DBM package from approved section outputs and generating package QA artifacts is essential to publish-ready delivery and governance compliance.

Core Features & Use Cases

Deterministic assembly of the DBM package from approved section outputs.
Generation of package QA artifacts including Publication_Content_Adequacy.md (FULL_ENGINEERING_DBM), Publication_Readiness.md, and Rerun_Recommendations.csv.
Post-authoring concordance review is handled separately by dbm-postauthor-concordance.
Validation that all outputs reside inside the immutable package snapshot and adhere to tool policy.

Quick Start

Run the dbm-publish skill after the section outputs exist to assemble the package and generate readiness artifacts.

Frequently Asked Questions about dbm-publish

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

FAQPage Schema

How do I assemble a rewritten DBM package from approved section outputs?▼

To assemble a rewritten DBM package, you need deterministic tooling that integrates approved section outputs into an immutable package snapshot. The process ensures all components are correctly aggregated and validated before final publication.

What is DBM publication readiness validation?▼

DBM publication readiness validation is the process of generating quality assurance artifacts, specifically Publication_Readiness.md and Publication_Content_Adequacy.md. It verifies that the assembled package meets governance compliance and content adequacy standards before release.

How do I generate package QA artifacts for a FULL_ENGINEERING_DBM publication?▼

You generate package QA artifacts by applying deterministic assembly rules to the approved section outputs. This produces Publication_Content_Adequacy.md, Publication_Readiness.md, and Rerun_Recommendations.csv to confirm the FULL_ENGINEERING_DBM package is ready.

When do I need to run a DBM package assembly and QA skill?▼

You need to run DBM package assembly and QA when section outputs exist and require integration into a publish-ready format. It is essential for enforcing deterministic tooling boundaries and ensuring all outputs reside inside the immutable package snapshot.

Does DBM publication assembly handle post-authoring concordance review?▼

DBM publication assembly does not handle post-authoring concordance review. That process is managed separately by a dedicated concordance skill, while publication assembly focuses strictly on package generation and readiness artifact creation.

What are the limitations of deterministic DBM package assembly?▼

The limitations of deterministic DBM package assembly include strict dependencies on pre-existing approved section outputs and mandatory adherence to tool policy. All outputs must be written inside the immutable package snapshot, preventing any external file modifications.