stay-busy

Generate parallel workstreams with blocked fallbacks and required artifacts.

2|1|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/vosslab/vosslab-skills --skill stay-busy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stay-busy
Source: https://github.com/vosslab/vosslab-skills/tree/main/skills/stay-busy
Command: npx skills add https://github.com/vosslab/vosslab-skills --skill stay-busy

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that work continues even when you're not present, by generating parallel workstreams to keep the project moving forward and producing evidence instead of motion.

Core Features & Use Cases

  • Parallel Workstream Generation: Creates multiple tasks to run in parallel, even when you're not available.
  • Evidence Production: Focuses on generating evidence (e.g., reports, tests, audits) rather than creating motion.
  • Use Case: If you need to step away from a project, you can use this Skill to ensure that work continues in your absence, with the resulting artifacts ready for review upon your return.

Quick Start

/stay-busy

Frequently Asked Questions about stay-busy

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

FAQPage Schema
How do I keep projects progressing with parallel execution when I step away?

To keep projects progressing when you step away, use parallel execution to generate multiple workstreams with blocked fallbacks. This ensures subagents continue executing tasks safely and producing evidence rather than waiting passively.

What is the best way to prevent idle waiting in automated work management?

The best way to prevent idle waiting in work management is to generate parallel workstreams that produce required artifacts. This approach keeps orchestrators busy by ensuring safe, parallel task execution instead of passive waiting.

How does evidence production work in automated project continuity?

Evidence production in project continuity works by generating artifacts like reports, tests, and audits during parallel execution. This ensures that when you return from being away, you have concrete evidence of completed work ready for review.

Do I need a delegate-manager-to-subagents workflow to run parallel workstreams?

Yes, you need a running delegate-manager-to-subagents workflow to generate parallel workstreams. The Skill operates within an approved plan to ensure safe execution and requires this environment to prevent reckless motion.

Can I use this approach for any work management tasks outside an approved plan?

No, you cannot use this approach outside an approved plan. Generating parallel workstreams with blocked fallbacks requires operating within an approved plan to ensure safe execution and prevent reckless motion when you are away.

Why does parallel execution focus on generating artifacts instead of motion?

Parallel execution focuses on generating artifacts instead of motion to ensure project continuity produces verifiable evidence. This prevents reckless action by requiring concrete outputs like reports and tests to be ready upon your return.