CreateGovernanceDoc

Name: CreateGovernanceDoc
Availability: InStock
Author: fnoritomi

Generates Markdown templates for documenting Vibe Coding, Architecture, and Refactoring Safety under docs/governance/.

Updated Aug 23, 2026

Search Tags:#architecture #templates #documentation #markdown #refactoring #governance #workflows

Ready to run

npx skills add https://github.com/fnoritomi/tabulador-dados-abertos --skill creategovernancedoc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: CreateGovernanceDoc
Source: https://github.com/fnoritomi/tabulador-dados-abertos/tree/main/.agent/skills/create-governance-doc
Command: npx skills add https://github.com/fnoritomi/tabulador-dados-abertos --skill creategovernancedoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create comprehensive governance documentation to guide future AI-driven refactoring efforts without modifying source code.

Core Features & Use Cases

Defines governance document types (Vibe Coding Guide, Architecture Decisions, Refactoring Safety Net) and their file paths.
Provides structured templates and workflows to standardize governance across projects.
Enables automated generation of Markdown governance docs under docs/governance/ for consistent documentation.

Quick Start

Run the governance doc generator to create:

docs/governance/vibe-coding.md
docs/governance/architecture.md
docs/governance/refactoring-safety.md

Frequently Asked Questions about CreateGovernanceDoc

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

FAQPage Schema

What is a governance document for refactoring and when do I need one?▼

Yes, you can standardize architecture and refactoring documentation by generating Markdown templates under a docs/governance/ directory. This approach standardizes workflows for coding philosophy, architectural decisions, and refactoring safety across your project.

How do I generate Markdown templates for architecture and refactoring safety?▼

You can generate standardized Markdown governance templates by running a documentation generator that creates files like vibe-coding.md, architecture.md, and refactoring-safety.md under the docs/governance/ directory. This establishes structured workflows for your project.

Does this governance documentation approach modify my existing source code?▼

No, creating governance documentation does not modify your existing source code. It strictly produces Markdown templates with explicit file paths under docs/governance/ to guide future AI-driven refactoring efforts safely from the outside.

What file structure is used for Vibe Coding and architecture decision records?▼

The file structure uses a docs/governance/ directory containing specific Markdown files: vibe-coding.md for coding philosophy, architecture.md for architectural decisions, and refactoring-safety.md for safety workflows.

Can I use these governance templates to standardize workflows across multiple projects?▼

Yes, the governance templates are designed to standardize workflows across multiple projects. By defining consistent document types and file paths for coding philosophy and refactoring safety, you can automate and replicate governance documentation generation.