split-tasks — Task DAG Decomposition & Provenance Slicing

Operating Invariants

• Zero-Persistence Boundary: Never write task files to disk or issues to remote trackers; produce only an in-memory or reviewable Task DAG manifest.
• Vertical Slice Mandate: Partition work strictly into end-to-end vertical slices (1–4 files, 50–150 LOC) with observable acceptance criteria; forbid horizontal technical layering (DB-only or API-only slices).
• Parent Provenance Rigor: Every slice must explicitly trace to its origin (Parent Trace: ADR ID, Feature Slug, or Frozen Contract coordinate); forbid orphan slices.
• Acyclic Dependency Enforcement: Slices must form a directed acyclic graph (DAG); forbid circular dependencies.
• Atomic Bypass: Retain a single unified slice when the input scope already fits within one verification turn (≤ 3 files, single criterion).
• Adaptive Invocation Output: Render the full Markdown table for human review; output a compact JSON DAG when dispatched by an autonomous runner.

Domain Rubric

1. Slicing Sizing & Blast Radius

A slice must be verifiable within one turn of /forge. If a slice spans more than 4 files or touches disparate domain contexts, split it further along independent caller or scenario boundaries.