crank

Automate epic orchestration across beads, TaskList, and swarm-enabled workflows.

418|40|Updated Nov 5, 2025
One-click install
npx skills add https://github.com/boshu2/agentops --skill crank
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crank
Source: https://github.com/boshu2/agentops/tree/main/skills/crank
Command: npx skills add https://github.com/boshu2/agentops --skill crank

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates epic orchestration to drive waves of tasks to completion without human prompts, coordinating multiple tools and modes.

Core Features & Use Cases

  • Autonomous epic orchestration: manage planning, execution, monitoring, and final vibe validation across tools like swarm, vibe, implement, beads, and post-mortem.
  • Wave-based parallelism: spawn multiple workers per wave with fresh context to maximize throughput while avoiding data bleed.
  • Validation-driven closure: perform a final vibe across changes and automatically sync results back to beads or TaskList.
  • Use Case: Imagine an epic with several interdependent tasks; crank coordinates the entire lifecycle from planning to completion with minimal manual prompts.

Quick Start

Use the crank skill to start an epic workflow locally. Provide a plan file or beads tasks, e.g., /crank <epic-id> or /crank plan.md.

Frequently Asked Questions about crank

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

FAQPage Schema
How do I automate epic orchestration to run tasks to completion without manual prompts?

Autonomous epic orchestration coordinates planning, execution, monitoring, and validation across tools like swarm and beads to drive tasks to completion without human prompts. It manages the entire lifecycle from initial planning to final vibe validation automatically.

What is wave-based parallel execution and how does it maximize workflow throughput?

Wave-based parallel execution spawns multiple workers per wave with fresh context to maximize throughput while avoiding data bleed. This parallelism allows independent tasks within an epic to run simultaneously, significantly reducing overall execution time.

How do I start an autonomous epic workflow using a plan file or task list?

Start an autonomous epic workflow by providing a plan file or beads tasks to the crank skill, using a command like /crank <epic-id> or /crank plan.md. The system then coordinates the entire task lifecycle from planning to final validation.

Does epic orchestration work with beads and TaskList for syncing validation results?

Epic orchestration works directly with beads and TaskList, automatically syncing validation results back to these tools. Validation-driven closure performs a final vibe across changes and updates the task tracking systems to reflect completion status.

Can I coordinate interdependent tasks across multiple workers without data bleed?

Coordinating interdependent tasks across multiple workers without data bleed is achieved through wave-based parallelism. Each worker operates with fresh context per wave, maximizing throughput while isolating task execution to prevent cross-contamination of data.

What are the limitations of autonomous epic execution for complex task workflows?

Autonomous epic execution requires a provided plan file or beads tasks to initiate, and depends on coordinating tools like swarm, vibe, and post-mortem for full lifecycle management. Complex interdependent tasks must be structured into waves to avoid data bleed during parallel execution.