Backfill V-model traceability into brownfield codebases with retrofit artifacts.
npx skills add https://github.com/pkuppens/pkuppens --skill v-model-retrofit
Please help me install this Agent Skill. Skill: v-model-retrofit Source: https://github.com/pkuppens/pkuppens/tree/main/skills/v-model/v-model-retrofit Command: npx skills add https://github.com/pkuppens/pkuppens --skill v-model-retrofit
Brownfield codebases often lack V-model traceability, making changes risky and hard to audit. This skill provides two modes to retrofit traceability without a big-bang rewrite.
Define the retrofit scope and initiate explicit V-model retrofit to backfill traceability in the target module.
High-intent search queries and answers about installing and using this skill.
V-model traceability retrofits target specific modules or bounded contexts by creating explicit artifacts like acceptance criteria and ADR notes. This approach backfills traceability incrementally, applying minimal changes to areas identified by issues rather than rewriting everything.
Explicit retrofit mode is triggered by a dedicated issue to backfill traceability for a named scope, while touch-driven incremental mode applies during ordinary bugfix or feature work. Touch-driven mode optionally uses a retrofit:incremental label and maps changes to acceptance criteria.
V-model traceability links verification evidence to issues and artifacts, making changes in legacy codebases auditable and less risky. It documents how requirements map to tests and architecture decisions, ensuring that modifications maintain compliance and intent.
Yes, V-model retrofits apply targeted, minimal changes to modules, bounded contexts, or features identified by issues or incremental changes. You define the retrofit scope and initiate explicit backfilling within that specific target area.
Architecture retrofitting mode answers what exists in the codebase, while V-model traceability adds how we verify it and links evidence to issues and artifacts. V-model retrofits enforce traceability through acceptance criteria and ADR notes.
When inferring intent from legacy behavior during a retrofit, artifacts must be marked as human-reviewed. The process avoids large changes and prefers small PRs, requiring careful scope definition to prevent big-bang rewrites in complex brownfield environments.
oalansilvaIdentify and define domains and bounded contexts for complex software systems.
jnealey88Execute verification commands and document outputs as completion evidence.
pkuppensMap V-model requirements to verification tests as a navigable skill-tree.
diShine-digital-agencyInventory current state and define target state for technical migrations.
