From harness-engineering
Split an annotated design document into micro-tasks in tasks.json. Use when user says "split", "break down", "create tasks", "generate tasks", or after a design.md has been annotated and the user runs /split. This is the third phase of Track 2.
npx claudepluginhub emingenc/harness-engineering --plugin harness-engineeringThis skill uses the workspace's default tool permissions.
Convert an annotated design.md into a structured tasks.json with explicit
Implements structured self-debugging workflow for AI agent failures: capture errors, diagnose patterns like loops or context overflow, apply contained recoveries, and generate introspection reports.
Monitors deployed URLs for regressions in HTTP status, console errors, performance metrics, content, network, and APIs after deploys, merges, or upgrades.
Provides React and Next.js patterns for component composition, compound components, state management, data fetching, performance optimization, forms, routing, and accessible UIs.
Convert an annotated design.md into a structured tasks.json with explicit dependencies. This enables micro-separated execution where each task is completable in <50% context.
Before splitting:
workspace/designs/<!-- ANNOTATION: ... --> commentsIf annotations are missing, tell the user to annotate first.
python3 ${CLAUDE_PLUGIN_ROOT}/skills/planner/scripts/validate_plan.py \
"workspace/designs/<name>-design.md"
Check that:
annotation_count > 0 (refuse if no annotations)python3 ${CLAUDE_PLUGIN_ROOT}/skills/task-splitter/scripts/split_tasks.py \
"workspace/designs/<name>-design.md"
This script:
python3 ${CLAUDE_PLUGIN_ROOT}/skills/task-splitter/scripts/validate_tasks.py
Checks tasks.json against the schema at docs/templates/tasks-schema.json.
Show the user:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/progress.py append "Tasks split: N tasks from <name>-design.md"
Input: "/split" (after annotating auth-design.md) Process: