Coordinate shipping of interdependent Trello cards with parallelization and automatic status updates.
npx skills add https://github.com/semanticpixel/abc --skill ship-epic
Please help me install this Agent Skill. Skill: ship-epic Source: https://github.com/semanticpixel/abc/tree/main/plugins/abc/skills/ship-epic Command: npx skills add https://github.com/semanticpixel/abc --skill ship-epic
Coordinating a multi-repo Linear epic is slow when sub-issues must be handled serially instead of being shipped in parallel once dependencies are satisfied.
blocks / blocked by so downstream workers only start when upstream sub-issues are merged./loop 6m /abc:ship-issue <SUB-ID> workers for every sub-issue that is ready, enabling true parallel shipping.<!-- ship-epic:status --> snapshot comment and driving terminal outcomes (complete/halt) based on worker states.Run the skill by passing a Linear parent issue ID or URL to start a parallel shipping coordinator for that epic.
High-intent search queries and answers about installing and using this skill.
To ship Linear epics in parallel across repos, this skill builds a dependency graph from blocks and blocked-by relations, firing independent worker loops only for ready sub-issues once upstream blockers are merged.
Dependency gating for Linear issue execution works by mapping blocks and blocked-by relations into a dependency graph, ensuring downstream worker loops only start after their upstream sub-issue blockers are successfully merged.
Yes, this skill uses Linear MCP tools to fetch issues and comments, aggregating live progress onto the parent epic by appending a status snapshot comment and driving terminal outcomes based on worker states.
Yes, cron orchestration is required to self-arm the skill via loop and manage state. It uses CronList to read state and CronDelete to terminate workers, applying idempotent cron matching to avoid duplicate arming.
If an upstream blocker fails to merge, the dependency graph prevents downstream worker loops from firing, keeping the epic-level source of truth intact while halting dependent sub-tasks until the blocker resolves.
Use parallel epic coordination when feature delivery workflows contain sub-tasks spanning multiple repositories that can progress concurrently once their specific upstream blockers are merged, avoiding slow serial handling.
semanticpixelConvert PLAN-*.md files into Linear parent issues and ordered sub-issues with dependency relations.
semanticpixelCoordinate parallel GitHub epic shipping via managed sub-issue task lists.
neubigDelegate parallel tasks to sub-agents via DelegateTool or OpenHands Cloud API.
OmniNode-aiDecompose Linear epic descriptions into actionable sub-tickets with repository assignments.