Skip to content

ROADMAP.md

Latest commit

 

History

History
72 lines (50 loc) · 6.8 KB

ROADMAP.md

File metadata and controls

72 lines (50 loc) · 6.8 KB
Raw

Roadmap — claude-team-cli

Living product roadmap. Current priorities and forward bets. Updated by Claude using the roadmap skill.

Current Roadmap

Shipping Now — v2.0

A team you can rely on across sessions, installs, and edits

v1 delivered the roster and the coordinator. v2 closes the gaps that made the team unreliable in daily use: personas leaking between parallel sessions, a profile edit reaching one installed copy out of three, and session context missing entirely because the SessionStart hook registered only through hooks/hooks.json, which needs a plugin runtime that the install.sh path never provides.

  • Session-scoped personas: the /name commands no longer write global state, so parallel sessions never overwrite each other
  • claude-team launch <persona> — a dedicated session with the persona as system prompt, on its tier model, optionally in an isolated worktree
  • Seventeen delegation subagents generated from profiles/, so any session can hand work to a specialist without switching
  • Plugin-shaped layout: commands/, agents/, and hooks/hooks.json sit at the paths Claude Code's plugin system expects, and .claude-plugin/plugin.json describes the package. Publishing to a plugin marketplace is retired, not deferred (see Near-Term). bash install.sh is the install path
  • Worktree-isolated /parallel: session plans create a worktree per session and never switch branches in a shared checkout
  • claude-team sync — one command propagates a profile edit to all three installed copies
  • claude-team install-hook — the SessionStart hook registers by absolute path in settings.json, so it works on the install.sh path instead of only through the plugin manifest
  • Plain technical English standard for the six coding specialists, documented in WRITING.md
  • Slash commands generated from profiles, so a new persona means writing one file instead of three
  • Session handoff briefing: every persona defines a Handoff Brief, the coordinator asks for one at a switch, and it now reaches all four delivery surfaces including the /name slash commands
  • Parallel session prompts carry a Context field, so a session starts from what was already decided instead of re-deriving it
  • Automated test coverage across the CLI commands, both coordinator modes, and the install path, run on Linux and macOS in CI

Shipped — v1.0

The specialist roster, the coordinator, and branch hygiene

  • claude-team coordinator on — casual mode, no branch enforcement
  • claude-team coordinator prod — prod mode, branch required before any code
  • /prod-mode and /casual-mode slash commands for mid-session toggling
  • claude-team status shows active mode: on (casual) or on (prod)
  • Branch hygiene infrastructure: branch start, done, abandon, status, list, guard
  • Session/worktree isolation: session start, done, status, list
  • Test suite covering all CLI commands and both coordinator modes
  • README refactor: casual/prod modes clearly explained, branch hygiene framed as prod-only
  • ROADMAP.md — this file

Near-Term

Local profile overrides are retired, not deferred. They were the top item here through v2. Building them would create a second source of persona truth competing with the repo, and the confusion between core version and local customization costs more than the convenience buys. Team-scoped profiles (claude-team init writing .claude-team/) are retired for the same reason at project scope.

Customizing a persona has two supported paths, both of which keep one source of truth: open a pull request so everyone gets the improvement, or fork and own your copy. See CONTRIBUTING.md.

Slash command generation shipped in v2.0 and is no longer queued. scripts/generate-agents.sh now writes both the delegation subagent and the /name slash command from the profile, so adding a persona means writing one profile.

Marketplace publishing is retired, not deferred. A full packaging plan was built and costed at roughly two days, and the engineering was never the problem. Two structural limits are: the plugin system namespaces commands, so /akira becomes /claude-team:akira, and a plugin cannot put claude-team in the user's shell, only on the Bash tool's path, so launch, session, and the worktree workflow could not ship through it. That is not a subset of the product, it is a different and worse product wearing its name. The layout stays plugin-shaped because it costs nothing, but bash install.sh is the install path.

Aspirational — Looking for Feedback

Nothing is queued here right now. v2.0 shipped or retired everything that was.

That is an invitation, not a finish line. If something about the team gets in your way, or a specialist you need is missing, open an issue. Real usage feedback shapes what gets built next.

Revision History

Date Type Description
2026-04-09 snapshot Initial ROADMAP.md — v0.6 shipping, aspirational backlog identified
2026-07-29 snapshot Renumbered to v2.0 current, v1.0 shipped; pre-release 0.x numbers retired. Corrected test count to 135. Local profile overrides promoted to top priority.
2026-07-29 decision Local profile overrides and team-scoped profiles retired. Both create a second source of persona truth competing with the repo. Supported paths are a pull request or a fork, documented in CONTRIBUTING.md.
2026-07-29 correction Session handoff briefing moved from aspirational to shipped. It was built with the personas and the entry was stale; the real defect was that the brief never reached the /name slash commands. Parallel session prompts gained a Context field. Aspirational list is now empty.
2026-07-31 decision Marketplace publishing retired. A costed packaging plan showed the plugin form cannot deliver /akira (namespaced to /claude-team:akira) and cannot put claude-team in the user's shell, so launch, session, and the worktree workflow are unavailable through it. Shipping a subset under the product's name was judged worse than not shipping it. .claude-plugin/ and hooks/hooks.json stay because the layout costs nothing.
2026-07-31 correction "Plugin packaging: installed in one step" was false and always was. There is no marketplace.json, and a plugin-only install never runs claude-team sync, so the CLI dies in require_profiles_dir. Restated as plugin-shaped layout, matching the wording in README. The same claim was corrected in README on 2026-07-31 but missed here, so the two now share one wording and a CI check asserts no doc claims a marketplace install path while marketplace.json is absent.