convoy-spec

Draft bead-ready docs into convoys and tasks with dependency graphs.

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/naramore/dotai --skill convoy-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convoy-spec
Source: https://github.com/naramore/dotai/tree/main/claude/skills/convoy-spec
Command: npx skills add https://github.com/naramore/dotai --skill convoy-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Decomposition of bead-ready docs into a coordinated convoy + tasks, enabling consistent governance, holdout planning, and cross-backend encoding across beads or Linear.

Core Features & Use Cases

  • Provides a structured framework to draft bead-ready docs and decompose them into a convoy with child tasks.
  • Defines metadata vocabulary and workflow rules for cross-team coordination and auditing.
  • Use case: break PRD-level work into a convoy with dependent tasks and holdout criteria for rapid, auditable execution.

Quick Start

Draft a bead-ready document, then decompose it into a convoy and tasks.

Frequently Asked Questions about convoy-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decompose a PRD into auditable cross-backend tasks?

Decomposing a PRD into auditable tasks requires drafting bead-ready docs and breaking them into a convoy with child tasks. This ensures dependency graphs and backend encoding are consistently produced for cross-backend coordination.

What is a convoy in workflow decomposition and when do I need it?

A convoy in workflow decomposition is a structured framework coordinating complex, multi-item projects. You need it when breaking down roadmap items into dependent tasks with holdout criteria for rapid, auditable execution.

Can I use Linear for convoy-based task coordination?

Yes, Linear is supported for convoy-based task coordination. The framework defines metadata vocabulary and workflow rules ensuring consistent governance, holdout planning, and cross-backend encoding across Linear.

What's the best way to plan holdout-driven roadmaps across multiple backends?

The best way to plan holdout-driven roadmaps is drafting bead-ready docs and decomposing them into a convoy. This approach consistently produces convoy-task metadata and dependency graphs for cross-backend coordination.

How do I structure dependency graphs for multi-item project roadmaps?

Structuring dependency graphs for multi-item projects involves decomposing bead-ready docs into a convoy with dependent tasks. This method ensures metadata vocabulary and backend encoding remain consistent and auditable.

Why does cross-backend coordination fail without consistent metadata?

Cross-backend coordination fails without consistent metadata because task dependencies and holdout criteria lack governance. Defining a metadata vocabulary within a convoy framework prevents these inconsistencies and enables auditable execution.