gvm-status

Monitor GVM pipeline status, detecting staleness and tracking build progress.

5|Updated May 4, 2026
One-click install
npx skills add https://github.com/gerquinn1978/gvm --skill gvm-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gvm-status
Source: https://github.com/gerquinn1978/gvm/tree/main/grounded-vibe-methodology/skills/gvm-status
Command: npx skills add https://github.com/gerquinn1978/gvm --skill gvm-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive overview of your GVM pipeline's progress, highlighting completed phases, upcoming tasks, and potential issues, ensuring you stay informed and on track.

Core Features & Use Cases

  • Pipeline Status Overview: Visualize your project's current position in the GVM pipeline.
  • Artefact Detection: Identify completed and in-progress phases based on file system artefacts.
  • Staleness Detection: Flag potential issues where upstream documents have changed after downstream outputs were generated.
  • Expert Activation Summary: Summarize expert engagement and citation rates across phases.
  • Build Progress Tracking: Monitor the progress of the build phase, including completed and pending chunks.
  • Quality Gates: Review the status of quality gates like code review and test results.
  • Methodology Changelog: Provide insights into recent changes and updates to the methodology.

Quick Start

Run the gvm-status command to get an immediate update on your project's GVM pipeline status.

Frequently Asked Questions about gvm-status

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

FAQPage Schema
How do I check my GVM pipeline build progress and status?

You can check GVM pipeline build progress by running a status command that monitors project files and the expert activation log to report completed phases, pending chunks, and overall build health.

How does staleness detection work for upstream documents in a build pipeline?

Staleness detection in a build pipeline flags potential issues where upstream documents have been modified after downstream outputs were generated, ensuring your artefacts remain synchronized and valid.

Can I track artefact completion across pipeline phases using file system outputs?

Yes, artefact detection identifies completed and in-progress pipeline phases by scanning file system artefacts, allowing you to visualize your project's current position and track phase completion.

How do I summarize expert engagement and citation rates across pipeline phases?

You can summarize expert engagement by analyzing the GVM expert activation log, which tracks expert participation and citation rates across the various phases of your pipeline.

Do I need access to project files and activation logs to monitor GVM pipeline health?

Yes, monitoring GVM pipeline health requires access to your project files and the GVM expert activation log to accurately detect artefacts, check staleness, and track build progress.

What is the best way to review quality gates like code review and test results in a pipeline?

The best way to review quality gates is to use a pipeline status tool that tracks code review statuses and test results alongside build progress, providing a comprehensive overview of project health.