regulatory-templates-gate3

Generate a Django/Jinja2 .tpl template and .tpl.docs from Gate 1-2 validations.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/withmartian-sandbox/ghrc-x-3126672651424eddb640ecc81321a665 --skill regulatory-templates-gate3-withmartian-sandbox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: regulatory-templates-gate3
Source: https://github.com/withmartian-sandbox/ghrc-x-3126672651424eddb640ecc81321a665/tree/main/finops-team/skills/regulatory-templates-gate3
Command: npx skills add https://github.com/withmartian-sandbox/ghrc-x-3126672651424eddb640ecc81321a665 --skill regulatory-templates-gate3-withmartian-sandbox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gate 3 generates the final production-ready .tpl template by applying Gates 1-2 validations, ensuring all fields and transformations are complete, and preventing drift into production artifacts.

Core Features & Use Cases

  • Production-ready template generation using finops-automation after Gate 2 passes.
  • Outputs two artifacts: the .tpl and the .tpl.docs for documentation.
  • Enforces 100% mandatory fields and preserves validated mappings to avoid drift.

Quick Start

Run Gate 3 after Gate 2 passes to produce the final template artifacts ready for deployment.

Frequently Asked Questions about regulatory-templates-gate3

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

FAQPage Schema
How do I generate production-ready Django templates from validated field mappings?

To generate production-ready Django templates, run an automated agent flow that applies Gate 1-2 validations to all field mappings, enforcing 100% mandatory fields and outputting a clean .tpl file.

What is a Gate 3 validation template in regulatory compliance automation?

Gate 3 template generation is the process of converting Gate 1-2 validated field mappings into a final production-grade Jinja2 .tpl template, preventing configuration drift into production artifacts.

Can I use Jinja2 templates for regulatory compliance if Gate 2 has not passed?

No, Gate 3 template generation only applies when Gate 2 has successfully passed. It requires completed field mappings and finops-automation to produce the final ready-for-production template.

How do I document field mappings and transformations for production templates?

You document field mappings and transformations by generating a separate .tpl.docs file alongside the clean .tpl template, containing full mappings and validation details for production artifacts.

What's the best way to prevent template drift in finops-automation workflows?

The best way to prevent template drift is to enforce 100% mandatory fields and preserve validated mappings during Gate 3 generation, ensuring all transformations are complete before deployment.

Do I need finops-automation to generate regulatory compliance templates?

Yes, finops-automation is required for Gate 3 production-ready template generation. It drives the automated agent flow that applies Gate 1-2 validations and outputs the .tpl and .tpl.docs artifacts.