agentic-engineering-verification

Independently review and verify implemented changes against approved requirements with traceable evidence.

Updated Jul 19, 2026

Search Tags:#code review #verification #agentic workflow #acceptance testing #requirement traceability #pr audit

Ready to run

npx skills add https://github.com/DagimAlemayehuu/AgenticEngineering --skill agentic-engineering-verification-dagimalemayehuu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agentic-engineering-verification
Source: https://github.com/DagimAlemayehuu/AgenticEngineering/tree/main/agentic-engineering/skills/agentic-engineering-verification
Command: npx skills add https://github.com/DagimAlemayehuu/AgenticEngineering --skill agentic-engineering-verification-dagimalemayehuu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Implemented changes often get merged or released without independent confirmation that they actually satisfy the approved requirements, leading to regressions and untraceable acceptance decisions. This Skill enforces a verification phase where a reviewer independent of the implementation reproduces evidence before anything is accepted. ## Core Features & Use Cases - Independent PR Audits: Review a completed change with a verifier identity separate from the implementer, producing a requirement-traceable review record. - Fresh Evidence Reproduction: Re-run test, build, visual, and manual checks rather than trusting stale or self-reported results. - Recovery and Acceptance Decisions: Document residual risks, recovery options, and a human-readable walkthrough before assurance or release. - Use Case: After a Jules-driven implementation phase opens a pull request, invoke this Skill to audit the PR, reproduce the build and test evidence, and produce an acceptance record before merge. ## Quick Start Use $agentic-engineering-verification to independently review and verify this change against its approved requirements.

Frequently Asked Questions about agentic-engineering-verification

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

FAQPage Schema

How do I independently verify a pull request before merging?▼

Invoke the verification phase to audit the PR with a reviewer identity separate from the implementer. It reproduces test, build, and manual evidence, then produces a requirement-traceable review record that must show acceptance before merge or release.

What is requirement traceability in code review?▼

Requirement traceability links every verified behavior back to an approved requirement in the project contract. This Skill generates a review record mapping each requirement to fresh command output, manual checks, or visual evidence.

Can the same agent that wrote the code verify it?▼

No. The Skill requires a verifier identity independent of the implementation, so the agent or session that produced the change cannot also sign off on its verification evidence.

When should I use sdlc-verify instead of the standard verification flow?▼

Use sdlc-verify only for legacy three-phase projects whose approved contract still assigns integration, release, and archive steps to that procedure. Current projects use openspec-verify-change, verification-before-completion, and review.

What happens if verification evidence cannot be reproduced?▼

The Skill documents residual risks and recovery decisions in the review record instead of approving the change. The change is not merged or released until the required acceptance evidence is obtained.