agentleFS
Sign inStart free
monaccodemonaccode/astromesh-sdd/skills/sdd-constitution/SKILL.md

sdd-constitution

Skill0 starsChanged 29 days agoApache-2.0View on GitHub

Use when a project has no specs/constitution.md yet, or the user wants to set or change project-wide engineering principles that every SDD spec and plan must respect.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. duviolin/sdd-kit★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before anything else, read these if they exist.

    line 13
  2. Very specific:

    Write every artifact in language.

    line 24
  3. Distinctive:

    Read the README, build/package files, CI config, lint and test setup, and a few representative source files.

    line 29
  4. Distinctive:

    Write 5–9 principles. Each one:

    line 35
  5. Very specific:

    Ask the user which principles they want to add or drop.

    line 43
  6. Very specific:

    Write <specs_dir>/constitution.md from the template.

    line 48

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

SDD — Constitution

The constitution is the short list of principles every spec, plan and task in this repo must respect. It is written once and amended rarely, on purpose.

Step 0 — Load project settings

Before anything else, read these if they exist. Missing files are normal; use the defaults.

  1. .sdd/config.yaml in the project, else ~/.sdd/config.yaml. Defaults: specs_dir: specs, language: en, ids: {requirement: REQ, task: T}, gates: [specify, plan, tasks], verify_command: "", phases: [constitution, specify, plan, tasks, implement, verify].
  2. Template: .sdd/templates/constitution.md, else ~/.sdd/templates/constitution.md, else templates/constitution.md next to this file.
  3. Extra rules: .sdd/rules/all.md and .sdd/rules/constitution.md (project, then global). They add to this skill; when they conflict with it, they win.

Write every artifact in language. Use the configured ID prefixes everywhere this skill says REQ or T.

Step 1 — Learn the project as it is

Read the README, build/package files, CI config, lint and test setup, and a few representative source files. Record what you observed, not what you would prefer: language and runtime, the real test command, the real lint/format command.

Step 2 — Draft principles

Write 5–9 principles. Each one:

  • is testable — a reviewer can answer yes or no to "does this change respect it?" ("Public functions have type hints", not "Write clean code");
  • carries a one-line Why;
  • reflects this project, not generic advice. If the codebase already follows a rule consistently, it is a principle; if it does not, ask the user before adding it.

Ask the user which principles they want to add or drop. Suggest the detected test command as verify_command for .sdd/config.yaml.

Step 3 — Write it

Write <specs_dir>/constitution.md from the template. If the file already exists, do not overwrite it: show the proposed changes as a diff, and on approval apply them and add a row to its Amendments table.

Show the user the result. Specs and plans written from now on must check themselves against it.

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.

Check your setup, free