skills.rest
lilmuckers
lilmuckersCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

assumption-governance

Document project and task assumptions in PRs and GitHub wiki pages.

Updated Apr 1, 2026
Search Tags:#documentation#governance#assumptions#wiki#project-management#pull-requests#team-workflow
One-click install
npx skills add https://github.com/lilmuckers/agentic-team-plugin --skill assumption-governance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: assumption-governance
Source: https://github.com/lilmuckers/agentic-team-plugin/tree/main/skills/assumption-governance
Command: npx skills add https://github.com/lilmuckers/agentic-team-plugin --skill assumption-governance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Govern who may make assumptions and how they must be documented. Use when clarifying project-level versus task-local assumptions, recording rationale, and ensuring assumptions appear in pull requests and the GitHub wiki where appropriate.

Core Features & Use Cases

  • Ownership split
  • Documentation rule
  • Disagreement handling

Quick Start

Document the current project-level assumptions for the upcoming sprint in the PR description and the project wiki.

Frequently Asked Questions about assumption-governance

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

FAQPage Schema
How do I document project assumptions in pull requests and wikis?▼

Document project assumptions in pull requests and wikis by defining ownership rules and capturing rationale directly in the PR description and wiki pages to ensure traceability and reduce team miscommunication.

What is the best way to govern who can declare project-level assumptions?▼

Governing who can declare project-level assumptions involves setting an ownership split that defines authority, applying documentation rules, and establishing clear disagreement handling procedures for the team workflow.

How do I separate project-level assumptions from task-local assumptions?▼

Separating project-level assumptions from task-local assumptions requires clarifying the scope of the decision, documenting the reasoning, and ensuring visibility in the relevant GitHub wiki pages and pull requests.

Can I use assumption governance for design reviews and sprint planning?▼

Assumption governance applies to design reviews and sprint planning by capturing the reasoning behind decisions, recording rationale in PRs, and ensuring assumptions are visible and traceable across the project wiki.

Why does my team have miscommunication during pull requests?▼

Miscommunication during pull requests often happens when project assumptions are undocumented; clarifying and codifying these assumptions in PR descriptions and wiki pages ensures visibility and reduces disagreements.

When should I not use an assumption governance workflow?▼

You should avoid using an assumption governance workflow for trivial, task-local decisions that do not require traceability or formal rationale recording in project wikis and pull requests.

Related Skills

Explore More Content & Communication Skills→
pradeepmoulipradeepmouli
2

speckit-workflows.baseline

Execute a script to generate baseline-spec.md and current-state.md from JSON output.

Community
Advanced
danilonovaisvdanilonovaisv
1

github-project-management

Coordinate GitHub issues, boards, and sprint planning across repositories.

Community
Advanced
BeastAyyGBeastAyyG
1

code-review-checklist

Generate a structured code-review checklist for pull requests.

Community
Intermediate
agnaldo4jagnaldo4j
1

wiki-maintenance

Map code changes to GitHub wiki pages and enforce update workflows.

Community
Advanced