Skip to content

Add implementation planning with PR-sized work, dependencies, sizing, and rollout metadata #1651

Closed

Description

@bradygaster

Parent epic: #1648

Outcome

Add /squad plan implementation to turn an accepted program plan into executable leaf work.

Each leaf includes outcome, scope/non-scope, parent, affected components, real dependencies, acceptance criteria/tests, migration impact, rollout/rollback guidance, evidence requirements, relative size, uncertainty, and expected PR boundary.

Prefer a GitHub Project size field when configured. Otherwise embed structured Size: XS–XL metadata; do not create size labels automatically.

Acceptance criteria

  • XL leaves are rejected or explicitly waived.
  • Dependencies use native GitHub relationships when available.
  • Parallel work and sequencing are explicit.
  • Cross-cutting work is decomposed rather than emitted as omnibus issues.
  • The first ready execution wave is unambiguous.

Size: L

Activity

  1. added
    squadSquad triage inbox — Lead will assign to a member
    gh-awGitHub Agentic Workflows integration
    on Aug 8, 2026
  2. bradygaster commented on Aug 8, 2026

    @bradygaster
    CollaboratorAuthor

    E2E evidence: native dependencies unused and sizing fallback creates labels

    Tested SHA: 47e04dc73663cba40b47f00dd8e2ac42c37f6419
    Consumer: https://github.com/bradygaster/squad-planning-e2e
    Implementation run: https://github.com/bradygaster/squad-planning-e2e/actions/runs/31241499516
    Activation run/artifacts: https://github.com/bradygaster/squad-planning-e2e/actions/runs/31242960785

    Prerequisites

    No Project V2 is configured. GitHub native issue dependency fields/APIs are available (blockedBy, blocking, and issue dependency summaries all query successfully).

    Reproduction

    Activate the accepted 18-task implementation plan from https://github.com/bradygaster/squad-planning-e2e/issues/2.

    Expected

    • Use native blocked-by relationships where supported.
    • With no Project Size field, use structured Size: XS|S|M|L|XL fallback metadata and do not create size labels.
    • Keep the first executable wave explicit.

    Actual

    Impact

    GitHub cannot enforce or visualize execution blocking natively, dependency-aware automation cannot consume real edges, and the no-Project sizing fallback pollutes repository labels instead of using the documented structured representation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    gh-awGitHub Agentic Workflows integrationpriority:p1This sprintsquadSquad triage inbox — Lead will assign to a membertype:featureNew capability

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions