sp-verify

Validate user-facing behaviors before marking software tasks complete.

Updated Jun 8, 2026

Search Tags:#task management #verification #software quality #feature completion #evidence-based development

Ready to run

npx skills add https://github.com/JZKK720/cubecloud-agentic-os --skill sp-verify-jzkk720

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sp-verify
Source: https://github.com/JZKK720/cubecloud-agentic-os/tree/main/.agents/skills/sp-verify
Command: npx skills add https://github.com/JZKK720/cubecloud-agentic-os --skill sp-verify-jzkk720

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Ensures that features and tasks are not claimed complete without actual user-facing evidence, fostering reliable software quality and integrity.

Core Features & Use Cases

Evidence-Driven Verification: Encourages evidence over claims, requiring users to verify their actions against actual user-facing behaviors.
Five Verification Questions: Assists in answering key questions before claiming completion of a task, such as ensuring the task has been run and results observed.
Anti-Patterns and Documentation: Helps identify common mistakes and provides guidelines on documenting and reporting results.

Quick Start

Execute the 'sp-verify' command and follow the prompt to ensure a task has been fully verified before marking it complete.

Frequently Asked Questions about sp-verify

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

FAQPage Schema

How do I verify feature completion for user-facing behaviors before marking a task complete?▼

Evidence-driven verification requires users to run tasks and observe results, providing proof of actual user-facing behaviors instead of claims. This process ensures software quality and accountability before marking a task complete.

What is evidence-based development for software quality control?▼

Evidence-based development demands observable proof of user-facing behaviors before finalizing administrative workflows. It prevents features from being claimed complete without actual verification, fostering software quality and integrity.

How do I use the five verification questions to ensure task completion?▼

The five verification questions prompt users to run the task and observe actual results before claiming completion. This framework identifies anti-patterns and provides guidelines for accurately documenting and reporting verification outcomes.

What are common anti-patterns when claiming a software feature is complete?▼

Common anti-patterns include marking tasks done without running them or observing user-facing results. Identifying these mistakes ensures developers provide actual evidence and proper documentation for quality control.

Does task management verification work for administrative workflows in software development?▼

Task management verification targets administrative workflows in software development for quality control and accountability. It ensures features are not finalized without actual user-facing evidence, making it suitable for managing release integrity.