v-model

Map V-model requirements to verification tests as a navigable skill-tree.

Updated Jan 5, 2025
One-click install
npx skills add https://github.com/pkuppens/pkuppens --skill v-model
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: v-model
Source: https://github.com/pkuppens/pkuppens/tree/main/skills/v-model
Command: npx skills add https://github.com/pkuppens/pkuppens --skill v-model

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligns requirements, architecture, and verification activities by applying a structured V-model overlay across SKILL_TREE skills for traceability in Agile and brownfield contexts.

Core Features & Use Cases

  • Provides a framework to map left-arm artefacts (requirements, analysis, architecture) to right-arm verification (tests, acceptance criteria) across multiple sub-skills.
  • Supports retrofitting and incremental V-model adoption in existing codebases and projects.
  • Guides decision-making with explicit mapping between artefacts and verification signals (contract tests, unit tests, acceptance criteria).

Quick Start

Apply v-model to a feature by mapping its requirements to unit tests and documenting the traceability.

Frequently Asked Questions about v-model

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

FAQPage Schema
How do I map V-model traceability to requirements and tests in an Agile workflow?

V-model traceability maps left-arm artefacts like requirements and architecture to right-arm verification signals such as unit tests and acceptance criteria. This structured overlay aligns Agile slices by enforcing explicit artefact-to-verification mapping across sub-skills.

Can I retrofit V-model traceability into an existing brownfield codebase?

Yes, V-model traceability supports brownfield retrofits by applying incremental V-model adoption to existing codebases. The framework guides mapping established project artefacts to their corresponding verification signals without requiring a full system rewrite.

What is the best way to enforce explicit mapping between architecture and integration tests?

The v-model-architecture-integration sub-skill enforces explicit mapping between architecture artefacts and integration verification. It structures the traceability links by connecting design-level components directly to their corresponding integration test signals.

Does V-model traceability work for compliance scenarios requiring strict artefact verification?

V-model traceability applies directly to compliance scenarios by enforcing explicit artefact-to-verification mapping. It provides a navigable skill-tree across requirements and tests, ensuring documented traceability for audit purposes.

How do I document traceability when mapping feature requirements to unit tests?

Apply V-model traceability by mapping your feature requirements to unit tests and documenting the connections. The v-model-requirements-acceptance and v-model-implementation-unit sub-skills structure this mapping between analysis artefacts and verification signals.