vc-plan-discovery

Output style: Follow process/development-protocols/communication-standards.md, answer-first, plain language, no unexplained jargon, TL;DR on long responses.

Invocation

Primary method, run the auto-discovery script. It applies the Scope Rules below (same-feature full depth; other features active-only; general-plans active always) and extracts ONLY the leading YAML frontmatter block of each .md file (no whole-file reads):

node .claude/skills/vc-plan-discovery/scripts/discover-plans.mjs [--feature <name>] [--json]

It groups output into Active Plans / Backlog / Completed / Reports / References (each line: - [name]: description (path)) and prints a trailing Found N active, N backlog, N completed, N reports, N references line. It never throws on a missing root and exits 0 unless given a bad flag. Use --json for a machine-readable object. Prefer this over the manual scan below, it is deterministic and avoids loading huge files into context.

Per task-folder artefact colocation, the script scans one level into each {slug}_{date}/ task folder and surfaces co-located _PLAN_/_REPORT_/_REF_ artefacts; the sibling reports//references/ dirs are deprecated and only hold legacy artefacts.

The manual scan in Scope Rules below is the FALLBACK for when the script fails.

Purpose

Surface all plans relevant to the current task so agents have full plan context, what was tried, what is in progress, what is deferred, and what reports and references exist, before doing any phase work.

Scope Rules