Roadmap

This roadmap reflects the current direction of Spec-To-Ship. It is intentionally lightweight and will evolve over time based on real usage patterns and feedback.

Now — Stabilization

The current focus is on making the core workflow solid and reliable:

CLI reliability and correctness across environments
Stage orchestration clarity and predictability
Governance files and project structure consistency
Documentation completeness — especially for first-time users
Onboarding experience (s2s init, s2s doctor)

The goal is that every user who installs s2s and runs s2s init has a clear, working path forward.

Next — Adoption

Once the core is stable, the focus shifts to real-world usability:

Improved examples and reference projects
Better documentation for different user profiles — solo developer, small team, engineering lead
Developer experience improvements and ergonomic refinements
Deeper integration patterns with common AI coding workflows
Discoverability and onboarding improvements

Later — Ecosystem

Longer-term exploration areas, not committed:

Advanced workflow extensions for complex project structures
Richer project state introspection and visualization
Team environment integration patterns
Optional ecosystem tooling around spec-to-ship

Principles

The roadmap is guided by:

Keeping the tool genuinely useful as open-source software
Avoiding unnecessary complexity — the workflow should stay predictable
Prioritizing clarity and execution quality over feature count
Maintaining a clean separation from any future commercial products

No functionality is intentionally restricted to paid users. Commercial work (if any) will be built separately, not by degrading the open-source version.

Feedback

If you have a use case that isn’t well-served by s2s today, open a GitHub issue. Patterns that repeat across multiple users influence prioritization more than individual requests.