Jay-Dev Evidence Collection Skill

Name: Jay-Dev Evidence Collection Skill
Availability: InStock
Author: jayhjenkins

Collect tests, QA, commits, and reviews into a structured STATUS.md.

Updated Jan 3, 2026

Search Tags:#documentation #QA #evidence #code-review #commit-history #test-results #STATUS.md

Ready to run

npx skills add https://github.com/jayhjenkins/Dev-Team-Full-SDLC --skill jay-dev-evidence-collection-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Jay-Dev Evidence Collection Skill
Source: https://github.com/jayhjenkins/Dev-Team-Full-SDLC/tree/main/.claude/skills/jay-dev-evidence-collection
Command: npx skills add https://github.com/jayhjenkins/Dev-Team-Full-SDLC --skill jay-dev-evidence-collection-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collecting and proving completion evidence for software work to prevent assumptions about task completion and simplify audits.

Core Features & Use Cases

Evidence gathering across tests, QA, commits, code reviews, and documentation to support completion status.
End-to-end closure for sprint handoffs and PRD-to-ship cycles, ensuring traceable quality gates.
Audit-ready outputs: generates and compiles STATUS.md with linked evidence sections for easy verification.

Quick Start

After finishing all plan tasks, trigger the evidence collection process to assemble tests, QA results, commits, and reviews into the completion report.

Frequently Asked Questions about Jay-Dev Evidence Collection Skill

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

FAQPage Schema

How do I collect completion evidence for software engineering tasks?▼

To collect completion evidence, trigger the evidence collection process after finishing plan tasks to assemble tests, QA results, commits, and code reviews into a structured STATUS.md file for audit verification.

What is a STATUS.md file and when do I need it for sprint handoffs?▼

A STATUS.md file is an audit-ready artifact containing linked evidence sections for tests, QA, commits, and reviews; you need it during sprint handoffs or PRD-to-ship cycles to ensure traceable quality gates and prevent completion assumptions.

How do I prove test results and QA status for a project closure?▼

You prove test results and QA status by gathering documentation across tests, commits, and code reviews, then compiling these outputs into a structured completion report to satisfy project closure requirements.

Does evidence collection work for PRD-to-ship cycles and code reviews?▼

Yes, evidence collection applies to PRD-to-ship cycles by capturing code reviews, commit history, and documentation updates to ensure traceable quality gates and prevent assumptions about task completion.

What's the best way to document commit history and code reviews for audits?▼

The best way to document commit history and code reviews for audits is generating a structured STATUS.md that links evidence sections, simplifying verification of end-to-end project closures and sprint handoffs.