- Home
- Skills
- Shotaiuchi
- Dotclaude
- Wf0 Nexttask
wf0-nexttask_skill
- Shell
0
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill shotaiuchi/dotclaude --skill wf0-nexttask- SKILL.md2.9 KB
Overview
This skill selects and executes the next pending task from a schedule stored in .wf/schedule.json, respecting task priorities and dependency order. It can preview a task (--dry-run), auto-run until a specified workflow phase (--until), or execute all remaining tasks (--all) with a safety cap. It updates schedule state (running/completed), records timestamps, and reports remaining work.
How this skill works
The skill loads .wf/schedule.json and finds the first pending work whose dependencies are all completed, sorted by priority. It displays task details, lets you choose an execution range (single kickoff, up to a target phase, or complete all), then runs wf1-kickoff and iteratively calls wf0-nextstep until the target phase or completion. It updates the schedule state (started_at, completed_at, progress) and marks the schedule completed when no tasks remain.
When to use it
- Execute the next actionable task from a team schedule while honoring dependencies
- Run just the kickoff or advance a task through specific phases without manual step-by-step calls
- Perform a dry run to inspect the next task and current progress without making changes
- Auto-run multiple tasks in sequence when clearing backlog (use --all with caution)
- Integrate into automation to keep schedule.json state consistent with executed workflows
Best practices
- Ensure .wf/schedule.json exists and is up-to-date (create with wf0-schedule create if missing)
- Use --dry-run before executing unfamiliar tasks to confirm selection and dependencies
- Prefer --until wf6-verify for full task completion when you want a single automated flow
- Use --no-branch when you must avoid creating feature branches during kickoff
- Limit use of --all for large schedules; the command enforces a 50-task safety cap per invocation
Example use cases
- Run the next high-priority task that has all dependencies satisfied and record progress automatically
- Survey the next task with --dry-run before assigning reviewers or resources
- Auto-advance a task to wf4-review to complete design review without manual wf0-nextstep loops
- Batch-execute remaining low-risk tasks with --all to clear backlog (within 50-task safety limit)
- Start work and pause after kickoff by selecting the wf1-kickoff option during the interactive stop prompt
FAQ
The skill errors and suggests creating the schedule (use wf0-schedule create) before proceeding.
How does --until map to workflow phases?
Interactive choices map to phases: wf1-kickoff, wf3-plan, wf4-review, wf6-verify; a final option executes all remaining tasks.