Spec-Craft
Obsidian-based Spec-Driven Development (SDD) toolkit with MCP and spec-kit integration.
Concept
spec-craft is a bridge between high-level roadmaps in Obsidian and tactical implementation using spec-kit.
Strategy vs Tactics
- Strategy (Obsidian): Defines the "What" and "Why". It holds the project's soul, long-term roadmap, and domain-specific principles (Manga storyboards, CAD logic, Blender Bonkei rules, etc.).
- Tactics (spec-kit): Defines the "How". It executes iterative SDD cycles (Specify → Plan → Implement) to generate concrete code and assets based on the strategy.
Installation
uv sync
pip install -e .
spec-kit Extension Setup
To enable slash commands (e.g., /speckit.obsidian-analyze), copy the extension/ folder to your project's .specify/extensions/spec-craft/ directory.
Discovery
Find more AI agent extensions at the official registry: geminicli.com/extensions/.
Automated Release Process
Spec-Craft uses GitHub Actions for CI/CD:
- Testing: Every push/PR triggers a test matrix across Python 3.10-3.12.
- Publishing: Pushing a tag matching
v*automatically builds and publishes the package to PyPI using Trusted Publishing.
Usage
Build Output Organization
All generated assets are stored in the build/ directory:
build/manga/<lang>/: Translated SVG scenes.build/cad/universal/: Parametric STL models and SVG projections.build/3d/universal/: Blender Python scripts for scene construction.
3D Preview
To view your generated CAD models interactively, run:
spec-craft browse
This starts a local server and opens a Three.js viewer. You can load specific models using query parameters: http://localhost:8080/?model=cad/universal/my_part.stl.
Visual Feedback Loop
When triggering a CAD build or rendering a 3D scene, spec-craft can generate SVG projections. These are ideal for AI vision analysis, allowing your agent to "see" the dimensions and propose improvements.
Isolated AI Editing
Spec-Craft provides a dedicated Emacs sandbox for AI agents. This environment is isolated from your personal configuration and comes pre-configured with LSP (Eglot) and Linting (Flymake) support to ensure high-quality code generation.
Transparent Tactical Workflow
Spec-Craft prioritizes transparency and security for project operations. Instead of executing sensitive tasks (like branch creation or planning) in the background, your AI agent will read the spec-kit definitions and propose the exact command for you to run. This ensures that interactive events, such as SSH password prompts, are handled safely by you in your own terminal.
Usage
CLI
spec-craft --version
spec-craft serve
MCP Server
Register the server in your MCP client (e.g., Claude Desktop, Gemini CLI) using:
{
"mcpServers": {
"spec-craft": {
"command": "spec-craft",
"args": ["serve"]
}
}
}
Metadata
Release files for spec-craft 0.1.8
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 |
|---|---|---|---|---|
| spec_craft-0.1.8.tar.gz | 40.3 kB | With provenance | Details for spec_craft-0.1.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| spec_craft-0.1.8-py3-none-any.whl | Python 3 | none | any | Details for spec_craft-0.1.8-py3-none-any.whl |
Total release size: 85.1 kB
Release files / spec_craft-0.1.8.tar.gz
| Download URL | spec_craft-0.1.8.tar.gz |
|---|---|
| Size | 40.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fe2df3857ea259bae200eec6172943bc9f9da1866a0c0dbb7f2bba4d244f9328
|
|
BLAKE2b-256 checksum How to use checksums |
9f8418e9be672703d088c392cf44c59c1a0ab9e762910a39779e888beae7bcfa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 16, 2026.
Transparency logRelease files / spec_craft-0.1.8-py3-none-any.whl
| Download URL | spec_craft-0.1.8-py3-none-any.whl |
|---|---|
| Size | 44.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
05c44260fee4be64ecd62d3a616e5fab74a3df5bff743aa31df87c581a22bafd
|
|
BLAKE2b-256 checksum How to use checksums |
59cea1c8b9e9398d27b5544f76e15c38db949c953a77a363a24c4832381c3789
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 16, 2026.
Transparency logSecurity for spec-craft 0.1.8
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for spec_craft-0.1.8.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 Oct 16, 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.