grounded-vibe-methodology

Plugin grounded-vibe-methodology from marketplace gvm-marketplace in gerquinn1978/gvm. Commands read from the repo's manifest — 1 month ago.

Skills (19)

• gvm-analysis

  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.

• gvm-build

  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 with strict TDD, reviews against best pr

• gvm-code-review

  Use when reviewing implementation code for quality, security, and spec adherence. Triggered by /gvm-code-review command, requests to review code, or after completing a build phase. Dispatches parallel defect-class panels as subagents, grounded in the project's spec-declared specialists.

• gvm-deploy

  Use when preparing a release — version bump, release notes, documentation accuracy check, changelog, and git tag. Triggered by /gvm-deploy command, requests to prepare a release, cut a version, or generate release notes. Does NOT execute deployment — that is organisation-specific.

• gvm-design-review

  Use when reviewing whether a design (data model, UI/UX, API) correctly fulfils requirements. Triggered by /gvm-design-review command, requests to review a database schema against requirements, check if a UI covers all user journeys, or verify API contracts. Also triggered by /gvm-site-survey when it

• gvm-design-system

  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 expert scoring and roster management, use /gv

• gvm-doc-review

  Use when reviewing documents for quality. Triggered by /gvm-doc-review command, requests to review or audit a document, or requests to check document quality. Dispatches parallel defect-class panels (Structure, Traceability, Content Quality, Scoring) as subagents. Auto-detects document types, presen

• gvm-doc-write

  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 command, requests to create documentation,

• gvm-experts

  Use when the user wants to score, rescore, or manage experts in the GVM roster. Triggered by /gvm-experts command, requests to score experts in a reference file, rescore an expert, evaluate expert authority, add experts, or score all industry domain experts.

• gvm-explore-test

  Use when running a timeboxed exploratory testing charter against built code, before doc-write. Triggered by /gvm-explore-test command or requests to run an exploratory tour, log defects in GWT form, or produce an explore-NNN session report. Writes a charter, drives AskUserQuestion-based defect intak

• gvm-impact-map

  Use when discovering goals, actors, impacts, and deliverables for a new project or feature, before requirements gathering. Triggered by /gvm-impact-map command or requests to map impact, identify outcomes, or trace a goal to deliverables. Produces impact-map.md (four linked tables) that downstream /

• gvm-init

  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 software — the pipeline discovers and scores

• gvm-requirements

  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.

• gvm-site-survey

  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, diagnoses architectural state, selects grounding

• gvm-status

  Use when the user wants to know where they are in the GVM pipeline, what phases are complete, what's next, or the overall health of their project's methodology state. Triggered by /gvm-status command or questions like "where am I?", "what's done?", "what's next?".

• gvm-tech-spec

  Use when creating technical specifications from a requirements document. Triggered by /gvm-tech-spec command, requests to create a tech spec, or requests to design system architecture. Reads requirements and test cases, produces multiple focused spec documents with adaptive decomposition based on pr

• gvm-test-cases

  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.

• gvm-test

  Use when verifying a completed build — integration seam audit, full code review, startup verification, smoke testing, and stub audit. Triggered by /gvm-test command, requests to verify the build is complete, or after the last chunk of /gvm-build finishes. This is the acceptance gate between "code ex

• gvm-walking-skeleton

  Use when wiring a thin end-to-end execution thread through every external integration boundary before feature work begins. Triggered by /gvm-walking-skeleton command or requests to set up a walking skeleton, wire integration boundaries, or create boundaries.md. Produces a runnable skeleton that exer

Similar plugins