feature-verify

Verify feature behavior in read-only mode with code analysis and Codex confirmation.

187|24|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/sd0xdev/sd0x-dev-flow --skill feature-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-verify
Source: https://github.com/sd0xdev/sd0x-dev-flow/tree/main/skills/feature-verify
Command: npx skills add https://github.com/sd0xdev/sd0x-dev-flow --skill feature-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables safe, read-only verification of feature behavior by combining code analysis, data validation, and Codex third-person confirmation to produce auditable results without modifying systems.

Core Features & Use Cases

  • Read-only feature verification: analyze behavior, validate data flows, and confirm correctness without writing data.
  • Structured workflow: exploration, planning, execution, analysis, Codex confirmation, and integrated reporting.
  • Executive reporting: generates a formal summary with checks, status, and actionable recommendations for APIs, data pipelines, and integrations.

Quick Start

To begin verification, run /feature-verify <system-name> with credentials, then initiate /codex-brainstorm for independent confirmation and review the generated report template in references/output-template.md.

Frequently Asked Questions about feature-verify

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

FAQPage Schema
How do I verify feature behavior in a read-only mode without modifying the production system?

Read-only feature verification analyzes code, validates data flows, and confirms correctness without writing data. It uses a structured workflow of exploration, planning, execution, and Codex confirmation to produce auditable results safely.

What's the best way to validate data pipelines and integrations without risking side effects?

Validating data pipelines safely requires a read-only approach that combines code analysis and data validation. This process generates a formal executive report with checks, status, and actionable recommendations without altering your systems.

Can I get an independent confirmation of my code analysis results for APIs?

Yes, obtaining independent confirmation for API code analysis involves using Codex third-perspective validation. This mechanism cross-references your initial findings during the analysis phase to ensure feature correctness and reduce diagnostic blind spots.

How do I generate an executive report for feature diagnosis and data validation?

Generating an executive report for feature diagnosis requires running a structured verification workflow. The process outputs a formal summary template containing validation checks, current status, and actionable recommendations for your systems.

Does feature verification work without write access to the target system?

Yes, feature verification operates entirely in read-only mode without requiring write access. It safely diagnoses feature behavior by analyzing code paths and validating data flows, ensuring the target system remains completely unmodified.

When should I not use a read-only approach for feature verification?

Read-only feature verification is not suitable when active system modification or data correction is required. Since it strictly analyzes behavior and validates data flows without writing data, you must use alternative methods to apply fixes or patch integrations.