skf-verify-stack

Verify tech stack feasibility against architecture and PRD documents.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/delorenj/voxxy --skill skf-verify-stack-delorenj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skf-verify-stack
Source: https://github.com/delorenj/voxxy/tree/main/.gemini/skills/skf-verify-stack
Command: npx skills add https://github.com/delorenj/voxxy --skill skf-verify-stack-delorenj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python, skf-core, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the verification of tech stack feasibility against architecture and PRD documents, identifying integration issues, coverage gaps, and requirements fulfillment.

Core Features & Use Cases

  • Cross-Reference Analysis: Automatically match generated skills against architecture and PRD documents.
  • Read-Only Workflow: Never modifies source documents, ensuring integrity.
  • Automated Report Generation: Produces feasibility reports with evidence-backed integration verdicts and requirements mapping.

Quick Start

To initiate a verification run, run the following command: ./verify-stack --arch_doc_path /path/to/arch_doc --prd_doc_path /path/to/prd_doc

Frequently Asked Questions about skf-verify-stack

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

FAQPage Schema
How do I verify tech stack feasibility against architecture and PRD documents?

Yes, you can automate tech stack verification by running a command-line script that points to your architecture and PRD document paths. The process analyzes integrations and requirements, generating an evidence-backed feasibility report.

What is architecture verification and how does it check requirements coverage?

Architecture verification cross-references your tech stack components against project architecture and PRD documents. It identifies integration issues and coverage gaps, generating evidence-backed feasibility reports with requirements mapping.

Do I need Python and skf-core to run stack verification for PRD analysis?

Yes, Python and skf-core are required dependencies for running stack verification. You also need local file paths to your architecture and PRD documents to initiate the cross-reference analysis.

Can I perform read-only feasibility analysis without modifying source architecture documents?

Yes, the stack verification workflow is strictly read-only and never modifies your source architecture or PRD documents. It ensures document integrity while performing cross-reference analysis and generating feasibility reports.

What's the best way to generate evidence-based feasibility reports for a tech stack?

The best way is to use an automated stack verification tool that cross-references your tech stack against architecture and PRD documents. This generates evidence-backed feasibility reports with integration verdicts and requirements mapping.

Why does stack verification fail when architecture or PRD document paths are missing?

Stack verification requires explicit file paths to both architecture and PRD documents to perform cross-reference analysis. Without these source documents, it cannot match skills, identify integration issues, or map requirements fulfillment.