agentleFS
nota-dawnota-daw/nota/.claude/skills/speckit-constitution/SKILL.md

speckit-constitution

Skill542 starsChanged yesterdayAGPL-3.0View on GitHub

Create or update the project constitution from interactive or provided principle inputs.

132 other projects use a version of this, 111 of them edited; 98 of 111 edited versions we compared changed its rules; 7 new projects in the last 4 weeks, against 11 the 4 before.

How people change it

98 of 111 edited versions changed its rules, and some changes recur.

Of the 111 edited versions we compared: 13 keep every rule, 98 made changes of their own.

Rules people drop

  1. If the YAML cannot be parsed or is invalid, do not skip silently: tell the user that .specify/extensions.yml could not be read (include the parser error) and that no hooks were checked, including any mandatory (optional: false) hooks registered there, …dropped by 97 of 98
  2. Run .specify/scripts/bash/resolve-template.sh constitution-template --json from the repository root and parse TEMPLATE_CONTENT as the active template.dropped by 79 of 98
  3. If it fails, stop and report the resolution error; do not continue with only one contributing template layer.dropped by 79 of 98
  4. If .specify/memory/constitution.md exists, load it as the source of current project-specific values and amendments. Preserve information that is still applicable when applying the newly resolved scaffold.dropped by 79 of 98
  5. If it does not exist, use the resolved template as the initial document.dropped by 79 of 98
  6. Do not write back to any versioned template layer.dropped by 79 of 98
  7. Write only .specify/memory/constitution.md; do not create or modify template source files.dropped by 79 of 98
  8. If the input includes feature implementation, code generation, refactoring, building, or deployment requests, you MUST NOT execute them. Extract them as deferred intents instead.dropped by 65 of 98

Rules people add

  1. If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normallyadded by 93 of 98
  2. Do not create a new template; always operate on the existing .specify/memory/constitution.md file.added by 78 of 98
  3. Note: If .specify/memory/constitution.md does not exist yet, it should have been initialized from .specify/templates/constitution-template.md during project setup. If it's missing, copy the template first.added by 76 of 98
  4. Read .specify/templates/plan-template.md and ensure any "Constitution Check" or rules align with updated principles.added by 69 of 98
  5. Read .specify/templates/spec-template.md for scope/requirements alignment—update if constitution adds/removes mandatory sections or constraints.added by 69 of 98
  6. Read .specify/templates/tasks-template.md and ensure task categorization reflects new or removed principle-driven task types (e.g., observability, versioning, testing discipline).added by 69 of 98
  7. Read any runtime guidance docs (e.g., README.md, docs/quickstart.md, or agent-specific guidance files if present). Update references to principles changed.added by 69 of 98
  8. Read each command file in .specify/templates/commands/*.md (including this one) to verify no outdated references (agent-specific names like CLAUDE only) remain when generic guidance is required.added by 58 of 98

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Cooling: 7 new projects took it in the last 4 weeks, 0.6× the 4 weeks before.

Week of Sep 20: 3 new projectsWeek of Sep 27: 3 new projectsWeek of Oct 4: 2 new projectsWeek of Oct 11: 3 new projectsWeek of Oct 18: 1 new projectWeek of Oct 25: 2 new projectsWeek of Nov 1: 2 new projectsWeek of Nov 8: 2 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read.

Most recently taken up by

Used with

Projects with it also use speckit-agent-context-update, speckit-git-commit and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Microsoft AzureSkill

    speckit-agent-context-update

    Refresh the managed Spec Kit section in coding agent context file(s)

    Also in 13 projects that use this

  • Sorcha-PlatformSkill

    speckit-git-commit

    Auto-commit changes after a Spec Kit command completes

    Also in 35 projects that use this

  • Sorcha-PlatformSkill

    speckit-git-feature

    Create a feature branch with sequential or timestamp numbering

    Also in 35 projects that use this

  • patterson-agentsSkill

    speckit-baseline

    Generate feature specifications by analyzing existing source code.

    Also in 3 projects that use this

  • patterson-agentsSkill

    claude-command-converter

    Convert Claude Code commands (.claude/commands/*.md) to standard Agent Skills (skills/*/SKILL.md). Use when migrating slash commands to portable skill format, creating skills from existing commands, or standardizing command definitions across AI runtimes.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    agentic-workflows

    Route gh-aw workflow design/create/debug/upgrade requests to the right prompts.

    Also in 3 projects that use this

  • +3 more from Sorcha-Platform

The file

Show its rules and text

We split this skill into the rules it gives an agent

29 rules. 10 are common, 5 are distinctive, and 14 are very specific to this project.

  • 10

    Common

    Most of the 112 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 14

    Very specific

    Tied to their project's names, files or tools. Probably skip.

Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 112 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.