wf0-schedule_skill

Overview

This skill provides schedule management for batch workflow execution with built-in dependency analysis and validation. It creates schedules from multiple sources (GitHub, Jira, local lists), stores a canonical schedule file, and enforces execution order based on priorities and dependencies. The tool helps teams run batch workflows reliably by detecting cycles and unresolved references before execution.

How this skill works

The skill fetches work items from configured sources and normalizes them into work-ids. It parses common dependency patterns in issue bodies to build a dependency graph, assigns priorities, validates the graph for cycles and missing references, and saves the schedule to .wf/schedule.json. Commands are available to show, edit, validate, and clear the schedule.

When to use it

• Prepare a batch run from multiple issue trackers or local task lists
• Detect and resolve dependency cycles before executing workflows
• Generate a prioritized execution plan that respects inter-work dependencies
• Audit current schedule status and progress across all works
• Quickly adjust priority or dependencies for a specific work

Best practices

• Use consistent dependency phrases in issue bodies (e.g., "depends on #N", "requires PROJ-N") for reliable detection
• Keep priorities numeric (1 highest to 10 lowest) and document team conventions in config.json
• Run validate after create or edit to catch cycles and unresolved references early
• Store schedule in version control or backup .wf/schedule.json for auditability
• Provide minimal, clear dependency lists to avoid unnecessary coupling between works

Example use cases

• Create a schedule from GitHub issues labeled scheduled and validate before a nightly batch run
• Combine Jira sprint items with local fixes to form a single execution plan
• Edit a work to raise its priority when a hotfix needs earlier processing
• Detect circular dependencies introduced by cross-references and resolve them before execution
• Clear the schedule to start a new batch planning cycle