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

spec-file-governance

Create and maintain a project-root SPEC.md linking to wiki pages.

Updated Apr 1, 2026
Search Tags:#documentation#onboarding#repository#governance#spec#wiki#spec.md
One-click install
npx skills add https://github.com/lilmuckers/agentic-team-plugin --skill spec-file-governance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-file-governance
Source: https://github.com/lilmuckers/agentic-team-plugin/tree/main/skills/spec-file-governance
Command: npx skills add https://github.com/lilmuckers/agentic-team-plugin --skill spec-file-governance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SPEC.md at the project root serves as the in-repo entrypoint for project intent, consolidating purpose, scope, and alignment with wiki documentation. It provides a concise reference for onboarding, governance, and future changes.

Core Features & Use Cases

  • Centralizes the project intent in a single SPEC.md at the root.
  • Links to authoritative wiki pages for deeper product, solution, and architecture material.
  • Supports onboarding and governance by capturing purpose, users, scope, non-goals, and delivery intent.

Quick Start

Create or update SPEC.md at the project root to reflect the current project intent and link to the wiki documentation.

Frequently Asked Questions about spec-file-governance

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

FAQPage Schema
How do I create a project specification document for repository onboarding?▼

Create a project specification document by generating a SPEC.md at the repository root. This file captures the project purpose, intended users, scope, non-goals, and current delivery intent to centralize onboarding and governance.

What is the best way to link a repository's root documentation to a GitHub wiki?▼

Linking repository root documentation to a GitHub wiki is done by creating a SPEC.md file that serves as an entrypoint, referencing authoritative wiki pages for deeper architecture and solution material while keeping root intent concise.

How do I maintain project governance documentation as delivery intent changes?▼

Maintain project governance documentation by updating the SPEC.md file in the repository root. It consolidates the current high-level delivery intent, scope, and non-goals, ensuring ongoing alignment as the project evolves.

Does a SPEC.md file replace detailed product and architecture documentation?▼

A SPEC.md file does not replace detailed documentation. It serves as a concise in-repo specification entrypoint that links out to authoritative wiki pages where the fuller product, solution, and architecture material resides.

What should be included in a repository specification for project alignment?▼

A repository specification for project alignment should include the project purpose, intended users, scope, non-goals, links to key wiki pages, and current high-level delivery intent, all maintained within a root SPEC.md file.

Related Skills

Explore More Software Engineering Skills→
agentteamlandagentteamland

wiki

Initialize and maintain cross-referenced wiki pages from ingested sources.

Official
Advanced
jac007xjac007x

org-roster-refresh

Parse roster requests, pull HR exports, and deliver delta-aware Excel or summary outputs.

Community
Advanced
Chronote-ggChronote-gg
4

Docs Authoring Workflow (OpenCode wrapper)

Automates Git/Markdown-based public documentation creation and updates for software products.

Official
Intermediate
arbiterForgearbiterForge
139

decision-lifecycle

Author and track numbered, dated architecture decision records with user attribution.

Official
Advanced