How do I install the Align Specs skill?

Run npx skillmds@latest add petar-djukic/align-specs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Align Specs safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Align Specs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Align Specs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Align Specs?

petar-djukic (@petar-djukic) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Align Specs by petar-djukic — Agent Skill

Name: Align Specs
Author: petar-djukic

File contents

align-specs command

Apply this command workflow. Treat any text after its invocation as the command input.

Command: Align Specs

Read docs/constitutions/design.yaml first and hold it as the authority for the rest of this session.

1. Inventory

Find all specification files in the project:

docs/VISION.yaml
docs/ARCHITECTURE.yaml
docs/SPECIFICATIONS.yaml (if present)
docs/road-map.yaml (if present)
docs/specs/product-requirements/prd*.yaml
docs/specs/use-cases/rel*.yaml
docs/specs/test-suites/test-rel*.yaml
docs/engineering/eng*.yaml

List every file found. Skip any that do not exist.

2. Align Each File

For each file, read it, then apply the constitution's format rules for that document type:

Required fields: Add any field that the constitution schema lists as required but is absent. Use a short placeholder value — do not invent content. Mark placeholders clearly (e.g. # TODO: fill in).

Field names: Rename any field whose key does not match the schema exactly.

Style: Apply the style rules from the constitution — active voice, present tense, remove forbidden terms, no bold in prose paragraphs, no horizontal rules. Do not rewrite substance; fix only what violates a rule.

Naming conventions: Check each file's name against the naming_conventions block in the constitution (e.g. prd[NNN]-[feature-name].yaml, rel[NN].[N]-uc[NNN]-[short-name].yaml). Rename the file if it does not match. Update any cross-references in other files that point to the old name.

Traceability: Apply the traceability_invariants block (T1–T5) from the constitution. Fix what you can in the spec files. Flag gaps you cannot resolve without human input as # TODO: link missing. Do not fabricate IDs.

Write each aligned file back to disk in place.

3. Validate

Run the repo's consistency check — mage audit, or mage analyze where the target is named that way — after all files are written.

Fix any errors it reports. Re-run until it exits 0 or until remaining errors require human input (in which case list them clearly).

4. Commit

Commit all changes:

git add -A
git commit -m "Align specifications to design constitution"

Report: how many files changed, what structural edits you made, and any TODOs that require human input.

---name: align-specsdescription: Read **docs/constitutions/design.yaml** first and hold it as the authority for the rest of this session.---# align-specs commandApply this command workflow. Treat any text after its invocation as the command input.# Command: Align SpecsRead **docs/constitutions/design.yaml** first and hold it as the authority for the rest of this session.## 1. InventoryFind all specification files in the project:- `docs/VISION.yaml`- `docs/ARCHITECTURE.yaml`- `docs/SPECIFICATIONS.yaml` (if present)- `docs/road-map.yaml` (if present)- `docs/specs/product-requirements/prd*.yaml`- `docs/specs/use-cases/rel*.yaml`- `docs/specs/test-suites/test-rel*.yaml`- `docs/engineering/eng*.yaml`List every file found. Skip any that do not exist.## 2. Align Each FileFor each file, read it, then apply the constitution's format rules for that document type:**Required fields**: Add any field that the constitution schema lists as required but is absent. Use a short placeholder value — do not invent content. Mark placeholders clearly (e.g. `# TODO: fill in`).**Field names**: Rename any field whose key does not match the schema exactly.**Style**: Apply the style rules from the constitution — active voice, present tense, remove forbidden terms, no bold in prose paragraphs, no horizontal rules. Do not rewrite substance; fix only what violates a rule.**Naming conventions**: Check each file's name against the `naming_conventions` block in the constitution (e.g. `prd[NNN]-[feature-name].yaml`, `rel[NN].[N]-uc[NNN]-[short-name].yaml`). Rename the file if it does not match. Update any cross-references in other files that point to the old name.**Traceability**: Apply the `traceability_invariants` block (T1–T5) from the constitution. Fix what you can in the spec files. Flag gaps you cannot resolve without human input as `# TODO: link missing`. Do not fabricate IDs.Write each aligned file back to disk in place.## 3. ValidateRun the repo's consistency check — `mage audit`, or `mage analyze` where the target is named that way — after all files are written.Fix any errors it reports. Re-run until it exits 0 or until remaining errors require human input (in which case list them clearly).## 4. CommitCommit all changes:```git add -Agit commit -m "Align specifications to design constitution"```Report: how many files changed, what structural edits you made, and any TODOs that require human input.

Frequently asked questions

Align Specs