impact

Draft Impact: Track Telemetry & Analytics

Generate a project-wide impact report measuring Context-Driven Development effectiveness across all tracks.

Red Flags - STOP if you're

• Profiling code coverage instead of measuring track-level impact.
• Rewriting tracker logic when local state objects are available for inspection.
• Generating reports without reading existing track metadata first.

---

Execution Constraints

First resolve the bundled helpers:

# Locate Draft's bundled helpers (cwd is the user's project; ${CLAUDE_PLUGIN_ROOT}
# is not exported into skill Bash). See core/shared/tool-resolver.md.
DRAFT_TOOLS="${DRAFT_PLUGIN_ROOT:-$(cat ~/.cache/draft/plugin-root 2>/dev/null)}/scripts/tools"
[ -d "$DRAFT_TOOLS" ] || DRAFT_TOOLS="$(ls -d ~/.claude/plugins/cache/*/draft/*/scripts/tools 2>/dev/null | sort -V | tail -1)"
[ -d "$DRAFT_TOOLS" ] || DRAFT_TOOLS="$(ls -d ~/.claude/plugins/marketplaces/*draft*/scripts/tools 2>/dev/null | tail -1)"
[ -d "$DRAFT_TOOLS" ] || DRAFT_TOOLS="$PWD/scripts/tools"

1. Load Track State:

   • Read all draft/tracks.md entries.
   • For each track, read metadata.json to extract: created_at, updated, status, phase counts, task counts, scope_includes, scope_excludes.
   • If no tracks exist, report "No tracks found. Run /draft:new-track to create your first track."
   • Run "$DRAFT_TOOLS/check-scope-conflicts.sh" to surface adjacent tracks sharing scope tags — duplicate effort signals in impact reporting. Schema: core/shared/template-contract.md.

2. Compute Metrics:

   • Delivery Pace: Average elapsed time from track creation to completion (planning → implementation → review).
   • Phase Duration: Time spent in each phase (planning, implementation, review). Flag any phase exceeding 14 days without updates.
   • Completion Rate: Ratio of completed tracks to total tracks.
   • Task Granularity: Average tasks per track. Flag tracks with fewer than 3 tasks (under-decomposed) or more than 30 (over-decomposed).