witness

Guide a structured human review of developer deliverables against acceptance criteria.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MariusWilsch/Developer-Position --skill witness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: witness
Source: https://github.com/MariusWilsch/Developer-Position/tree/main/plugins/dev-lead-position-plugin/skills/witness
Command: npx skills add https://github.com/MariusWilsch/Developer-Position --skill witness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires uv, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of reviewing developer work by providing a structured, human-guided ceremony to verify deliverables against acceptance criteria and project context.

Core Features & Use Cases

  • Structured Review Process: Guides a human through a step-by-step verification of code, documentation, and deployment.
  • Contextual Grounding: Ensures reviews are based on defined acceptance criteria, design documents, and issue context.
  • Use Case: When a developer finishes a feature, use this Skill to conduct a "witness ceremony" where you collaboratively walk through the implementation, ensuring it meets all requirements and behaves as expected.

Quick Start

Use the witness skill to start a review ceremony for the current pull request.

Frequently Asked Questions about witness

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

FAQPage Schema
How do I verify code against acceptance criteria during a pull request review?

To verify code against acceptance criteria during a pull request review, you can run a structured witness ceremony that fetches issue context, design documents, and PR details to ground the human-guided verification process.

What is a structured review ceremony for developer deliverables?

A structured review ceremony for developer deliverables is a human-guided process that step-by-step verifies code, documentation, and deployment against project context and defined acceptance criteria to ensure quality.

How do I conduct a feature verification walkthrough for a completed developer task?

You can conduct a feature verification walkthrough by initiating a witness process that collaboratively guides you through the implementation to ensure the deliverable behaves as expected and meets all requirements.

Do I need to fetch issue context and design documents before reviewing developer output?

Yes, fetching issue context, design documents, and PR details is required before reviewing developer output to ensure the witness process is grounded in the actual project requirements and acceptance criteria.

What is the best way to spot-check developer output for quality assurance?

The best way to spot-check developer output for quality assurance is applying a structured ceremony that verifies deliverables against defined acceptance criteria and project context to ensure comprehensive validation.