Roadmap: What's coming in v5.6 — telemetry dashboard, more rule packs, GitHub Action

[sgroy10]

Roadmap: What's coming in v5.6 — telemetry dashboard, more rule packs, GitHub Action

Posting the public roadmap so the community can weigh in. v5.6 is targeting a release in ~4 weeks. Here's what's planned, what's shipped on main, and what I'm still deciding on.

Shipped on main (will land in v5.6)

Telemetry dashboard

A local-first, opt-in dashboard at http://localhost:5151/speclock that shows:

• Violations caught over time (per-repo)
• Which locks trip most often
• Drift heatmap across your tracked repos
• Session activity for Claude Code / Cursor / Copilot

All data stays local. No phone-home. Opt-in via speclock telemetry enable.

Expanded synonym taxonomy

v5.5.7 added "sweep away", "wipe", "purge". v5.6 extends coverage to architectural actions: "refactor out", "inline away", "absorb into", "migrate off of". See the Show & Tell post on v5.5.7 for context.

New rule packs

Curated rule packs you can apply with one command:

• speclock apply-template nextjs-prod — production Next.js guardrails
• speclock apply-template python-data — data pipeline invariants
• speclock apply-template monorepo-turbo — monorepo workspace boundaries
• speclock apply-template oss-library — public package hygiene

Each pack is curated from real-world violations I've seen across 50+ repos.

GitHub Action

sgroy10/speclock-action@v1 — runs semantic audit on every PR. Posts a comment with:

• Violations found (with file + line)
• Suggested fix
• A "SpecLock approved" badge on clean PRs

This is the piece I get the most requests for. It's ~80% done.

Under consideration (need community input)

1. VS Code extension — should SpecLock ship a standalone VS Code extension, or is the MCP-via-Cursor path enough? Let me know which you'd use.

2. Team mode — shared lock registry across a team via a hosted sync service. This would be a paid tier. Is this something you'd actually pay for, or should it stay 100% local/OSS?

3. Rule conflict auto-resolver — when two locks disagree, suggest a merge. Useful but complex. Worth it?

4. LLM-assisted lock authoring — speclock suggest-locks already exists but v5.6 could ship a conversational mode where you describe a rule and it writes the lock spec for you.

Not shipping in v5.6 (punted to v5.7+)

• Non-git VCS support (Mercurial, Fossil) — low demand
• Cloud-hosted audit service — out of scope for now
• GUI installer — CLI is good enough

How to influence the roadmap

1. Reply to this thread with what you want prioritized.
2. Open a GitHub Issue tagged feature-request.
3. Drop into an existing discussion and +1.

Everything ships as OSS. The repo is at sgroy10/speclock. Star it if you find it useful — it actually does help visibility.

Thanks for all the feedback so far. v5.6 is shaped by it.