Spec Kit Spark Roadmap

Future plans and development direction for the Adaptive System Life Cycle Development Toolkit

Vision Statement

Spec Kit Spark aims to become the definitive toolkit for AI-agent driven software development lifecycle management, built on three pillars:

  • Agent-agnostic by default — every AI assistant is a first-class citizen; canonical prompts live in .documentation/commands/ with thin platform shims
  • Multi-user personalization — shared governance with individual customization via /speckit.personalize and per-user overrides in .documentation/{git-user}/commands/
  • Complete lifecycle coverage — from project initiation through ongoing maintenance, release management, and constitution evolution
  • Adaptive workflows that scale from quick fixes to complex features
  • Living governance where constitutions evolve with the systems they govern
  • Measurable quality through continuous compliance tracking
  • Seamless integration with existing development tools and practices

Current Release: v1.6.0

What's Implemented

Core Spec-Driven Development

  • ✅ /speckit.constitution - Create and manage project principles
  • ✅ /speckit.specify - Feature specification creation
  • ✅ /speckit.plan - Technical implementation planning
  • ✅ /speckit.tasks - Task breakdown generation
  • ✅ /speckit.implement - Task execution
  • ✅ /speckit.clarify - Specification clarification
  • ✅ /speckit.checklist - Quality checklist generation
  • ✅ /speckit.analyze - Artifact consistency checking

Constitution-Powered Commands

  • ✅ /speckit.discover-constitution - Brownfield constitution discovery
  • ✅ /speckit.pr-review - Constitution-based PR review
  • ✅ /speckit.site-audit - Codebase compliance auditing
  • ✅ /speckit.critic - Adversarial risk analysis

Adaptive Lifecycle Commands

  • ✅ /speckit.quickfix - Lightweight workflow for bug fixes
  • ✅ /speckit.release - Release documentation and archival
  • ✅ /speckit.evolve-constitution - Constitution amendment proposals
  • ✅ /speckit.harvest - Knowledge-preserving cleanup for stale docs and completed specs
  • ✅ /speckit.repo-story - Evidence-based repository narrative generation

CLI Commands

  • ✅ specify init - Initialize new or existing projects
  • ✅ specify upgrade - Upgrade existing projects
  • ✅ specify check - Verify tool dependencies
  • ✅ specify version - Show version information

Architecture (NEW in v1.6.0)

  • ✅ Agent-agnostic canonical layout — prompts in .documentation/commands/ with thin platform shims
  • ✅ Multi-user personalization (/speckit.personalize) — per-user overrides in .documentation/{git-user}/commands/
  • ✅ SPECKIT_VERSION stamp — version tracking for consumer projects

Platform Support

  • ✅ Agent-agnostic architecture (canonical prompts + thin platform shims)
  • ✅ Multi-user personalization (/speckit.personalize)
  • ✅ 17+ AI agent integrations
  • ✅ Cross-platform scripts (Bash + PowerShell)
  • ✅ Greenfield and brownfield support

Near-Term Roadmap (v1.7.x – v1.8.x)

Enhanced Technical Debt Tracking

Goal: Make technical debt a first-class, measurable metric.

Feature Description Status
Debt Metrics Storage Store audit results in structured format for trend analysis 🔜 Planned
Debt Dashboard Summary view of technical debt across categories 🔜 Planned
Burndown Tracking Track debt reduction over sprints/releases 🔜 Planned
Debt Prioritization AI-assisted prioritization of remediation items 🔜 Planned

Improved Business Value Alignment

Goal: Connect development activities to business objectives.

Feature Description Status
Business Value Metadata Optional fields in specs linking to goals/epics 🔜 Planned
Value Tracking Track business value realization through lifecycle 📋 Backlog
OKR Integration Link features to OKRs and success metrics 📋 Backlog

Workflow Enhancements

Goal: Smoother developer experience.

Feature Description Status
Workflow Selection Guide Interactive guidance for choosing appropriate workflow 🔜 Planned
Quickfix → Spec Upgrade Seamless escalation when quickfix grows 🔜 Planned
Batch Operations Process multiple quickfixes or specs in batch 📋 Backlog

Medium-Term Roadmap (v1.9.x – v2.x)

