agentleFS
Sign inStart free
duviolinduviolin/sdd-kit/skills/sdd-constitution/SKILL.md

sdd-constitution

Skill0 starsChanged 54 days agoMITView on GitHub

Use to define or update a project's non-negotiable engineering principles that govern every SDD phase. Auto-use when starting SDD on a project with no constitution.md, or when the user says "princípios", "constituição", "constitution", "padrões do projeto", "regras que valem pra tudo". Creates or updates a project-level constitution.md.

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. monaccode/astromesh-sdd★ 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 repository9 other files it gives its agents.

The file

Create a free account to mount
Files
SKILL.md

sdd-constitution

Cria/atualiza constitution.md na raiz do projeto: os princípios inegociáveis que toda feature herda. É o documento que gateia sdd-requirements, sdd-design, sdd-delivery e sdd-acceptance.

Passos

  1. Ler constitution.md se já existir (documento vivo — atualizar com bump de versão, não recriar).
  2. Levantar os princípios reais: padrões de código/teste, política de erro e segurança, camadas permitidas/proibidas, processo (branch, revisão), restrições de negócio/plataforma. Basear-se em evidência do repo + decisão humana — não inventar regra que o time não segue. Incorporar as guidelines/convenções já existentes no projeto (CONTRIBUTING, guia de estilo, config de lint) — a constituição as torna oficiais e o SDD passa a exigi-las.
  3. Preencher a partir de ${CLAUDE_PLUGIN_ROOT}/sdd/templates/constitution.md. Cada princípio deve ser verificável (dá pra dizer objetivamente se foi violado).
  4. Escrever/atualizar constitution.md na raiz e registrar a versão no histórico.

Regras

  • Um constitution.md por projeto. É prescritivo (o que sempre/nunca fazer), diferente do architecture.md, que é descritivo (o que o sistema é).
  • Só muda por decisão humana explícita, com bump de versão.
  • Mudança aqui pode invalidar specs/planos em aberto — sinalizar quando isso acontecer.
  • Próximo passo natural: sdd-discovery (ou direto sdd-requirements).

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