start

Transforms prototypes and screenshots into screenshot-backed product integration analysis packages.

1|Updated May 19, 2026
One-click install
npx skills add https://github.com/edonghyun/donghyuns-agent-tools --skill start-edonghyun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start
Source: https://github.com/edonghyun/donghyuns-agent-tools/tree/main/plugins/feature-intake/skills/start
Command: npx skills add https://github.com/edonghyun/donghyuns-agent-tools --skill start-edonghyun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns prototypes, demos, screenshots, and other pre-implementation artifacts into a structured product integration analysis package, reducing ambiguity during handoff.

Core Features & Use Cases

  • Intake and Coverage Planning: Identifies the artifact, output location, capture scope, and whether runtime evidence or external-call mocking is needed.
  • Screenshot-Backed Analysis: Produces inspect, capture, frame, analyze, map, and package outputs for page flows, controls, states, and edge cases.
  • PoC Fidelity Review: Builds a baseline fidelity matrix when a delivered build must be checked against a source prototype or design reference.

Quick Start

Ask the start skill to turn this PoC into a screenshot-backed product integration analysis package.

Frequently Asked Questions about start

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

FAQPage Schema
How do I turn a PoC prototype into a product handoff package?

A product handoff package transforms prototypes and screenshots into structured integration analysis. It applies inspect, capture, frame, analyze, map, and package outputs to document page flows, controls, states, and edge cases for implementation teams.

How do I document user flows for pre-implementation design artifacts?

Screenshot-backed analysis works by applying a structured inspect, capture, frame, analyze, map, and package sequence to artifacts. It produces mapped page flows, controls, states, and edge cases with state-taxonomy coverage for PoC fidelity verification.

What is the best way to review implementation parity against a source prototype?

Yes, you can verify implementation divergence by building a PoC fidelity matrix. This matrix checks a delivered build against a source prototype or design reference to map state-taxonomy coverage and confirm implementation parity.

Does product handoff analysis require runtime evidence or external-call mocking?

Product handoff analysis may require runtime evidence or external-call mocking depending on the artifact. Intake and coverage planning identifies the specific capture scope, output location, and whether runtime evidence or mocking is needed for the integration package.

What is a screenshot-backed product integration analysis package?

A screenshot-backed product integration analysis package is a structured output that transforms prototypes and demos into inspect, capture, frame, analyze, map, and package deliverables. It documents page traversals, controls, states, and edge cases to reduce handoff ambiguity.