spec-file-governance

Create and maintain a project-root SPEC.md that captures main intent and project definition while referring out to authoritative wiki pages. Use when bootstrapping or updating a project repo so there

SKILL.md

GitHub

SPEC.md governance

Rule

Every project should have a root SPEC.md maintained by Spec.

Purpose of SPEC.md

SPEC.md is the in-repo entrypoint for project intent. It should:

  • state the main intent of the project
  • summarize the core project definition
  • link to the authoritative wiki pages for deeper product, solution, and architecture material
  • stay aligned with the current project direction

What belongs in SPEC.md

  • project purpose
  • intended users or operators
  • scope summary
  • non-goals summary
  • links to key wiki pages
  • current high-level delivery intent

What does not belong only in SPEC.md

Do not treat SPEC.md as the sole home for deep design truth. Detailed product definition, architecture, and evolving assumptions should still live in the wiki.

Ownership

  • Spec creates and maintains SPEC.md
  • Spec keeps it aligned with wiki truth and merged code changes

Related in other

limits-colimits

Context management for Claude Code. Hooks maintain state via ledgers and handoffs. MCP execution without context polluti...

by parcadei
3,392

ddttom-allaboutv2-claude-skills-block-collection-and-party

The Block Collection and Block Party are repositories for existing AEM blocks, build tools, code snippets, integration p...

by mattnigh
20

nodnarbnitram-claude-code-extensions-claude-skills-esphome-confi

This skill should be used when the user asks to "create an esphome config", "set up an esp32 device", "configure esphome...

by mattnigh
20