A curated list of issues that are well-scoped, well-described, and a good place to start. Grouped by lane (the part of the system you'll touch) and by difficulty (goodFirst is the easiest tier).
If nothing here looks like a fit, search the issue tracker with the good first issue label directly, or open a feature request for something you'd like to build.
How this list is maintained The contributor-onboarding agent grooms inbound issues into lanes and difficulty tiers. Maintainers refresh this list during the monthly recap. If an issue here is already claimed or has gone stale, it'll be re-groomed and either reopened or replaced.
- Comment
/claimon the issue (or just say "I'd like to take this") so we don't double-assign - Run
pnpm dev:cli doctorto verify your environment - Optionally:
pnpm dev:cli contributors groom-issue --number <issue>to get acceptance criteria + lane suggestion from the contributor-onboarding agent - Open a PR using the PR template
See CONTRIBUTING.md for the full flow.
Documentation, READMEs, JSDoc, contributor docs, lessons.
- #615 — fix 5 broken docs links from docs/README.md and ARCHITECTURE.md
- #616 — add JSDoc to spec-097 contributor use-case public interfaces
- No curated issues right now — search docs + easy directly.
- No curated issues right now.
Agent prompts, supervisor flow, agent-agnostic plumbing under tsp/agents/, application/use-cases/agents/, infrastructure/agents/.
- No curated issues right now.
Web dashboard under src/presentation/web/, Storybook stories, Playwright e2e.
- #619 — add Storybook stories for 5 shadcn UI primitives
- #620 — add interaction-state stories for DoctorSummary
- No curated issues right now.
Commander commands, terminal UX, structured output under src/presentation/cli/.
- No curated issues right now.
SQLite, ports/adapters, queues, schedulers, GitHub plumbing under infrastructure/.
- No curated issues right now — search infra + good first issue directly.
It usually means the curated buffer is being refreshed, not that there's nothing to do. Two reliable next steps:
- Search the live tracker for open
good first issuelabels — anything there is fair game. - Drop into Discord and ask "what should I work on?" — a maintainer will route you.
You can also open a Good First Issue yourself if you spot something a future contributor could pick up.
- CONTRIBUTING.md — how to contribute
- ROADMAP.md — what's shipping next
- ARCHITECTURE.md — 10-minute tour of the codebase