skf-verify-stack

To verify skill stack feasibility, you cross-reference architecture and PRD documents against the generated skills. This process checks composition coherence and produces an evidence-backed feasibility report citing specific APIs, types, and function signatures for auditability.

Skill stack traceability validates generated skills by mapping them against architecture and PRD documents. It ensures each skill is backed by evidence, citing specific APIs and function signatures, to confirm the implementation plan is coherent and verifiable.

You generate a feasibility report by providing an architecture document path and an optional PRD to the verification workflow. It performs compatibility checks and outputs a report conforming to a deterministic schema with stable file naming for auditability.

Yes, you can validate skill compatibility using only an architecture document, though providing an optional PRD enhances the analysis. The verification process cross-references available documents to produce a traceable feasibility verdict.

Yes, the verification process uses deterministic skill enumeration and synthesis to guide workflows. It outputs reports conforming to a deterministic schema with stable frontmatter, sections, and file naming schemes specifically designed for auditability.

The best way to ensure traceability is to cross-reference your skill inventory with architecture and PRD documents. This generates an evidence-backed feasibility report that records source locations and cites specific APIs and types for each skill.