Uh oh!
There was an error while loading. Please reload this page.
/split: per-subtask repo routing and two-phase proposals - #3
Merged
Conversation
The agent proposes with a full annotated repo menu (Target repos: narrows it) and a per-subtask repo field; deterministic Ruby enforces reality at apply (App-not-installed fallback with an Intended repo: note, never a silent reroute). --dry stages the proposal as an editable fenced-yaml ## Subtasks section in the plan body; --apply executes exactly that section with no agent call (adopt/reference existing: issues, close stale, fully qualified Depends on:), then rewrites it into a linked map — canonicity transfers to the sub-issues. /build refuses on a staged spec and notes open sub-issues; /build --split skips undrivable nodes with warnings and reports blocked dependents. New docs/commands.md and docs/plan-lifecycle.md are the normative references. Part of #2 Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/splitbecomes plan/apply:--dryruns the one agent pass (full annotated repo menu, per-subtaskrepofield,existing:schema, deterministic# possible match:discovery) and stages an editable fenced-yaml## Subtaskssection in the plan body;--applyexecutes exactly that section with no agent call — create per repo, adopt parentlessexisting:issues / reference parented ones,Intended repo:fallback + warning where the App isn't installed, close stale, fully qualifiedDepends on: owner/repo#n— then rewrites the section into a linked map (canonicity transfers to the sub-issues). Bare/splitdoes both./buildis state-aware on issues: refuses on a staged (unapplied) spec, proceeds with a note when open sub-issues exist./build --splitkeys dependencies byowner/repo#n, skips undrivable nodes (intended-repo fallbacks, adopted/referenced externals from the applied map) with explicit warnings, and reports dependents blocked — including on open external dependencies.docs/commands.md(per-surface reference, refusals verbatim) anddocs/plan-lifecycle.md(end-to-end narrative + body conventions); README/architecture trimmed to pointers.Closes#2
Test plan
bundle exec rake test— 72 tests, 0 failures (new coverage: routing, fallback+warning, dry stages without creating, hand-edited apply without agent, refusals, adopt vs reference, possible-match annotation, skip/block checklist, /build guards)/split --dryon plans#5, hand-edit,--apply, cross-repo children;/buildguard behaviorsMade with Cursor