DIXI Spec Kit
Purpose / Propósito
Specification-driven development (SDD) kit by Dixi Project: traceable specs, tests first, verified code and human review. Ships the dixi CLI (standard library only, no network, no AI calls) and optional commands for Claude Code and Codex.
Kit de desarrollo guiado por especificaciones de Dixi Project: specs trazables, pruebas primero, código verificado y revisión humana.
Install
uv tool install dixi-spec-kit # or: pipx install dixi-spec-kit
Requirements: Python 3.11+, macOS or Linux. On Windows, use WSL 2 with the project under ~, not /mnt/c; native Windows exits with code 4.
Quickstart
dixi init my-project --agent claude # or --agent codex, --agent skills, or --agent none
cd my-project
dixi doctor
dixi check
make verify
Optional: --profile site|app|platform (and --regulated) for fuller templates, --controls (with --agent claude or codex) for hooks that enforce frozen tests, no secrets, no signing or merging, production-mode safety and verification before stopping. Without --controls, these rules are instructions; hooks are a second layer, not the last one.
In Claude Code, thirty-three commands: /dixi.constitution, /dixi.onboard, /dixi.discover, /dixi.interview, /dixi.specify, /dixi.clarify, /dixi.domain, /dixi.architecture, /dixi.contract, /dixi.data, /dixi.threat-model, /dixi.ai, /dixi.plan, /dixi.tasks, /dixi.build, /dixi.verify, /dixi.review, /dixi.analyze, /dixi.checklist, /dixi.converge, /dixi.bugfix, /dixi.issues, /dixi.quality, /dixi.status, /dixi.handoff, /dixi.change, /dixi.release, /dixi.promote, /dixi.operate, /dixi.finops, /dixi.compliance, /dixi.duediligence, /dixi.risk-review, plus four subagents.
For other agents that read Agent Skills (Cursor, VS Code/Copilot, Gemini CLI, OpenCode…), --agent skills installs the operations in .agents/skills/, with implicit invocation disabled. In Codex, --agent codex installs the same operations as skills, invoked as $dixi-specify, $dixi-plan, etc., with implicit invocation disabled.
Terminal: dixi init, dixi doctor, dixi check, dixi workflow list|show|prepare, dixi upgrade --dry-run (preview what a newer kit version would change, without writing), dixi upgrade --apply (write only kit files you have not edited), dixi extension add|list|remove (your own operations from a local, data-only folder), dixi preset add|list|remove (your versions of kit texts and templates), dixi placeholders, dixi pr-size. Global options --lang es|en and --json go before the command. Exit codes: 0 success, 1 invalid content, 2 usage, 3 occupied or unsafe destination, 4 unsupported version or platform, 5 I/O.
dixi check and the generated make verify check documentary structure and traceability; connect your application's real tests to make verify.
Related / Relacionados
Source, documentation, support matrix and contribution guide: https://github.com/dixi-project/dixi-spec-kit. License: MIT.
Metadata
Release files for dixi-spec-kit 1.9.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| dixi_spec_kit-1.9.0.tar.gz | 602.2 kB | With provenance | Details for dixi_spec_kit-1.9.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dixi_spec_kit-1.9.0-py3-none-any.whl | Python 3 | none | any | Details for dixi_spec_kit-1.9.0-py3-none-any.whl |
Total release size: 1.6 MB
Release files / dixi_spec_kit-1.9.0.tar.gz
| Download URL | dixi_spec_kit-1.9.0.tar.gz |
|---|---|
| Size | 602.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3f8a10ccb676b49958721963fcce79d9f415fb5e7863ee7e3b7c049e2f9a35a3
|
|
BLAKE2b-256 checksum How to use checksums |
cece1d960ae57fae3aa823bcfbfda6585c7bbe53c5f7ba3cf567dc7fa50ef354
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logRelease files / dixi_spec_kit-1.9.0-py3-none-any.whl
| Download URL | dixi_spec_kit-1.9.0-py3-none-any.whl |
|---|---|
| Size | 1.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
196043fccc7368a805de8940d28ee5d05445372fd0d0eba92f37fcedcbaec1cf
|
|
BLAKE2b-256 checksum How to use checksums |
765882051b3ca812106fb3f62d29d5a15260a7be3a6311261ae8f20378a4a3d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logSecurity for dixi-spec-kit 1.9.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for dixi_spec_kit-1.9.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.