About this skill

What problem it solves

Business demos and product prototypes often stop at screens and talking points, while engineering still lacks fields, APIs, exceptions, permissions, and acceptance criteria. Yiou DemoToTech turns HTML, React, screenshots, and requirement text into a reviewable technical solution document instead of production code.

How it works

It maps business goals, roles, and page flows, then extracts business rules, entities, fields, data ownership, and interface requirements. It also adds edge cases, error states, timeouts, and permission scenarios. Key outputs include:
- Technical document: pages, modules, fields, flows, APIs, and acceptance criteria
- Structured JSON: importable or checkable downstream
- Open questions: with impact, priority, and default suggestion
- Task breakdown: split by FE, BE, and QA
- Maturity level: from L1 to L4, with blocking_gaps

Boundaries

It is best used for pre-development clarification and solution review, not for replacing technical review or making final business decisions. When API sources, data ownership, or permission rules are unclear, it should mark them as to be confirmed and avoid claiming the doc is ready for development.

Screenshots

Use Cases

Convert a product demo into a reviewable technical solution with APIs, fields, and open questions.
Use screenshots and prototype notes to clarify business rules, entity fields, and data sources before development.
Break business language into FE, BE, and database tasks with priorities and acceptance criteria.
Detect missing permission, exception, and timeout cases in a demo and build an open-question table.

Best For

Product managers who need to turn prototypes and demos into reviewable engineering plans.
Backend engineers who need to confirm APIs, fields, data sources, and edge cases before development.
Project leads who need to break business requirements into FE, BE, and QA tasks for scheduling.
QA owners who need to structure acceptance criteria, open questions, and delivery docs.