governance-workflow

Automates governance workflows and cascade propagation for the tzh-Harness framework.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/huanlongAI/tzh-Harness --skill governance-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: governance-workflow
Source: https://github.com/huanlongAI/tzh-Harness/tree/main/cowork-skills/governance-workflow
Command: npx skills add https://github.com/huanlongAI/tzh-Harness --skill governance-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates governance workflows and lifecycle management across the tzh-Harness ecosystem, enabling consistent ruling creation, spec sign-offs, and cascade updates.

Core Features & Use Cases

  • Ruling creation and log (RULINGS.md) with versioned, auditable entries.
  • Spec sign-off workflow for MIRA, SAAC, CONSEN-SPEC with cascade impact analysis.
  • PROGRESS.json session tracking, Obsidian session memory synchronization, and memory-augmented governance.
  • Cascade verification and cross-repo governance coordination using the cascade_map to ensure downstream consistency.
  • Cross-repo governance event flow and automation from ruling to matrix updates and escalation.

Quick Start

Describe the ruling you want to issue, and I will create a RULINGS.md entry, bump the spec version, and propagate changes across downstream documents.

Frequently Asked Questions about governance-workflow

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

FAQPage Schema
How do I automate governance spec sign-offs and cascade propagation across repositories?

Automate governance spec sign-offs by applying deterministic checks and versioned frontmatter to MIRA, SAAC, and CONSEN-SPEC documents, ensuring downstream cascade consistency through CI validations and a cascade_map.

What is the best way to track governance lifecycle progress and sync session memory?

Track governance lifecycle progress by updating PROGRESS.json and synchronizing Obsidian session memory, which provides memory-augmented governance and auditable event tracking across the workflow.

How do I create an auditable ruling entry with version tracking for governance workflows?

Create an auditable ruling entry by generating a versioned RULINGS.md record with deterministic checks and audit logs, bumping the spec version, and propagating changes across downstream documents automatically.

Does the governance workflow support cross-repo coordination and cascade impact analysis?

Cross-repo governance coordination is supported through cascade verification using a cascade_map, enabling impact analysis for spec sign-offs and ensuring downstream consistency across repositories via CI validations.

Can I use this governance workflow for MIRA and CONSEN-SPEC documents without external dependencies?

Yes, you can apply this governance workflow to MIRA and CONSEN-SPEC documents without external dependencies, as it requires only deterministic checks, versioned frontmatter, and CI validations to ensure lifecycle integrity.

Why do I need versioned frontmatter and audit logs for governance cascade checks?

Versioned frontmatter and audit logs are required for governance cascade checks to maintain deterministic end-to-end lifecycle integrity, ensuring that ruling creations and spec sign-offs are traceable and verifiable across downstream documents.