agentsclimarketplace

Spec constitution

Skill h3y6e/spec-skills/skills/spec-constitution

Agent Skills for Spec-Driven Development

Install
npx -y skills add h3y6e/spec-skills --skill spec-constitution

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when a team wants to create or update specs/constitution.md to define durable principles that govern spec-skills runs, especially when starting a new workflow, revising shared governance for the spec-driven phases, or deciding what belongs in constitutional rules versus lower-level docs.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.6 KB, as published. Nobody here has run it

Constitution Skill

Purpose

Create or update specs/constitution.md when the team wants shared rules that spec-skills should apply during their own workflow.

Input

  • User-provided project rules (via prompt or conversation)
  • Existing specs/constitution.md when present

Output

  • specs/constitution.md

Steps

  1. Determine language.
    • Use the existing specs/constitution.md frontmatter value if present
    • Otherwise infer from the user's own message (never from this SKILL.md or system instructions)
    • If still unknown, ask the user before proceeding
    • Conduct all subsequent interaction in this language
  2. Read specs/constitution.md; if missing, initialize from references/constitution-template.md.
  3. Keep the document structure aligned with references/constitution-template.md.
    • Do not invent additional top-level sections unless the user explicitly requests them
  4. Update Core Principles based on user-provided rules.
    • Ask the user if no rules were provided
    • Keep only stable, project-wide principles here when they are meant to guide spec-skills phases
    • Prefer durable decision principles over implementation details
    • Do not copy concrete coding conventions, framework APIs, directory names, commands, or tool-specific rules into the constitution unless the user explicitly wants to elevate them into permanent governance
    • Even when the user requests elevation, include such a rule only if it is intended to remain valid across features and over time; otherwise keep it in lower-level docs
    • The constitution should govern spec-skills behavior and outputs, not become a general repository policy file by default
    • Apply YAGNI: if a principle is speculative or addresses a scenario that hasn't occurred, omit it. Constitutions grow stale when they accumulate hypothetical rules.
  5. Add variable project rules only when the user specifies them.
    • Fold them into existing principles when possible
    • If a rule belongs more naturally in AGENTS.md, contribution docs, or feature documents, keep it out of the constitution and preserve that separation of responsibility explicitly
  6. Update frontmatter.
    • Required keys: language, summary
  7. If updating an existing constitution, verify consistency with existing feature documents.
    • Check specs/{feature}/spec.md and plan.md
    • Preserve consistency by removing contradictions, not by copying feature-level implementation detail into the constitution
    • Skip this step when no feature documents exist
  8. Perform final review and keep the file within 150 lines.
    • Remove repetition
    • Simplify wording
    • Resolve contradictions
  9. In the completion message, suggest the next step.
    • New feature: spec-specify
    • Existing feature update: spec-specify for the target spec.md

Success Criteria

  • Constitution reflects the shared rules that spec-skills should use during the workflow.
  • Constitution stays at the level of durable governing principles rather than duplicating lower-level implementation guidance.
  • Frontmatter values are valid and complete.
  • Related feature documents stay consistent.

Completion Guidance

  • Next recommended step: spec-specify
  • Include the target feature and next file path in the response

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.