You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: move nested repo branching to plan-aware, task-driven workflow
Instead of automatically creating branches in all nested repos during
/speckit.specify, this redesign defers branching to the plantasksimplement
workflow:
- Specify phase: creates root branch + spec only (no nested repo work)
- Plan phase: setup-plan.sh discovers nested repos (NESTED_REPOS in JSON)
and the AI agent identifies affected modules from the spec
- Tasks phase: generates a Phase 1 setup task for creating feature branches
in only the affected nested repos identified by the plan
- Implement phase: executes the branch-creation task via git commands
Changes:
- Revert create-new-feature.sh/.ps1: remove --repos, --scan-depth, and
NESTED_REPOS output (specify phase is clean again)
- Add nested repo discovery to setup-plan.sh/.ps1 with --scan-depth flag
- Update plan.md template: add step for AI to identify affected repos
- Update plan-template.md: add Affected Nested Repositories section
- Update tasks.md command: guidance for generating branch-creation task
- Update tasks-template.md: Phase 1 example for nested repo branching
- Update specify.md: remove nested repo guidance, point to plan+tasks
- Rewrite tests: 13 tests covering discovery, depth config, setup-plan
output, and verification that specify phase doesn't branch nested repos
Resolves the concern that at specify time the spec doesn't exist yet,
so we cannot know which repos are affected. The AI agent now makes this
determination during planning based on spec analysis.
Refs: #2120
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
0 commit comments