Documentación de DIXI Spec Kit English · Código en GitHub

Esta página está disponible solo en inglés; el resumen en español, si existe, está al final.

DIXI Spec Kit and GitHub Spec Kit

Purpose

Help a person choose between, or combine, two specification-driven development kits, with facts and their sources. GitHub Spec Kit is a mature, widely used project; this page states where DIXI Spec Kit matches it, where it goes in a different direction and where it has gaps. It is refreshed with each DIXI release.

Sources and date

Read on 2026-11-11. GitHub Spec Kit v1.4.0 (released 2026-11-10): repository https://github.com/github/spec-kit (templates/commands/, CHANGELOG.md, docs/, README.md) and its open issues. DIXI Spec Kit v1.14.0. Figures about another project (agents, extensions, stars) change quickly and are quoted as that project publishes them; verify them before reusing.

Agent commands

GitHub Spec KitDIXI Spec KitNotes
/speckit.constitution/dixi.constitutionDIXI keeps the principles in 00-governance/principles.md, versioned, and every operation reads them.
/speckit.specify/dixi.specifyDIXI places each feature under a module and a domain, checked by dixi check.
/speckit.clarify/dixi.clarify
/speckit.plan/dixi.plan
/speckit.checklist/dixi.checklistBoth write requirement-quality items a person ticks; DIXI's build stops on open items.
/speckit.tasks/dixi.tasks
/speckit.analyze/dixi.analyzeBoth read only and report.
/speckit.implement/dixi.buildDIXI requires a failing test committed before code and treats committed tests as frozen.
/speckit.converge/dixi.convergeBoth append convergence tasks without editing specs or code.
/speckit.github.taskstoissues (extension)/dixi.issuesDIXI uses gh instead of an MCP server and creates nothing before the person confirms a preview.
—/dixi.onboard, /dixi.bugfixAdopting an existing codebase as validated drafts; traced bug fixes with a failing test first.
—21 more operationsDomain, architecture, contracts, data, threat model, AI, quality, verification, review, status, handoff, change, interview, risk review, release, promotion, operation, FinOps, compliance and due diligence.

CLI and platform

AreaGitHub Spec KitDIXI Spec Kit
Installuv tool install, uvx, pipx, PyPI, air-gappeduv tool install, pipx, PyPI, release wheel
Project checksspecify check (installed agent tools)dixi check (structure, links and goal → domain → module → feature → contract → test traceability), dixi doctor
Upgrading a projectspecify self upgrade upgrades the CLI; a procedure for already initialised projects is an open request (issue #1210)dixi upgrade --dry-run previews kit-file changes; dixi upgrade --apply writes only unedited kit files, atomically
WorkflowsExecutable, resumable workflows with human review gatesdixi workflow list/show/prepare: deterministic context packets; the agent runs the operation
ExtensibilityExtensions, presets, workflows, bundles and catalogs (the project lists 186 community extensions and 42 presets)Local, data-only extensions (dixi extension) that add operations and presets (dixi preset) that override kit texts and templates; no catalogs, workflows or bundles
MCPExperimental read-only serverNone; the CLI needs no network
Agents41 integrations plus generic and noneClaude Code and Codex (verified), skills (Agent Skills in .agents/skills/, format compatible with Cursor, Gemini CLI, OpenCode, Goose and Amp, verified for discovery and explicit invocation in OpenCode only), plus none
SystemsWindows, macOS and LinuxmacOS and Linux; Windows through WSL 2 (verified in CI)
Runtime dependenciesPython packagesNone (standard library only)
LanguagesREADME in English, Chinese, Japanese and Korean; docs in EnglishDocuments, commands and messages in English and Spanish

Where DIXI takes a different direction

Gaps DIXI has today

Using both

The two kits use different folders (.specify/ and specs/ against DIXI's numbered folders and .dixi/). Moving a project is a manual mapping, described in Coming from Spec Kit.