gsdd-verify

Verify project phases against defined success criteria using code, documentation, and test results.

Updated Dec 17, 2024
One-click install
npx skills add https://github.com/patcarter883/open-broadcast-encoder --skill gsdd-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsdd-verify
Source: https://github.com/patcarter883/open-broadcast-encoder/tree/main/.agents/skills/gsdd-verify
Command: npx skills add https://github.com/patcarter883/open-broadcast-encoder --skill gsdd-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps verify that completed work genuinely meets project-phase goals rather than merely marking tasks as done.

Core Features & Use Cases

  • Phase Goal Verification: Checks that phase outputs fulfill success criteria from planning and specification documents.
  • Artifact Validation: Confirms the existence, completeness, and proper wiring of code artifacts.
  • Key Link Assessment: Ensures critical component interactions and data flows are correctly established.
  • Use Case: A developer completes a feature; GSDD-Verify cross-checks the code, tests, and documentation to confirm the feature fully satisfies the intended goal before progressing.

Quick Start

Run the verification tool to cross-validate build artifacts against the original goals and documentation.

Frequently Asked Questions about gsdd-verify

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

FAQPage Schema
How do I verify project phases meet defined success criteria before release?

Verify project phases by cross-checking source code, test results, and documentation against original planning specifications to ensure completed work genuinely achieves goals rather than just marking tasks as done.

What is the best way to validate code artifacts and key integrations for production readiness?

Validating code artifacts involves confirming the existence, completeness, and proper wiring of components while assessing critical data flows to ensure key integrations are correctly established for production readiness.

How does phase goal verification work for completed software features?

Phase goal verification works by cross-validating build artifacts against original goals and documentation, checking that phase outputs fulfill success criteria from planning and specification documents before progressing.

What do I need to provide for comprehensive validation of development pipelines?

Comprehensive validation of development pipelines requires source code, test results, and documentation as inputs to check code, validate artifacts, and assess key links across quality assurance workflows.

Can I use this validation approach across different quality assurance workflows?

Yes, this validation approach applies across development pipelines and quality assurance workflows to verify production readiness by checking code, documentation, and key integrations for genuine goal achievement.

Why does task completion not guarantee project goals are truly achieved?

Task completion often misses project goals because standard tracking marks items done without verifying that phase outputs fulfill success criteria or that critical component interactions are correctly established.