Skip to content

Planboard card dependency chains (card B blocked on card A) #251

Closed

Description

@currentbits

Inspired by Cline's Kanban (dependency chains between cards) and the most-requested missing feature in Vibe Kanban.

Let issues on the Planboard declare 'blocked by' relationships (GitHub's native blocked-by API or a label convention). Blocked cards are visually marked and skipped by auto-dispatch (#165) until their blockers land; unblocking can trigger dispatch automatically.

Activity

  1. currentbits commented on Aug 17, 2026

    @currentbits
    OwnerAuthor

    Deep-dive detail (skills ecosystem): skill-gated pipelines — thread type B cannot start until thread type A's gate artifact exists (a plan file with status Validated). The ecosystem encodes this as pleading markdown; an orchestrator can actually enforce it. Gate = file + status, mapping cleanly onto checkpoints.

  2. currentbits commented on Aug 17, 2026

    @currentbits
    OwnerAuthor

    Deep-dive detail (cadre.rocks): subtask umbrellas — an approved plan decomposes into sequential child tasks with chained worktrees, and the parent card shows roll-up progress. The parent-card roll-up is the piece to add to dependency chains.

  3. added and removed on Oct 11, 2026
  4. added and removed on Oct 11, 2026
  5. currentbits commented on Oct 11, 2026

    @currentbits
    OwnerAuthor

    Landed from Solenta thread "Planboard card dependency chains (card B blocked on card A)" (PR #1586). Closed on merge.

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions