vc-plan-discovery

Scan directories for plans and group YAML frontmatter from .md files into categories.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/tutran27/trust-room-AI --skill vc-plan-discovery-tutran27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-plan-discovery
Source: https://github.com/tutran27/trust-room-AI/tree/main/.agents/skills/vc-plan-discovery
Command: npx skills add https://github.com/tutran27/trust-room-AI --skill vc-plan-discovery-tutran27

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The vc-plan-discovery skill simplifies the discovery process of related plans and artifacts for the current task, providing agents with a comprehensive context before initiating any phase of work.

Core Features & Use Cases

  • Auto-discovery Script: Executes a script that scans directories for plans and artifacts based on specified rules.
  • Scope Rules: Reads plan files and groups them into active plans, backlog, completed, reports, and references.
  • Purpose: To surface all plans relevant to the current task, providing agents with full context for planning and decision-making.

Quick Start

Invoke the skill by specifying the feature folder name or task description: vc-plan-discovery [feature folder name or task description]

Frequently Asked Questions about vc-plan-discovery

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

FAQPage Schema
How do I automatically discover related plans and artifacts for a current project management task?

To automatically discover related plans and artifacts for a current task, you can use an auto-discovery script that scans directories and groups files into active plans, backlog, completed, reports, and references based on specified rules.

How does artifact analysis work when reading YAML frontmatter from markdown files?

Artifact analysis reads YAML frontmatter from .md files to extract task context, grouping the markdown documents into distinct categories like active plans and references to provide comprehensive project context.

Can I organize project documents into active plans and backlogs based on custom scope rules?

Yes, you can organize project documents into categories like active plans and backlogs by applying specified scope rules that read plan files and group them according to their frontmatter metadata and current task relevance.

What is the best way to provide agents with full task context before initiating project work?

The best way to provide full task context is to surface all relevant plans and artifacts beforehand, ensuring agents read grouped YAML frontmatter data from markdown files for comprehensive planning and decision-making.

Does plan discovery require any external dependencies to scan directories for project artifacts?

No, plan discovery requires no external dependencies to scan directories for project artifacts; it executes as a standalone script that reads markdown files and categorizes them based on internal scope rules.