schedule

Schedule work orders from backlog, plan phases, and session history.

218|11|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/poteto/noodle --skill schedule-poteto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: schedule
Source: https://github.com/poteto/noodle/tree/main/.agents/skills/schedule
Command: npx skills add https://github.com/poteto/noodle --skill schedule-poteto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams avoid manual, error-prone backlog juggling by automatically scheduling work orders using backlog state, plan phases, and session history.

Core Features & Use Cases

  • One-plan-at-a-time scheduling: prioritizes a single plan's remaining phases to finish end-to-end.
  • Deterministic orders: outputs orders-next.json and promotes it atomically to orders.json, avoiding direct writes to orders.json.
  • Schema-driven: uses mise and orders schemas as the source of truth for task types and plans.

Quick Start

Load the current backlog, run the scheduler, and observe it writing orders-next.json for subsequent promotion.

Frequently Asked Questions about schedule

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

FAQPage Schema
How do I automate work order scheduling for a backlog-driven project?

Automate work order scheduling by evaluating backlog state, plan phases, and session history to determine the next set of actions. The scheduler outputs orders-next.json and promotes it atomically to orders.json, ensuring deterministic progression without manual juggling.

How does deterministic order generation prevent manual backlog juggling?

Deterministic order generation prevents manual backlog juggling by using backlog state and session history to output orders-next.json, then atomically promoting it to orders.json. This avoids direct writes and ensures a single plan drives the next actions.

Can I use this scheduler for cross-team infrastructure tasks?

Yes, you can use this scheduler for cross-team infrastructure tasks. It applies to backlog-driven projects and cross-team initiatives by prioritizing a single plan's remaining phases to execute end-to-end, ensuring deterministic progression.

Do I need specific schemas to orchestrate workflow phases?

Yes, you need mise and orders schemas to orchestrate workflow phases. The scheduler uses these schemas as the source of truth for task types and plans, ensuring deterministic progression when evaluating backlog and session history.

What is the best way to prioritize one plan at a time during orchestration?

The best way to prioritize one plan at a time is to let the scheduler evaluate remaining phases and session history. It focuses on finishing a single plan end-to-end before moving to the next, outputting orders-next.json for atomic promotion.

Why does the scheduler write to orders-next.json instead of orders.json directly?

The scheduler writes to orders-next.json instead of orders.json directly to ensure atomic promotion and avoid race conditions. This mechanism guarantees deterministic progression by evaluating backlog and plan phases before updating the source of truth.