spec-dev 0.3.2

Bundle of the .spec-dev workspace template.

spec-dev

A small helper package that bundles the .spec-dev workspace template so it can be installed with pip and copied into new projects.

Installation

pip install spec-dev

If you are working from the repository source, you can install it locally instead:

pip install .

CLI Usage

# Initialise a project (default destination is the current directory)
spec-dev init
spec-dev init path/to/app
spec-dev init --force                  # overwrite an existing .spec-dev folder

# Create a task memory scaffold from the bundled template
spec-dev memory T-123

# Archive the current cycle and reset active templates/memories
spec-dev cycle --label fal-ai-image-gen

# Regenerate and validate the file coverage manifest for the current tasks
# Regenerate and validate the file coverage manifest for the current tasks
spec-dev tasks-manifest --rewrite --check

# Update task status or validate memories without editing Markdown manually
spec-dev tasks-status T-123 --set done
spec-dev memories                # add --ensure to scaffold missing stubs

Run spec-dev --help for the full command list and examples.

Python API

from spec_dev import copy, create_memory, complete_cycle
from spec_dev.tasks_manifest import cmd_build_manifest

root = copy("/path/to/project", overwrite=True)
memory = create_memory("T-123", root)
archive = complete_cycle(root, label="fal-ai-image-gen")
manifest = cmd_build_manifest(root)  # also available via CLI: spec-dev tasks-manifest

Each helper returns the Path it creates (the .spec-dev directory, the new memory file, or the archived history folder).

Workflow Primer

The bundled instructions under .spec-dev/*.md walk you through the Plan & Intent → Tasks → Implementation phases. Highlights:

• .spec-dev/templates/active/ contains fresh templates for each phase, ready to copy into .spec-dev/active-dev/. Add deeper discovery material alongside the plan only when it adds value.
• The Plan & Intent artifact must list every existing file to modify, every new file to create, and spell out ordered phases (Phase 0, Phase 1, …) with objectives and exit criteria.
• Run spec-dev tasks-manifest --auto-scope --rewrite --check after the task board is in place. It regenerates active-dev/file-coverage.json, validates that each (path, selector) maps to exactly one task (use @ <selector> to scope to a region), and becomes the checklist before you flip the gate to READY FOR IMPLEMENTATION.
• Tasks mirror the plan phases using ## Phase N — … headings with status badges while keeping the strict ### T-### + changes blocks for manifest compatibility.
• Implementation logs capture each finished task while you keep the phase badges in sync (note phase completion in a task entry only if it helps reviewers).
• Update task status (pending, in-progress, done) with spec-dev tasks-status T-XXX --set <status> so history stays intact until you archive the cycle.
• Task memories live under .spec-dev/active-memories/; use spec-dev memory T-XXX the moment a task ships to capture why it mattered, what changed, how it shipped, and the validation evidence. Run spec-dev memories (or --ensure) to verify/complement entries. The implementation log template links directly to these files.
• After delivering a cycle, run spec-dev cycle [--label <name>] to move the finished plan/tasks/implementation log and active memories into .spec-dev/history/, then reset active-dev/ and active-memories/ with clean templates for the next iteration.

Key Files

• .spec-dev/Plan.md, .spec-dev/Tasks.md, .spec-dev/Implementation.md — phase instructions that govern the agent. Add any deeper discovery material alongside the plan on an as-needed basis.
• .spec-dev/active-dev/ — working copies for the current cycle.
• .spec-dev/active-memories/ — task memory drafts for the active cycle.
• .spec-dev/active-dev/file-coverage.json — auto-generated manifest of task changes (maintained via spec-dev tasks-manifest).
• .spec-dev/history/ — archived cycles produced by spec-dev cycle.