schedule-work

Decompose plan files into Jules-sized tasks and register them in the work ledger.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill schedule-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: schedule-work
Source: https://github.com/BedaBeda-Growth/bedabeda-growth-site/tree/main/skills/schedule-work
Command: npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill schedule-work

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Break down a plan into discrete, runnable Jules tasks and register them in a central work ledger, enabling scalable execution.

Core Features & Use Cases

  • Shards plans in plans/ into tasks aligned with repository scope
  • Infers target repo and assigns tasks to the correct owner
  • Enforces structured acceptance criteria and task context for auditing

Quick Start

Shatter a plan file in plans/ into Jules-sized tasks and register each task in the work ledger.

Frequently Asked Questions about schedule-work

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

FAQPage Schema
How do I break a project plan into smaller executable tasks?

Task decomposition works by sharding plan files from the plans/ directory into discrete tasks aligned with repository scope, encoding acceptance criteria and context for deterministic execution alongside ledger registration.

Can I track decomposed tasks automatically in a work ledger?

Yes, tracking decomposed tasks automatically in a work ledger is supported. The skill enforces structured ledger entry creation for each task, encoding acceptance criteria and context to enable auditing and deterministic execution.

How do I generate self-contained tasks with acceptance criteria from a plan file?

You generate self-contained tasks from a plan file by using the skill to shard plan sections, encode acceptance criteria and context, and optionally generate per-task Jules files for deterministic execution.

Does the task decomposition process require specific repository configurations?

The task decomposition process requires a plan file in the plans/ directory and infers the target repository automatically, assigning tasks to the correct owner without needing explicit external dependencies.

What are the limitations of automating task decomposition from plan files?

A limitation of automating task decomposition from plan files is that the skill relies on plan sections for sharding and requires structured input to enforce task sizing and self-contained task generation for deterministic execution.