Roadmap: what's coming and where we'd love help

[chacosoldier]

Pinned. This is the public state of where Compabob is going. Updated as things land.

In progress

• CI smoke test + maintenance signals (PRs chore: CI smoke test, FUNDING.yml, fix memory-search status #5, docs: badges, alternatives section, CHANGELOG #6). Weekly fresh-clone CI on Ubuntu, badges row, CHANGELOG, FUNDING.yml. Removes "looks abandoned" risk between maintenance passes.
• Animated terminal demo (replacing the static docs/assets/demo.png with a vhs .tape + GIF). Single biggest README upgrade left.
• memory-search hardening — the module ships, but the docs and the second-brain agent hand-off could be tighter.

Wanted (open to contribution)

These are all open issues, tagged good first issue. Pick one and go:

• Add a 'researcher' persona preset (academia / R&D) #7 — Add a researcher persona preset (academia / R&D).
• Add a /weekly-review skill #8 — Add a /weekly-review skill.
• Document how to swap the default Claude model #9 — Document how to swap the default Claude model.
• Translate the README intro to Spanish #10 — Translate the README intro to Spanish.
• Add a Linux-specific troubleshooting note for the full walkthrough #11 — Add Linux-specific troubleshooting notes.

Other ideas that are not yet issues but would be welcome PRs:

• An evaluator agent that reviews drafts (LinkedIn posts, emails, doc edits) against a small rubric before they go out.
• A sales-coach skill for outreach drafting (pairs with the linkedin-outreach module).
• A project-manager agent for multi-week initiatives with status snapshots.
• Additional persona presets: PM, designer, marketer, ops, data scientist.
• More integrations in the scripts/integrations-catalog.json picker (suggestions welcome).

Considered but not doing (right now)

• Team / multi-user mode. A shared variant with org / department / user tiers is on hold. There is an employer-IP constraint on the maintainer side (context); when that is resolved this comes back.
• WhatsApp channel. Account-ban risk is real and the user-experience win over Telegram is marginal. Use Telegram. The placeholder module exists as a deliberate "no, here's why."
• Telemetry of any kind. Not now, not later. The kit runs entirely on your machine.

How to contribute

See CONTRIBUTING.md. One change per PR; CI must pass; no real names, emails, or company data in the diff. Issues and PR templates are wired.

Watching this issue

If you have a strong feature ask that is not on this list, open a separate issue with the enhancement label. This one is the high-level map; specific work lives in its own ticket.