agentleFS
neal-kyleneal-kyle/cosmion/.claude/skills/speckit-constitution/SKILL.md

speckit-constitution

Skill2 starsChanged 31 days agoMITView on GitHub

Create or update the project constitution.

133 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use speckit-agent-context-update, speckit-baseline and 5 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

  • 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

  • arkanSkill

    review-animations

    Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.

    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

  • VercelSkill

    emil-design-eng

    This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 131 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If an instruction could be either constitution content or a non-governance intent, ask for clarification before making changes.

    line 32
  2. Very specific:

    After updating the constitution, list each deferred intent in a Next Actions section with an appropriate follow-up Spec Kit command, such …

    line 34
  3. Very specific:

    Create or update the project constitution and store it in .specify/memory/constitution.md.

    line 41

“Common” is measured: kept by at least 6 in 10 of the 131 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Speckit Constitution Skill

User Input

$ARGUMENTS

Scope Guard

This command's own work is limited to creating or updating the project constitution and propagating constitution-driven changes to dependent Spec Kit artifacts.

  • Classify every part of the user input as constitution content or a separate non-governance intent. Feature implementation, code generation, refactoring, build, and deployment requests are examples of non-governance intents.
  • You MUST NOT execute any non-governance intent. Defer each one to Next Actions.
  • You MUST NOT create, modify, or delete application source files or other artifacts unrelated to the constitution workflow.
  • If an instruction could be either constitution content or a non-governance intent, ask for clarification before making changes.
  • After updating the constitution, list each deferred intent in a Next Actions section with an appropriate follow-up Spec Kit command, such as /speckit-specify, but do not invoke it.
  • Omit Next Actions when there are no non-governance intents.

Outline

  1. Create or update the project constitution and store it in .specify/memory/constitution.md.
    • Project name, guiding principles, non-negotiable rules
    • Derive from user input and existing repo context (README, docs)

Download now (ZIP)

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.