[Extension Submission] Conformidad — Software Humano conformance checks

[dacunao]

Extension ID

conformidad

Extension Name

Conformidad — Software Humano

Version

2.2.2

Description

Runs a deterministic conformance check over a project's artifacts: verifies that what the Software Humano manifesto requires is present, that every absence is declared as an approved exception, and that the method itself is still installed intact.

Author

Damián Acuña

Repository URL

https://github.com/dacunao/software-humano-speckit

Download URL

https://github.com/dacunao/software-humano-speckit/releases/download/v2.3.2/Software_Humano_Conformidad_v2.2.2.zip

Documentation URL

https://github.com/dacunao/software-humano-speckit/blob/v2.3.2/tools/speckit/conformidad-2.2.2/README.md

Changelog

https://github.com/dacunao/software-humano-speckit/blob/v2.3.2/tools/speckit/conformidad-2.2.2/CHANGELOG.md

License

MIT

Required Spec Kit Version

=1.0.0,<2.0.0 (verified on 1.0.8)

Required Tools

git to compare dates, python3 to read Spec Kit's preset registry. Without either it says so and does not check, rather than reporting green.

Commands

1 — speckit.conformidad.comprobar

Hooks

1 — registered as a mandatory before_implement hook. Category quality, effect read-only: it never modifies an artifact.

Key Features

• Ships a deterministic script a person, a CI job or a workflow shell step can run. Spec Kit hooks are invoked by the agent, which means an agent can skip one without anything noticing; this one is outside that discretion.
• Verifies the method is still installed. A preset can be left without effect silently: a project-local override wins over any preset, another preset with higher precedence can register a command in its place, an emptied template layer removes the doctrine. In all three cases the artifact comes out clean because nothing was ever asked of it. The check reads Spec Kit's own preset registry to detect the precedence case.
• Detects decisions that never reached the artifacts. A decision made in conversation gets recorded in AGENTS.md or the product foundation and may never reach spec.md. The artifact stays complete and correct, so no other check can see it. This compares last-commit dates and stops when a governing source is newer. It detects one direction only, and says so.
• Approved exceptions need four fields — artifact, section, reason, and who approved — because an exception without a reason or an approver is not an approved exception. When one is missing it names which.

Testing details

Verified on one real project — a multilingual documentation site built with the method — plus an automated rehearsal that installs the package into a throwaway project and asserts 36 claims, including that the check stops on an undeclared absence, stops on an incomplete exception naming the missing field, and goes green again once reconciled.

Example usage

.specify/extensions/conformidad/scripts/conformidad.sh

Exit 0 when everything is covered or declared, 1 when something is missing undeclared or the method is not installed intact, 2 when it cannot find the project.

Additional context

What it does not check is stated in its README: whether what is written is any good, and whether the experience meets the principles. Neither is reachable by any of these checks — in the pilot, four real defects were found by a person using the product and had passed every check.

Pairs with the software-humano preset, submitted separately. Most of the package's documentation is in Spanish; this extension's README is in English.