Shared design references for all GVM skills. Not invoked directly by users — other skills load its reference files at runtime. Contains the Tufte/Few HTML design spec, expert reference files, shared rules, pipeline contracts, and scoring methodology. For…
Use when creating or revising documents — presentations, strategy documents, newsletters, training materials, status reports, whitepapers, any prose document, or pipeline documentation (README, CHANGELOG, user guides, API docs). Triggered by /gvm-doc-write…
Use when initialising the Grounded Vibe Methodology for a new project, especially in specialised domains (financial services, healthcare, regulated industries). Triggered by /gvm-init command or requests to calibrate experts. Optional for general-purpose…
Use when gathering, refining, or fleshing out requirements for a new project or feature. Triggered by /gvm-requirements command, rough project descriptions needing structure, or requests to create a requirements document.
Use when working with an existing codebase for the first time, before making changes. Triggered by /gvm-site-survey command, requests to assess or evaluate a codebase, or requests to understand an existing system's architecture. Explores the codebase,…
Use when generating test cases from a requirements document produced by /gvm-requirements. Triggered by /gvm-test-cases command, requests to create acceptance tests, or requests to verify requirements coverage.
Privacy-preserving exploratory data analysis. Claude orchestrates a Python engine that reads the user's data, produces a grounded findings report with headline insights, provenance, and a methodology appendix. Raw rows never enter Claude's context.
Use when implementing code from a /gvm-tech-spec implementation guide. Triggered by /gvm-build command, requests to build/implement a chunk or phase, or requests to start coding from specs. Reads the implementation guide, generates per-chunk prompts, executes…