disciplined-validation

Automates Phase 5 validation via system and user acceptance testing with stakeholder sign-off and defect tracing.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/terraphim/terraphim-skills --skill disciplined-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: disciplined-validation
Source: https://github.com/terraphim/terraphim-skills/tree/main/skills/disciplined-validation
Command: npx skills add https://github.com/terraphim/terraphim-skills --skill disciplined-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Phase 5 of disciplined development validates that the system meets original requirements through system testing and user acceptance testing (UAT). It uses structured stakeholder interviews to gather sign-off and traces defects back to research or design phases.

Core Features & Use Cases

  • End-to-end validation of requirements via system tests and UAT.
  • Stakeholder interviews and sign-off documentation.
  • Defect traceability back to research/design for efficient remediation.

Quick Start

Run the disciplined-validation workflow to initiate Phase 5: load the research and design inputs, generate a system test suite, conduct system testing, perform UAT with stakeholder interviews, and produce the Validation Report. Then archive evidence and update the requirements-traceability matrix. Ensure all specialist outputs are linked in the Quality Gate.

Frequently Asked Questions about disciplined-validation

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

FAQPage Schema
What is end-to-end validation in software engineering?

End-to-end validation ensures a system meets original requirements through system testing and user acceptance testing. It uses structured stakeholder interviews to gather sign-off and traces defects back to research or design phases for efficient remediation.

How do I conduct user acceptance testing and gather stakeholder sign-off?

To conduct user acceptance testing, load research and design inputs, generate a system test suite, and perform UAT with structured stakeholder interviews. This process gathers required sign-off documentation and produces a validation report.

How do I trace defects back to original research and design phases?

Defect traceability is achieved by updating a requirements-traceability matrix during validation. This links discovered defects directly back to specific research or design phases, enabling targeted and efficient remediation.

Can I integrate security audits and performance testing into a validation workflow?

Yes, validation workflows can integrate with specialist skills such as acceptance-testing, security-audit, and rust-performance. All specialist outputs are linked in the Quality Gate to ensure comprehensive evidence collection.

What is a validation report and how is evidence archived?

A validation report is the final output of system testing and UAT that records stakeholder sign-off. After generating the report, you archive the collected testing evidence and update the requirements-traceability matrix.