conform

Diagnose and fix convention drift in governed feature folders after a Speccle convention change.

1|Updated Jul 9, 2026
One-click install
npx skills add https://github.com/matthewalton/speccle --skill conform-matthewalton
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conform
Source: https://github.com/matthewalton/speccle/tree/main/packages/plugin/skills/conform
Command: npx skills add https://github.com/matthewalton/speccle --skill conform-matthewalton

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When the Speccle convention changes — a folder shape tightens, a new contract file becomes required, a lint rule sharpens — feature folders scaffolded under the old convention silently drift out of compliance. This Skill sweeps every governed feature folder, diagnoses each slice's drift against the current convention, and applies form-only fixes while keeping the test suite green. ## Core Features & Use Cases - Drift diagnosis: Finds every SPEC.md under a project root and checks each slice against the bundled convention — folder naming, markdown contract completeness, over-full flat src/ directories, decisions content misplaced in CONTEXT.md, and lint violations via the deterministic speccle oracle. - Form-only remediation: Renames catch-all folders, regroups over-full directories, migrates AGENTS.md to CLAUDE.md, splits decisions into ADR files, and rewords statements only as far as lint requires — never changing behaviour or splitting slices. - Verified completion: Confirms lint exits 0, the whole suite stays green with the same test count, and the diff contains no source-semantic changes, then hands back a spec summary with findings. - Use Case: After upgrading Speccle to a version whose convention renamed AGENTS.md to CLAUDE.md and added a new lint rule, run this Skill to sweep all feature folders, apply the renames and rewordings, and receive a per-slice report of what changed. ## Quick Start Conform all the feature folders in this repository to the current Speccle convention and report any drift you find.

Frequently Asked Questions about conform

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update Speccle feature folders after the convention changes?▼

Run the conform skill against your project root. It finds every SPEC.md, diagnoses each slice against the bundled convention, announces a drift report, and applies form-only fixes such as folder renames, AGENTS.md migration, and lint-driven rewording while keeping the suite green.

What is the difference between conform, carve, and amend in Speccle?▼

Conform updates already-governed folders to the current convention with form-only changes. Carve brings ungoverned code (no SPEC.md) under governance, and amend changes what a criterion means. A request mixing conforming with either is handled as two separate passes.

Does conform change code behaviour or split features?▼

No. Conform applies form changes only — file moves, import and config fixes, markdown edits — and never splits a slice into sibling features. When an over-full directory reads as two behaviours, it regroups files and records a split suggestion as a finding for the human to decide.

What happens if the speccle CLI is not installed?▼

The skill resolves the oracle in order: the repo's pinned copy in node_modules/.bin, a global install on PATH, or running from a source clone with Node 24 or later. If none resolves, it points you to the install steps in Speccle's README and stops rather than hand-checking lint rules.

Why does conform refuse to start on a failing test suite?▼

Conform never starts on red without saying so, because a pre-existing failure is the user's to rule on, not something to absorb into the drift-fix diff. It runs the suite before touching anything and verifies the same test count stays green after every structural move.