Skip to content

Add continuum objective one-command workflow#41

Merged
00PrabalK00 merged 1 commit into
mainfrom
feat/objective-command
May 30, 2026
Merged

Add continuum objective one-command workflow#41
00PrabalK00 merged 1 commit into
mainfrom
feat/objective-command

Conversation

@00PrabalK00
Copy link
Copy Markdown
Owner

@-

Strategy §8.2 / Gap1: Continuum read like a toolkit, not a daily
workflow. `continuum objective "<goal>"` turns one objective into a
coordinated, controlled multi-agent plan by composing existing
primitives -- it adds no new state machine of its own.

- New continuum/objective.py thin planner reuses the route classifier
  (TeamManager.classify/explain) for task-type + lane inference and
  WorktreeManager.schedule for --mode schedule (overlapping-lane
  rejection, dependency edges, file ownership and context packets are
  enforced there, not duplicated).
- New `objective` subcommand with --task-type, --agent, --path,
  --depends-on, --tests, --review-policy, --mode {plan,schedule},
  --execute and --json. Output styled like status/route explain:
  plan + lanes + dependency timeline + NEXT COMMANDS.
- plan mode creates tasks + next-commands without worktrees when no
  paths are given; schedule mode creates branches/worktrees/packets for
  lanes that own paths and task-only for the rest. --execute refuses
  gracefully (exit 1, no traceback) when an agent provider is disabled.
- tests/test_objective.py (8 tests) covers plan/schedule/json/overlap/
  execute-refusal, reusing the git-identity setUp from test_worktrees.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@00PrabalK00 00PrabalK00 merged commit d93bef5 into main May 30, 2026
12 checks passed
@00PrabalK00 00PrabalK00 deleted the feat/objective-command branch May 30, 2026 18:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant