devbooks-test-owner

Enforce Test Owner roles and generate verification.md with AC coverage evidence.

84|6|Updated Jan 12, 2026

Search Tags:#verification #audit #traceability #quality-gate #evidence-management #ac-coverage #test-owner

Ready to run

npx skills add https://github.com/Darkbluelr/dev-playbooks-cn --skill devbooks-test-owner

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: devbooks-test-owner
Source: https://github.com/Darkbluelr/dev-playbooks-cn/tree/main/skills/devbooks-test-owner
Command: npx skills add https://github.com/Darkbluelr/dev-playbooks-cn --skill devbooks-test-owner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Test Owner role often lacks a clear, auditable process to translate designs/specs into executable verification, tests, and evidence, causing misalignment between design intent and implementation.

Core Features & Use Cases

Enforces Test Owner isolation from Coders with independent verification workflows.
Generates verification.md with status management, AC coverage, and traceability matrices.
Manages evidence lifecycle (red baseline, green final) and artifact routing in change packages.
Provides preconfigured templates and guidelines to drive testing and auditing in complex AI/engineering tasks.

Quick Start

Run the skill to initialize a verification plan from a change's design and generate a ready verification.md guiding the next steps.

Frequently Asked Questions about devbooks-test-owner

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

FAQPage Schema

How do I enforce test ownership and generate verifiable evidence for AI-driven testing?▼

You can enforce test ownership by automating Test Owner role isolation from Coders and generating a verification.md file that manages evidence lifecycles, AC coverage, and traceability matrices.

What is a verification.md file and how does it support traceability in change packages?▼

A verification.md file structures your verification planning by mapping acceptance criteria coverage and evidence paths. It provides a traceability matrix that ensures alignment between design intent and implementation within change packages.

How do I create a verification plan with AC coverage and evidence routing for CI workflows?▼

You create a verification plan by running the skill to initialize from a change's design. This generates a ready verification.md guiding evidence routing, baseline management, and CI workflow integration.

Can I use automated evidence management for complex engineering tasks without coding conflicts?▼

Yes, the skill enforces Test Owner isolation from Coders through independent verification workflows. This ensures role separation while managing evidence lifecycles and artifact routing in change packages.

Does this approach support preconfigured templates for audit and quality gate enforcement?▼

Yes, it provides preconfigured templates and guidelines to drive testing and auditing in complex AI tasks. These templates enforce quality gate checks and structure evidence generation within change packages.

What is the best way to manage the evidence lifecycle from red baseline to green final?▼

The best way is using an automated governance process that tracks evidence artifacts from red baseline to green final. This manages artifact routing in change packages and ensures verifiable evidence for audits.