Enso Method Stakeholder Review Packet
Prepare an approachable project review with selected requirements, every open business assumption, clear proposed answers, and traceable corrections. A self-contained, MIT-licensed SkillDB adaptation of EnsoDynamics' stakeholder review workflow.
Use this skill to help a business stakeholder review a project's intended behavior without having to study its entire technical specification. Produce one readable Markdown packet with the relevant context, every open business assumption, and a clear way to confirm or correct each proposal. The packet is a dated view of the source documents. Requirements and technical design remain the implementation contract.
skilldb get enso-method-skills/stakeholder-review-packetFull skill: 150 linesStakeholder Review Packet
Use this skill to help a business stakeholder review a project's intended behavior without having to study its entire technical specification. Produce one readable Markdown packet with the relevant context, every open business assumption, and a clear way to confirm or correct each proposal. The packet is a dated view of the source documents. Requirements and technical design remain the implementation contract.
This is a self-contained SkillDB adaptation of the EnsoDynamics method. Its Markdown procedure replaces the upstream HTML renderer and interactive form; no plugin, external installation, or helper script is required. Preparing a packet does not authorize sending it, publishing private material, changing requirements, or treating an unanswered proposal as accepted. Preserve the user's established scope and sharing instructions.
1. Establish the source snapshot
Read the complete current requirements and assumption register, plus relevant mockups and design sections. Record each source path and an immutable revision or content digest. If the project is not under version control, identify the saved snapshot and capture a reproducible content hash with an available local tool. A preparation timestamp alone cannot establish freshness.
Check whether the requirements belong to a larger initiative. If so, state this phase's place in that initiative using the current plan. Use ordinary language for the reader: what exists today, what the proposed work changes, and what stays outside its scope. Preserve limits that could affect the stakeholder's answer, such as eligible customers, money movement, exceptions, or excluded workflows.
If a named source is missing, stop claiming a complete review and record the gap. If no assumptions register exists, inspect the requirements for unresolved proposals before recording that there are no open assumptions. Do not manufacture an empty register merely to satisfy a template. If different sources disagree, resolve ownership or explicitly identify the conflict before presenting a single settled answer.
2. Inventory the decisions
List every open business assumption by its stable ID before drafting. Include provisional and reopened decisions. Keep settled entries separately identified, and count technical assumptions that remain with the build team. Business questions concern outcomes a stakeholder can choose; technical questions concern facts or construction decisions the implementation team must investigate.
A review can highlight a selection of acceptance criteria, but it must not silently select only the easiest business questions. Every open business assumption needs exactly one answerable location. One assumption containing several choices still needs all those choices visible. Preserve the register's identifiers so a returned correction maps back without guessing.
Do not convert an unresolved blocking question into a fabricated proposal. State the question, available evidence, consequence of waiting, and the decision needed. Such a packet can be marked incomplete and used to request that specific decision. Independent authorized work can continue, but the unresolved decision remains unresolved.
Inventory at source snapshot
Open business assumptions: A-01, A-03
Reopened business assumptions: none
Settled business assumptions: A-02
Technical assumptions: T-01, T-02, tracked by the build team
Questions without a supported proposal: none
Expected answerable entries: A-01, A-03, each exactly once
3. Organize around recognizable work
Group the packet by the stakeholder's workflow, such as eligibility, approval, and handling uncertain outcomes. Explain terms before asking about them. Place each proposal beside the behavior or mockup it affects. A reader should be able to answer without opening a repository file or deciphering an internal API name.
For each section, select consequential requirements: who can act, what changes, money or data outcomes, exceptions, and scope exclusions. Summarize accurately and link each selection to its criterion ID in the packet's traceability notes. Do not imply that the selected criteria are the complete specification.
Use approved, sanitized mockups only when they clarify a decision. Provide a text equivalent for the relevant behavior, and label whether the image is a concept or a working screen. Remove secrets, real customer details, internal-only commentary, and access-bearing links from the shareable packet. If removing a detail would change the meaning of a decision, prepare an approved sanitized example rather than hiding the condition.
4. Write answerable proposal cards
Each card should lead with the proposed answer, then explain its consequence. Carry over the source's confidence, evidence, uncertainty, and material alternatives. Confidence measures support for the proposal, not stakeholder approval or business importance. Do not invent percentages for visual polish. If the source has no confidence assessment, say it has not been assessed.
Here is a complete synthetic Project Returns example:
## Eligibility window
Today, support checks the policy manually. This phase adds a full-refund
check before an authorized support representative submits the request.
Partial refunds are outside this phase.
Selected requirement: Ineligible or unauthorized requests leave the original
payment unchanged, including no provider call or committed refund. The response
gives the caller the appropriate explanation. [R-03]
### A-01 — How long after payment can a refund be requested?
Proposed answer: Allow requests through 30 elapsed 24-hour days after payment,
including the exact cutoff. Use the recorded payment and request times in UTC.
Confidence: Medium. The policy draft supports 30 days; the historical
samples are incomplete and do not resolve older orders.
Impact: Changes which orders qualify and the boundary examples we test.
If corrected: Update the rule, customer explanation, and affected tests
before allowing real refunds under the revised policy.
Your response: Confirm / Change / Need more information / Not reviewed
Correction or question:
### A-03 — What should support see while a provider result is uncertain?
Proposed answer: Show "Refund pending confirmation" and prevent a new
refund for the same operation until its original result is reconciled.
Confidence: Medium; this proposal protects against a duplicate effect,
but the support team has not yet reviewed the wording.
Impact: Changes what support tells the customer while the result is pending.
If corrected: Revise the explanation without treating uncertainty as failure
or permission to issue another refund. [R-02, R-04]
Your response: Confirm / Change / Need more information / Not reviewed
Correction or question:
The card is for deciding business behavior. The provider's idempotency interface, database locking, and retry implementation belong to technical review. If a stakeholder response affects those contracts, record the downstream impact during reconciliation.
5. Assemble the packet
Use this structure, adapting the project's existing filenames:
Title, preparation date, scope, and source snapshot
Notice: For business review; selected criteria and all open business assumptions.
Implementation uses the complete requirements and technical design.
Current workflow and what this phase changes
In this review: section names
Workflow sections: selected criteria, contextual mockups, proposal cards
Feedback on criteria or mockups: criterion/section, correction, rationale
Already decided: concise answers that can still be corrected explicitly
Technical questions: count and build-team owner, without unnecessary detail
Response instructions and freshness warning
Source inventory and assumption-coverage reconciliation
Keep unanswered entries visibly unanswered. Partial feedback is useful; it does not approve the remaining proposals. Do not place high-impact exceptions behind a reference that a reader must open to understand what “Confirm” means. Keep source notes available for deeper inspection without making them essential to comprehension.
6. Verify completeness and freshness
Reconcile the packet's answerable IDs against the source inventory using set equality and duplicate detection. Two appearances of A-01 do not compensate for a missing A-03. Check that every displayed proposal matches the current register and that all selected requirements preserve their actor, scope, and exceptions. Confirm that referenced local artifacts exist and that the shareable copy contains no private fields.
Perform a cold read as someone unfamiliar with the project. Can they explain what will happen if they confirm each proposal, and what changes if they correct it? A beautifully formatted packet fails review if its answers depend on undocumented context. Check the source digests again before sharing or consuming feedback. A changed source makes the affected packet stale; refresh it and show which decisions changed.
For acceptance, the two-entry synthetic inventory above must produce exactly two answerable cards. As negative checks, remove A-03, duplicate A-01, or change the requirement source after preparation: each must prevent a “complete and current” status. These are verification scenarios to execute during preparation, not claims of a prebuilt validation tool.
7. Reconcile returned feedback
Record the response date, respondent's decision authority, packet version, assumption or criterion ID, and exact intended correction. If A-01 changes to 45 days, compare the reply against the current register before applying it. Another person may already have corrected the source after this packet was prepared. Preserve both records and resolve conflicts through the appropriate owner.
Apply accepted corrections to requirements and assumptions first, then identify affected design choices, mockups, tests, and planned phases. Preserve earlier evidence as historical rather than rewriting its observed result. Route new features into explicitly scoped work. Do not infer production authorization from a policy answer.
Finish with the packet path, source snapshot, included and missing IDs, verification outcomes, corrections received, and next owner/action. Sending remains a separate action governed by the user's instructions. The useful deliverable is a review someone can answer confidently and a traceable path for carrying their answer into the actual project.
Attribution and license
Adapted from EnsoDynamics/enso-method, revision 23a908030bf6b4e228ba90f1937af87aed470e0b: stakeholder-review-package. This catalog adaptation is distributed under the MIT License below.
MIT License
Copyright (c) 2026 Doug Kerwin
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OF OR OTHER DEALINGS IN THE SOFTWARE.
Install this skill directly: skilldb add enso-method-skills
Related Skills
Enso Method Technical Design and Readiness Review
Use the Enso Method to design from acceptance criteria, verify recovery and integration details, and hand off a bounded implementation scope.
The Enso Method
Turn a project idea into clear requirements, practical build phases, and evidence that the result works. A self-contained, MIT-licensed SkillDB adaptation of EnsoDynamics' method, with proposed answers and stakeholder corrections kept alongside the work.
Enso Method Research Assumptions and Reconcile Feedback
Use the Enso Method to record proposed business decisions with evidence and confidence, then propagate authorized stakeholder corrections to requirements and dependent work.
Enso Method Evidence-Based Review and Testing
Review deliverables against intent, audit delivery and tests by acceptance criterion, and verify repaired evidence at the boundary where the outcome is observed.
Enso Method Implementation and Recovery
Implement a bounded requirements phase, resolve discoveries in its source documents, and recover interrupted work without replaying uncertain effects.
Enso Method Initiative and Phase Planning
Turn an initiative into bounded requirements documents and implementation phases with stable acceptance criteria, dependency contracts, and reviewable handoffs.