package

To generate a delivery-ready README from feature intake screenshots, this Skill assembles intake evidence into a reviewer-friendly directory, building screenshot indexes, contact sheets, and a top-level README with links, risks, and next decisions.

The best way to organize a product review handoff package is to assemble intake outputs into a single delivery structure, generating a feature coverage matrix, visual proof inventories, and a top-level README so stakeholders can review without digging through raw artifacts.

To build a feature coverage matrix from UI testing evidence, the Skill validates package shape for a specific feature slug, indexes remaining questions, and highlights blockers or fidelity gaps directly within the final handoff directory.

Yes, you can include decision notes and risk highlights in a screenshot intake README. The Skill generates a top-level README that explicitly links important screenshots, records remaining questions, and outlines next decisions for reviewers.

To assemble a feature intake handoff package for a single feature slug, you need the relevant screenshots and intake evidence. The Skill then validates the package shape, builds contact sheets, and writes the top-level README.

A feature intake handoff package needs a coverage matrix and screenshot index to summarize visual proof and QA results, ensuring stakeholders understand what changed, what still needs a decision, and where fidelity gaps exist.