Constitution Evolution Automation

Goal: Automated detection and proposal of constitution updates.

Feature Description Status
Automatic Pattern Detection Detect new patterns that should become principles 📋 Backlog
Conflict Detection Identify when proposals conflict with existing principles 📋 Backlog
Amendment History UI Visualization of constitution evolution over time 📋 Backlog
Team Voting Integration Built-in approval workflow for amendments 📋 Backlog

Documentation Lifecycle

Goal: Zero documentation drift.

Feature Description Status
Auto-Archive Triggers Automatic archival when specs are fully implemented 📋 Backlog
Staleness Detection Alert when specs haven't been updated in N days 📋 Backlog
Cross-Reference Validation Ensure documentation references are valid 📋 Backlog
Documentation Coverage Track what % of code has corresponding docs 📋 Backlog

Integration Ecosystem

Goal: Seamless integration with existing tools.

Feature Description Status
Jira/GitHub Issues Sync Bi-directional sync with issue trackers 📋 Backlog
CI/CD Integration Run audits and reviews as pipeline steps 📋 Backlog
IDE Extensions VS Code extension for in-editor commands 📋 Backlog
Slack/Teams Notifications Alert channels on review findings 📋 Backlog

Long-Term Vision (v2.x+)

Intelligent Context Management

Goal: Optimal AI agent context for every task.

Feature Description
Dynamic Context Sizing Automatically determine optimal context based on task
Context Caching Cache common context patterns for efficiency
Multi-Agent Coordination Distribute tasks across multiple agents effectively
Learning from Feedback Improve context selection based on success rates

Cross-Project Governance

Goal: Organizational-level consistency.

Feature Description
Template Library Shared constitution templates across projects
Org-Level Principles Inherit organizational standards into project constitutions
Cross-Project Auditing Compliance reporting across portfolio
Best Practices Mining Extract patterns from successful projects

Advanced Analytics

Goal: Data-driven development insights.

Feature Description
Predictive Quality Predict quality issues before they occur
Developer Productivity Insights into workflow efficiency
Architecture Health Long-term architectural trend analysis
Cost of Delay Business impact of technical debt

Experimental Features

These features are in early exploration and may not ship:

Machine Learning Integration

  • Pattern Recognition: ML-based detection of code patterns for constitution discovery
  • Risk Prediction: Predict which PRs are likely to have issues
  • Context Optimization: Learn optimal context size per developer/task type

Natural Language Improvements

  • Conversational Spec Creation: More natural dialogue for specification
  • Requirement Extraction: Extract specs from meeting transcripts
  • Documentation Generation: Auto-generate user-facing docs from specs

Multi-Repository Support

  • Monorepo Support: Handle large monorepos with multiple constitutions
  • Microservice Coordination: Cross-service spec and review management
  • Shared Libraries: Constitution inheritance for shared code

How to Contribute

We welcome contributions in all areas! Here's how to get involved:

High-Impact Contributions

  1. Technical Debt Tracking - Help build the metrics storage and visualization
  2. Business Value Alignment - Design the metadata schema for business linking
  3. CI/CD Integration - Create GitHub Actions or other CI integrations

Documentation Contributions

  1. Use Case Documentation - Document how you use Spec Kit in your workflow
  2. Tutorial Creation - Create tutorials for specific scenarios
  3. Translation - Help translate documentation

Feature Requests

  1. Open a GitHub Issue with the enhancement label
  2. Describe the use case and expected behavior
  3. Include any relevant examples or mockups

Pull Requests

  1. Fork the repository
  2. Create a feature branch
  3. Follow existing code patterns
  4. Include tests where applicable
  5. Update documentation
  6. Submit PR with clear description

Versioning Strategy

Spec Kit Spark follows standard Semantic Versioning 2.0.0:

vMAJOR.MINOR.PATCH

Examples:
- v1.6.0  (current stable release)
- v1.7.0  (next minor feature additions)
- v2.0.0  (breaking changes)

Version Meaning

Component Meaning
MAJOR Breaking changes to command interfaces or file formats
MINOR New commands or significant feature additions
PATCH Bug fixes and minor improvements

Community

Getting Help

Staying Updated

Last updated: April 2026

Edit this page