speckit-constitution

Create or update project governing principles and development guidelines. Use at project start to establish code quality, testing standards, and architectural constraints that guide all development.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./bundled/skills/speckit-constitution/SKILL.md

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, actionable template-filling workflow with explicit validation before a destructive overwrite and clear propagation steps. It is concise and concrete, falling short of top marks only on missing error-recovery feedback loops and the lack of a worked example.

Suggestions

Add an explicit feedback loop after step 6 validation: "If validation fails, fix the issues and re-run validation before proceeding to step 7."

Include a short worked example showing a placeholder token before and after substitution (e.g., [PROJECT_NAME] -> "AcmeAPI") to make the template-filling step copy-paste concrete.

Specify the exact template-copy action (e.g., `cp .specify/templates/constitution-template.md .specify/memory/constitution.md`) so the fallback path is executable rather than described.

Dimension	Reasoning	Score
Conciseness	The body is dense and task-specific with little explanation of concepts Claude already knows; only minor padding in the formatting notes ("Wrap long rationale lines... but do not hard enforce") keeps it from a 5.	4 / 5
Actionability	Provides concrete file paths, placeholder format, explicit MAJOR/MINOR/PATCH versioning rules, and a defined Sync Impact Report structure; minor gaps include no example of a filled constitution and no exact copy command for the template.	4 / 5
Workflow Clarity	An explicit 8-step sequence with a validation step (step 6) preceding the destructive overwrite (step 7) and batch propagation (step 4); not a 5 because there is no explicit "if validation fails, fix and re-run" feedback loop.	4 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ all absent) and the self-contained body is well-organized into clear sections; good structure with no nested references, though the absence of any external reference files means it does not reach the one-level-deep reference pattern of a 5.	4 / 5
	Total	16 / 20 Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly states what the skill does and when to use it in third person, with several concrete capability areas and a clear niche. It falls just short of top marks due to narrower trigger coverage and categorical rather than fully concrete action wording.

Suggestions

Add broader trigger phrases such as "Use when establishing or amending a project constitution, principles, or coding standards" to cover non-start amendment scenarios.

Include synonyms like "constitution" and "project principles" that users would naturally say.

Sharpen the action verbs from categorical areas ("establish code quality, testing standards") to concrete operations ("draft, version, and propagate governing principles").

Dimension	Reasoning	Score
Specificity	Names the domain ("governing principles and development guidelines") and lists several concrete areas ("code quality, testing standards, and architectural constraints that guide all development"); not a 5 because the actions are categorical rather than a comprehensive set of concrete operations.	4 / 5
Completeness	Explicitly answers both what (create/update governing principles and dev guidelines) and when ("Use at project start to establish..."); not a 5 because the "when" is narrow (only project start) and lacks broader amendment-trigger phrases.	4 / 5
Trigger Term Quality	Includes natural phrases like "Use at project start", "governing principles", "code quality", and "testing standards", but misses common synonyms a user would say such as "constitution" or "set project standards".	4 / 5
Distinctiveness Conflict Risk	The governance/constitution niche ("governing principles", "architectural constraints") is mostly distinct with only minor overlap risk against generic guidelines skills.	4 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/speckit-constitution/SKILL.md
Commit: ddcaa2a

Reviewed: 14 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.