Skip to content

Latest commit

 

History

History
52 lines (35 loc) · 1.58 KB

File metadata and controls

52 lines (35 loc) · 1.58 KB

Governance

This document describes how decisions are made for the Vibe-Coding Prompt Template.

Scope

Governance applies to:

  • Workflow documents (README.md, part*.md, docs/*)
  • Template artifacts (templates/*)
  • Community health files (.github/*)

Roles

Maintainer

  • Reviews and merges pull requests
  • Curates roadmap direction
  • Resolves disputes and final tie-break decisions

Contributor

  • Proposes changes through issues, discussions, and pull requests
  • Helps improve prompts, docs, examples, and workflows

Decision-making model

We use a pragmatic, lightweight model:

  • Small changes: maintainer discretion after normal PR review
  • Significant changes (structure, workflow contract, breaking guidance): discussed first in Discussions or an issue
  • Default approach: seek consensus, but avoid blocking progress indefinitely

Change categories

  • Editorial: typo fixes, clarity improvements, link updates
  • Operational: workflow/action updates, policy docs, checklist updates
  • Structural: major prompt contract or template architecture changes

Structural changes should include:

  • Rationale
  • Migration notes (if behavior changes)
  • Updated references in docs

Release and maintenance cadence

  • Primary cadence: monthly maintenance updates
  • Urgent fixes: shipped as needed (broken links, security clarifications, major regressions)

Conduct and enforcement

Community behavior follows CODE_OF_CONDUCT.md.

Security and sensitive reports

Security issues must follow SECURITY.md and should not be filed as public issues.