THE WORKFLOW. THE SCREENS. THE DECISIONS.

A review people
can respond to.

The stakeholder-review-package AI skill turns your PRD, assumptions and mockups into one HTML file for business stakeholders. Email it to them; they review it and return their feedback.

Fictional example: community class bookings. Try the controls; nothing is submitted.

One document to review and answer.html
The fictional class-booking review: selected requirements and a class-list mockup on the left, answerable assumptions on the right.
Made with stakeholder-review-packageReal working example · entirely fictional content
LESS TO NAVIGATE. MORE TO RESPOND TO.

Put each decision
beside its context.

01

The requirements that matter to the business

A short account of each workflow, with its mockups alongside. The full PRD stays one click away.

02

Every open assumption, once

Each proposal shows its confidence and has a Confirm or Change response. Partial feedback is welcome; unanswered decisions stay open.

03

A place for the correction

Comment on an assumption, a requirement or a screen, right where you’re reading it.

An example correction: change the proposed cancellation cutoff to two hours before the class, with a comment explaining why.
An illustrative response in the fictional example.

A USEFUL ANSWER, IN PLAIN LANGUAGE

“Change this”
is enough to start.

Reviewers don’t need to rewrite the specification. They mark a proposal and explain what should be different, including anything they’re unsure about.

When they’re ready, Download reply (.txt) gives them a file to send back, or Copy reply to clipboard lets them paste the same feedback into an email or message. Save editable copy (.html) keeps their answers for later.

Answers stay on their device. Nothing is sent automatically.

FROM REVIEW TO REQUIREMENTS

Short for the reader.
Traceable for the builder.

The package is a dated snapshot with links to its sources. The returned text includes decision IDs, the proposals reviewed and the reviewer’s comments.

Use assumptions-document-feedback to apply the answers, including changes to requirements and mockups. Corrections amend the PRD; once the build has started, new requests go to a follow-on PRD. Implementation still uses the complete PRD and technical design.

PART OF THE ENSO METHOD

Ready when you want to share.

Your agent prepares this after design refinement. Run stakeholder-review-package any time to create or refresh one.