Documentation Assembly

Consolidate validated findings from Skills 1–7 into docs/model_doc.md.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/gtylee/ModelGAS --skill documentation-assembly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Documentation Assembly
Source: https://github.com/gtylee/ModelGAS/tree/main/modelgas/skills/documentation
Command: npx skills add https://github.com/gtylee/ModelGAS --skill documentation-assembly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill integrates validated findings from governance-focused skills to produce a single, human-readable model documentation artifact that preserves the original intent while embedding evidence and traceability.

Core Features & Use Cases

  • Integrates findings from Skills 1–7 (risk tiering, methodology, ALW, tests, OPM, production controls) into a consistent narrative.
  • Generates docs/model_doc.md and a concise governance summary for reviewers.
  • Maintains traceability by including evidence references and a consolidated unknowns list.

Quick Start

After Skills 1–7 have produced their outputs, run the Documentation Assembly skill to generate the final model documentation.

Frequently Asked Questions about Documentation Assembly

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

FAQPage Schema
How do I consolidate model risk findings into a single governance-ready document?

Model risk findings are consolidated into a single governance-ready document by integrating validated outputs from prior skills, applying a documentation template to produce a traceable model_doc.md file and summary.

What is the best way to maintain traceability across model documentation for an audit?

Traceability for audits is maintained by embedding evidence references and a consolidated unknowns list directly within the generated model documentation, linking final narrative findings back to prior skill outputs.

How do I compile model documentation after completing risk tiering and methodology validation?

Model documentation is compiled by running the assembly process after risk tiering, methodology, and validation skills finish, integrating their outputs into a consistent narrative using the required template.

Do I need a specific documentation template to generate governance-ready model docs?

Yes, a documentation template is required to ensure consistency and traceability when generating governance-ready model docs, structuring the integrated findings into the final model_doc.md artifact.

Can I generate a model documentation summary for reviewers without manual formatting?

A concise documentation summary for reviewers is generated automatically alongside the full model_doc.md, capturing integrated findings, risk tiers, and production controls without manual formatting.

What happens if I run model documentation assembly before prior skill outputs are ready?

Running assembly before prior skill outputs are ready prevents proper integration, as the process requires intermediate risk, methodology, and test findings to embed evidence and ensure traceability.