[Preset] Software Humano

[dacunao]

Preset ID

software-humano

Preset Name

Software Humano

Version

2.0.3

Description

Compiles the requirements of the Software Humano manifesto into the eight core Spec Kit commands and into the spec, plan and tasks templates, quoting the manifesto's literal text rather than rephrasing it. Treats the cost a product transfers to the person — attention, learning, decisions they did not come to make — as something budgeted and verified.

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/preset-software-humano-v2.0.3/Software_Humano_Preset_v2.0.3.zip

Documentation URL

https://github.com/dacunao/software-humano-speckit/blob/preset-software-humano-v2.0.3/tools/speckit/software-humano-spec-kit-preset-2.0.3/README.md

License

MIT

Required Spec Kit Version

=1.0.0,<2.0.0

Required Extensions (optional)

None — the preset installs and works on its own.

Templates Provided

• constitution-template — the manifesto core's full operational projection (the one template composed with replace, because its content is entirely the preset's own)
• spec-template — additions composed with append
• plan-template — additions composed with append
• tasks-template — additions composed with append

Commands Provided

• constitution
• specify
• clarify
• plan
• tasks
• analyze
• implement
• converge

Number of Scripts (optional)

0

Tags

human-centered, jobs-to-be-done, job-stories, product-governance, sdd

Key Features

• Each command gains one table whose every row is a literal quotation of the manifesto core v2.1: where it says it, what it requires, and which artifact or verification dimension answers it. No prose of our own.
• Commands compose with wrap and declare no frontmatter of their own, so the native description, handoffs and scripts survive intact. This is also what lets an agent invoke them from natural language, since the native descriptions name concrete artifacts and moments.
• Templates use append, not replace, so the sections native commands look up by name are preserved. The constitution template is the single exception.
• Of 300 checkable statements in the manifesto core, 210 are compiled; 40 are declared out of scope with a stated reason and 50 are editorial. The coverage map ships with the package.
• It is not a design system: it sets criteria — accessibility, states, cognitive load, performance, traceability — not aesthetics. Visual direction stays with the team.
• Licensing boundary. The preset's code is MIT. The manifesto core's text, including its projection in templates/constitution-template.md, is CC BY 4.0. Which file falls on which side is declared in LICENSING.md inside the ZIP.

Testing Checklist

• Preset installs successfully via specify preset add
• Template resolution works correctly after installation
• Documentation is complete and accurate
• Tested on at least one real project

Additional context

Two real projects are using the method. The first is the manifesto's own public site, built and live. The second is the Software Humano agency site, under construction right now, and it runs this exact version — preset 2.0.3, byte for byte identical to the submitted archive. That project has materialized the constitution from this preset's constitution-template, resolved 31 clarifications, run three rounds of analyze corrections and converge, moved its product foundation through three approved versions, and committed an implementation phase.

The preset was also installed from the exact download URL submitted here, into a clean Spec Kit project, and its templates resolve with the manifesto addendum present.

What the first project measured, including what went wrong. The method's provisions reached the artifacts without anyone typing a command: the agent recognized the moment from natural language and ran analyze ten times and converge seven, chosen turn by turn. In seven cases the method changed a product decision. It also found its own limits — four experience defects were found by a person using the product, and all four had passed every automated check. The commands compare artifacts with each other and code with tasks; none of them looks at the screen.

We publish that record rather than hiding it, including a measured execution-cost analysis and nine open items: https://github.com/dacunao/software-humano-speckit/blob/main/ROADMAP.md

On the tag naming. This repository ships four components that version independently, so the release tag carries the component's scope: preset-software-humano-v2.0.3. The package's own releases use vX.Y.Z.

On language. Most of the package's documentation is written in Spanish, where the doctrine holds its authority. This preset's own README is in English.

Submission Requirements

• Valid preset.yml manifest included
• Linked README (Documentation URL) explains how to use this preset and includes a valid specify preset add ... command
• LICENSE file included
• GitHub release created with version tag
• Preset ID follows naming conventions (lowercase-with-hyphens)

[github-actions]

cc @github/spec-kit-maintainers — new catalog submission for review.

[github-actions]

Validation failed for this preset submission.

Failed checks:

• Version/download tag pinning: Submitted version is 2.0.3, but the download URL uses release tag v2.3.2. The tag's semver must match the submitted version (for example, use a v2.0.3 tag or submit version 2.3.2). Because pinning failed, the archive URL was not fetched.
• Issue-form fields: Tags and Number of Scripts were not provided. Templates Provided and Commands Provided are prose rather than the required list-item format (- ...) or None, so their required counts cannot be parsed as submitted.
• Submission checklists: The required checked Testing Checklist and Submission Requirements sections are missing from the issue body. Please submit the complete issue form with every required checkbox checked.

The repository is publicly accessible and contains LICENSE and preset.yml under tools/speckit/software-humano-spec-kit-preset-2.0.3/. The submitted documentation URL resolves to a readable README and contains an accepted specify preset add --dev ... command.

Please update the submission with the corrected version/tag and complete required fields/checklists, then request validation again.

Generated by 🎨 Add Community Preset from Issue Submission for #4802 · copilot · gpt52codex · 1.47 AIC · ⌖ 9.26 AIC · ⊞ 25.4K · ◷

[KSchlobohm]

Thanks for your submission. Please address the feedback by matching the preset version to the release tag, adding the missing issue details, and completing the required checklists so we can rerun validation.

[dacunao]

@KSchlobohm thanks — the submission is updated. Every failed check is addressed.

Version/download tag pinning. The repository ships four components that version independently, so the release tag now carries the component's scope: preset-software-humano-v2.0.3, matching the submitted version 2.0.3. The package's own releases keep using vX.Y.Z.

Issue-form fields. Tags and Number of Scripts are now provided, and Templates Provided / Commands Provided are list items rather than prose.

Submission checklists. Both sections are present with every box checked. Each one is backed by evidence rather than assumed — the preset was installed from the exact download URL above into a clean Spec Kit project, and its templates resolve with the manifesto addendum present.

All submitted URLs return HTTP 200. Ready for validation to be rerun whenever suits you — the workflow triggers on the preset-submission label, which I can't re-apply myself.