vc-plan-discovery

Discovers and groups plan artifacts by scanning frontmatter across feature folders.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/HyuseCS/project-c --skill vc-plan-discovery-hyusecs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-plan-discovery
Source: https://github.com/HyuseCS/project-c/tree/main/.claude/skills/vc-plan-discovery
Command: npx skills add https://github.com/HyuseCS/project-c --skill vc-plan-discovery-hyusecs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Agents starting a task often lack visibility into what plans already exist — what was tried, what is in progress, and what is deferred — leading to duplicated work or missed context. This Skill surfaces all relevant plan artifacts before any phase work begins. ## Core Features & Use Cases - Scoped plan scanning: Reads the same feature folder at full depth (active, backlog, completed, reports, references), other feature folders at active-only depth, and general-plans active always. - Frontmatter-only extraction: Parses only the leading YAML frontmatter block of each Markdown file, avoiding loading large files into context. - Grouped output: Returns plans organized into Active Plans, Backlog, Completed, Reports, and References sections, with a summary count line and an optional JSON mode. - Use Case: At the start of a research or execution loop step, run the discovery script to see every plan related to the current feature, including co-located PLAN, REPORT, and REF artifacts inside task folders. ## Quick Start Run the plan discovery script with the current feature folder name to list all related active, backlog, and completed plans.

Frequently Asked Questions about vc-plan-discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find all plans related to a feature folder?

Run the discover-plans.mjs script with the --feature flag followed by the feature folder name. It scans that folder at full depth plus active plans from other features and general-plans, then prints grouped results.

How to get plan discovery results as JSON?

Pass the --json flag to the discover-plans.mjs script. It outputs a machine-readable object with active, backlog, completed, reports, and references arrays containing paths and parsed frontmatter fields.

Does the plan discovery script read entire Markdown files?

No, it extracts only the leading YAML frontmatter block of each .md file, reading at most the first 80 lines. Files without valid frontmatter are skipped and reported as having no frontmatter.

What happens if a plan directory does not exist?

The script never throws on a missing root directory and exits with code 0. It only fails with exit code 2 when given an unknown or malformed command-line flag.

How are report and reference artifacts classified?

Files are bucketed as reports or references either by living in a reports/ or references/ directory or by having _REPORT_ or _REF_ in the filename, supporting co-located task-folder artifacts.