Skip to content

SpecForge v0.1.0 — Initial public release

Choose a tag to compare

View all tags
@cihejimba cihejimba released this 19 May 19:27
· 18 commits to main since this release
v0.1.0
6fc953f

Initial public release. Phases 1-3 of the roadmap complete; Phase 4 (maturity) in progress.

For the canonical, machine-readable changelog entry see CHANGELOG.md. For the citation-stable record see CITATION.cff.

What is SpecForge?

An open-source framework for spec-driven agentic software engineering — vendor-neutral across Claude Code, Codex, Gemini CLI, Kiro, Cursor, and Windsurf. SpecForge ships markdown content (templates, runtime layouts, worked examples) rather than application code; consumers drop the per-vendor runtime layouts into their own repositories and adapt the templates to their stack.

What's in v0.1.0

Framework foundation

  • Repo skeleton, root files, vendor matrix, two-tier docs pattern.
  • Implementation team in .claude/: 11 author agents, 4 contributor skills, 4 slash commands, 3 hooks, agent-memory directories.
  • Sanitization infrastructure: gitignored wordlist + PreToolUse hook gate + /sanitize command + sanitization-auditor agent.

Artifact templates

  • PRDs: full 23-section enterprise + lightweight + platform SRS.
  • Specs: triplet (requirements-template.md + design-template.md + tasks-template.md) with stable IDs and back-reference contract; lightweight feature-spec; technical-spec; ADR.
  • Agents: template + 7 archetypes + cross-vendor roster.
  • Skills: folder-per-skill SKILL.md with full frontmatter contract.
  • Commands: per-vendor templates (Claude markdown + Gemini JSON).
  • Hooks: comprehensive coverage across all six vendors (~27 Claude / 6 Codex / 11 Gemini / 10 Kiro / ~19 Cursor / 12 Windsurf events).
  • Prompts: master/phase/task production-grade trio + per-vendor sets + shared utility prompts.

Runtime layouts

  • Per-vendor layouts under runtimes/.<vendor>/ for all six supported vendors.
  • MCP single-source-of-truth (runtimes/mcp/servers.yaml) + working Python renderers.
  • tools/sync-skills.py — cross-runtime skill / agent diff and copy.

Workflows and rules

  • 5 workflow playbooks (prd-to-production, spec-to-implementation, agent-review-loop, testing-and-validation, release-readiness).
  • Vendor-neutral engineering / code-review / security / documentation rules + per-vendor surfacing files.

Drop-in worked example: examples/sample-project/

  • Self-contained, Claude-Code-only.
  • Full PRD (23-section, prds/active/user-search.md), spec triplet (specs/user-search/), 5 ADRs (adrs/), 7 project-specific deep references (agentic-docs/).
  • 28 prompt files: 1 global master + 4 phase masters + 22 numbered task prompts + 2 runtime operational prompts.
  • 8 implementation-team agents, 4 slash commands, 3 hooks, agent-memory.
  • Drop-in flow: copy folder → rename .template files → open Claude Code → run prompts/runtime/pickup-next-task.md.

Documentation and attribution

  • 10-file agentic-docs/ framework reference library.
  • MAINTAINERS.md (governance, decision-making, becoming-a-maintainer).
  • CITATION.cff (CFF v1.2.0) — GitHub renders a "Cite this repository" button.
  • NOTICE file (Apache 2.0 attribution).
  • README sections: Maintainers, Citation, Mermaid spec-driven flow diagram with text fallback.

Get started

git clone https://github.com/Enovatr-Labs/SpecForge.git
cd SpecForge

# Read the canonical context
cat AGENTS.md

# Walk the worked example
ls examples/sample-project/

# Or copy the example into a new repo for drop-in use
cp -R examples/sample-project/. /path/to/your-new-repo/
cd /path/to/your-new-repo/
mv .claude/settings.local.template.json     .claude/settings.local.json
mv .claude/claude_desktop_config.template.json .claude/claude_desktop_config.json
mv .claude/.forbidden-strings.template.txt  .claude/.forbidden-strings.txt
# Open with Claude Code; run prompts/runtime/pickup-next-task.md

Citation

@software{Ihejimba_SpecForge_2026,
  author       = {Ihejimba, Chika},
  title        = {{SpecForge: An open-source framework for spec-driven agentic software engineering}},
  organization = {Enovatr Labs},
  year         = {2026},
  version      = {0.1.0},
  url          = {https://github.com/Enovatr-Labs/SpecForge},
  license      = {Apache-2.0}
}

A persistent DOI via Zenodo will be added at v1.0.

Roadmap

See ROADMAP.md. Phase 4 (Maturity) target items include additional worked examples, broader vendor support based on community demand, and the Zenodo DOI.

Maintainers

Assets 2
Loading