cleanmatic:product-spec

To generate a traceable product spec hierarchy, use an interview-driven workflow to map plain language goals into a structured tree from Vision to BRD, PRD, Epic, and Story. This model enforces deterministic validation and frontmatter-driven structure without requiring coding.

The best way to visualize product requirements offline is to generate deterministic outputs like ASCII, Mermaid, or HTML formats. This skill provides a read-once export path and optional on-demand assets to render the spec tree without writing any code.

Yes, this product spec workflow supports bilingual EN/VI requirements mapping. It applies across bilingual workflows to help non-technical product owners capture, structure, and validate requirements in both English and Vietnamese.

Yes, you can enforce approval workflows and change-tracking for product specs. The hierarchy model loads frontmatter-driven metadata to satisfy memory governance, structure validation, and strict change-tracking across the entire artifact tree.

No, you do not need technical coding skills to decompose PRDs into Epics and Stories. The skill is designed for non-technical product owners, using interview-driven decomposition to elicit goals and map them into a testable spec tree.