All skills
task-dag-planner
ProfessionalRuntime top levelanalysis-agent: plan dependencies between semantic tasks that need ordering, integration or independent work; skip single edits and established plans.
- Group
- Intake, analysis and planning
- Routing mode
- evidence-only
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- explicit Task DAG request
- multiple tasks with a real dependency parallel benefit integration need or release order
Do not use when
Anti-triggers — as binding as the triggers above
- single bounded edit
- existing dependency plan already resolves coordination
- no useful decomposition or dependency question
Required inputs
What must be supplied before this skill can decide anything
- clear goal and important decisions
- current source evidence
- work owners and dependency boundaries
- write coordination requirements
Output contract
What this skill owes the next role
- bounded tasks with needed expertise
- actual dependency edges
- integration order
- validation and unresolved questions
Escalation signals
When this skill must hand the decision back
- scope, authority, or material risk exceeds the selected task contract
Related expertise
2 Layer 3 candidates may be loaded behind this skill — each only when the current task's evidence calls for it, never as a bundle.
Targeted references
Each reference carries its own load condition. None of them enter context by default.
| Reference | Load when | Do not load when | Required by |
|---|---|---|---|
| checklist.mddecision-checklist | A bounded review needs a quick DAG readiness and closure checklist | Detailed evidence map or executable node contract is required | Analysis |
| index.mdindex | competing task dag planner references require dependency, conflict, or output-fragment selection | the task dag planner root or a task-named reference already resolves selection | Analysis |
| planning-evidence-patterns.mdevidence-pattern | Closing graph validity, new-hypothesis, parallelization, rollback, or plan-execution consistency | Only task field shape is needed | Analysis |
| task-contract-patterns.mdbenchmark-pattern | Nodes must be executable by a fresh implementer or placeholder tasks need replacement | Existing task contracts already name exact scope, behavior, validation, and residual risk | Analysis |