Skip to content

Commit 5135ca4

Browse files
committed
docs: mark v0.4 roadmap items complete
1 parent 275f742 commit 5135ca4

File tree

1 file changed

+96
-0
lines changed

1 file changed

+96
-0
lines changed

docs/ROADMAP.md

Lines changed: 96 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,96 @@
1+
# suggestion-box Roadmap
2+
3+
## v0.2 — Foundation & Trust
4+
> Goal: fix adoption blockers, make the project safe to recommend to strangers
5+
6+
- [x] Fix issue #57`init` modifying global `~/` (adoption blocker)
7+
- [x] Add `--dry-run` flag to `init` that shows what would be written without touching anything
8+
- [x] Add config schema validation with clear error messages on startup
9+
- [x] Add per-session rate limiting to prevent runaway agent spam
10+
- [x] Add minimum quality filter rejecting vague/too-short submissions before hitting the queue
11+
- [x] Store session ID on every feedback entry now, even before transcript capture exists
12+
- [x] Capture dependency/package versions on every feedback entry for regression analysis
13+
- [x] Tie feedback entries to git SHA at submission time; auto-flag when related files change
14+
- [x] ~~Add `CHANGELOG.md`~~ (covered by release-drafter)
15+
- [x] Add `CONTRIBUTING.md`
16+
17+
---
18+
19+
## v0.3 — Developer Experience
20+
> Goal: make it feel polished and serious to first-time visitors
21+
22+
- [x] Add a demo GIF/screen recording to the README showing the full submission → triage → publish loop
23+
- [x] Add a "Built with suggestion-box" section to the README linking to actual agent-filed issues
24+
- [x] Give cross-agent compatibility (Claude Code + Codex + OpenCode) its own README section
25+
- [x] Build a `suggestion-box doctor` command to verify environment health (`gh` CLI, embedding model, write permissions)
26+
- [x] Ship pre-authorized tool list in Claude Code config for safe operations (`submit`, `upvote`, `list`, `status`, `triage`) — keep `publish_to_github` and Linear outside the allowlist
27+
- [x] Make feedback categories configurable per project
28+
- [x] Create a README badge for adopters to add to their own repos — passive distribution
29+
- [x] Publish a Homebrew formula
30+
31+
---
32+
33+
## v0.4 — Review Workflow
34+
> Goal: make human triage fast enough to actually happen
35+
36+
- [x] Fix CLI/MCP server DB lock contention — CLI commands fail when server is running (#149)
37+
- [x] Make `init` create the database so `doctor` passes immediately (#150)
38+
- [x] Fix GitHub dedup for custom categories — `searchExistingIssues` only handles hardcoded title prefixes (#148)
39+
- [x] Auto-triage by vote count to surface high-signal items without manual review
40+
- [x] Build interactive `suggestion-box review` TUI with keyboard shortcuts (`p`=publish, `e`=edit, `d`=dismiss, `s`=skip)
41+
- [x] Add a `/review` slash command that kicks off the pre-triage agent flow conversationally inside Claude Code
42+
- [x] Add a pre-triage MCP tool that groups entries, deduplicates against target repo/Linear, enriches with impact summary, and moves results to a `pending_review` queue
43+
- [x] Inject a digest of top-voted unresolved friction into SessionStart so new agents arrive pre-warned
44+
- [x] Add a webhook option that pings Slack/Discord when high-vote items arrive
45+
46+
---
47+
48+
## v0.5 — Transcript & Context
49+
> Goal: give the triage agent enough context to reason well
50+
51+
- [ ] Leverage Claude Code's native session transcripts at `~/.claude/projects/<project-hash>/<session-id>.jsonl`
52+
- [ ] Add a PostToolUse hook that appends tool calls/responses to `.suggestion-box/transcripts/<session-id>.jsonl` for non-Claude Code agents
53+
- [ ] Document the transcript capture integration path clearly
54+
- [ ] Add per-session agent quality scoring based on feedback vote patterns — use it to measure SessionStart prompt quality
55+
56+
---
57+
58+
## v0.6 — Publisher Ecosystem
59+
> Goal: make suggestion-box work wherever teams already live
60+
61+
- [ ] Linear publishing support (team + project required)
62+
- [ ] Design generic publisher backend interface to support future targets
63+
- [ ] Auto-detect issue templates from target GitHub repo, use local fallback when none exist
64+
- [ ] Build reverse sync — poll GitHub/Linear and auto-resolve local feedback when linked issues close
65+
- [ ] Track resolver attribution and build resolution rate metric per target repo/project
66+
- [ ] Design publisher plugin interface so the community can build Jira, Notion, Azure DevOps targets
67+
68+
---
69+
70+
## v0.7 — Distribution & Discoverability
71+
> Goal: get in front of the community while the MCP ecosystem is still sparse
72+
73+
- [ ] Publish to `modelcontextprotocol/registry` at `io.github.igmagollo/suggestion-box`
74+
- [ ] Add `server.json` with proper tags (`feedback`, `ai-agents`, `claude-code`, `developer-tools`)
75+
- [ ] Add a `suggestion-box check` CI command that fails/warns based on unresolved high-vote items
76+
- [ ] Write post framed as "my agents filed their own GitHub issues" targeting Claude Code / Codex communities
77+
- [ ] Write a longer thought leadership piece on "agents as contributors" — stake out the category
78+
79+
---
80+
81+
## v1.0 — Ecosystem Signal
82+
> Goal: become the quality feedback layer for the MCP ecosystem
83+
84+
- [ ] Design opt-in telemetry layer for anonymized MCP tool friction signals only (target identifier + category + timestamp — no content, no repo, no identity)
85+
- [ ] Add `suggestion-box telemetry on/off` command with clear status in `suggestion-box doctor`
86+
- [ ] Open-source the aggregation server
87+
- [ ] Build public dashboard of systemic friction patterns across opted-in users
88+
- [ ] Build public leaderboard of most-reported MCP tool friction across the ecosystem
89+
90+
---
91+
92+
## Post-v1.0 — Sustainability
93+
> Goal: build a model that funds continued development
94+
95+
- [ ] Design B2B analytics tier (MCP tool author monitoring) — avoid architecture decisions that foreclose this path
96+
- [ ] Introduce MCP tool author dashboard: "here is how agents experience your tool across the ecosystem"

0 commit comments

Comments
 (0)