zigzag-validator

Map and validate traceability across CP, CN, and FR domains.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/shirogin/jesuph-skills --skill zigzag-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zigzag-validator
Source: https://github.com/shirogin/jesuph-skills/tree/main/.agents/skills/zigzag-validator
Command: npx skills add https://github.com/shirogin/jesuph-skills --skill zigzag-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool helps product teams and engineers ensure traceability across Customer Problems (CP), Customer Needs (CN), and Functional Requirements (FR), identifying gaps, orphan items, and inconsistencies before development progresses.

Core Features & Use Cases

  • ZAG-MAP: forward mapping from CP/CN to FR to reveal relationships and gaps.
  • ZIG-VALIDATE: backward traceability to confirm FR/Ns trace back to CPs.
  • DECOMPOSE: hierarchical breakdown across domains to surface refinement opportunities.
  • CONSISTENCY-CHECK: full audit covering coverage, gaps, orphans, and redundancies.

Quick Start

Run Zig Zag validation to map CPs to CNs and CNs to FRs, then verify bidirectional traceability and highlight gaps.

Frequently Asked Questions about zigzag-validator

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

FAQPage Schema
How do I ensure traceability between customer needs and functional requirements?

To ensure traceability between customer needs and functional requirements, you need bidirectional mapping that validates forward decomposition and backward traceability to highlight coverage gaps and orphan items.

What is requirements decomposition and when do I need it?

Requirements decomposition is the hierarchical breakdown of customer problems into functional requirements. You need it during and after generation to surface refinement opportunities and ensure hierarchical alignment across domains.

How do I audit requirements for gaps and orphan items?

To audit requirements for gaps and orphan items, perform a full consistency check covering coverage and redundancies, applying independent axiomatic design mapping to verify cross-domain decomposition and alignment.

What's the best way to validate backward traceability from functional requirements to customer problems?

The best way to validate backward traceability from functional requirements to customer problems is to apply backward validation operations that confirm every functional requirement traces back to a defined customer problem.

Does this traceability validation approach work without external dependencies?

Yes, this traceability validation works without external dependencies, applying internal axiomatic design mapping to independently audit cross-domain decomposition and ensure hierarchical alignment across customer problems and functional requirements.