plan-task-discipline

Enforce DAG-based task transitions and file scope boundaries in git worktrees.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/getspur/spur --skill plan-task-discipline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-task-discipline
Source: https://github.com/getspur/spur/tree/main/.spur/skills/plan-task-discipline
Command: npx skills add https://github.com/getspur/spur --skill plan-task-discipline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents multi-agent collisions and scope drift by enforcing strict DAG (Directed Acyclic Graph) order and task isolation during complex coding projects.

Core Features & Use Cases

  • DAG Enforcement: Ensures tasks are executed only when dependencies are met, preventing invalid state transitions.
  • Task Isolation: Maintains strict boundaries for file modifications, preventing workers from interfering with each other's worktrees.
  • Use Case: When running multiple coding agents to refactor a large codebase, use this skill to ensure that agents only modify their assigned modules and respect the order of operations defined in the plan.

Quick Start

Activate the plan-task-discipline skill to monitor the current task lifecycle and ensure all agent actions adhere to the defined dependency graph.

Frequently Asked Questions about plan-task-discipline

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

FAQPage Schema
How do I prevent multi-agent coding collisions during a large codebase refactor?

To prevent multi-agent coding collisions, you can enforce strict DAG-based task isolation. This ensures workers only modify assigned files within isolated git worktrees, maintaining dependency awareness and preventing scope drift across complex workflows.

What is DAG enforcement for multi-agent task management?

DAG enforcement for multi-agent task management ensures tasks are executed only when dependencies are met. By validating task status transitions and file scope boundaries, it prevents invalid state transitions and maintains system integrity.

How do I isolate file modifications for parallel coding agents using git worktrees?

You can isolate file modifications by maintaining strict boundaries within isolated git worktrees. This prevents parallel workers from interfering with each other's work and explicitly signals any scope drift to maintain system integrity.

Does DAG-based task orchestration work for complex multi-agent workflows?

DAG-based task orchestration works for complex multi-agent workflows by enforcing strict task lifecycle management. It requires adherence to DAG-based dispatch rules, ensuring agents respect the defined order of operations during execution.

Why does scope drift happen in multi-agent coding workflows and how to stop it?

Scope drift happens when agents modify unassigned files, but you can stop it by enforcing strict task lifecycle management. The system explicitly signals scope drift and validates file scope boundaries within isolated git worktrees to prevent interference.