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.
Self-contained SkillDB adaptation of The Enso Method by EnsoDynamics. Upstream copyright 2026 Doug Kerwin. SkillDB reorganized the workflow and added the synthetic Returns example, explicit authorization boundaries, and local verification steps.
skilldb get enso-method-skills/technical-design-and-readinessFull skill: 80 linesEnso Method: Technical Design and Readiness Review
Self-contained SkillDB adaptation of The Enso Method by EnsoDynamics. Upstream copyright 2026 Doug Kerwin. SkillDB reorganized the workflow and added the synthetic Returns example, explicit authorization boundaries, and local verification steps.
Read the requirement before choosing an architecture
Use this workflow after a PRD has outcomes, scope and acceptance criteria, or when a change exposes a design gap. The example uses requirements.md, technical-design.md, and assumptions.md together with phase, evidence and handoff records. Capture the current repository and requirement revision and identify which criteria belong to this design. Read existing application entry points, relevant tests and environment configuration. Locate the current behavior and constraints before proposing new components. Existing code can show how the feature works today. The requirements remain the source of truth for what the changed feature should do.
Write down which surfaces will change, which interfaces and callers must remain compatible, and which assumptions would alter a design decision. A limited change may need only a concise design record. A cross-system capability needs an explicit data and control-flow description, failure and recovery model, integration contracts, migrations or rollout constraints, and verification evidence linked to criteria. Keep business behavior and technical choices linked by criterion ID rather than reproducing rules in several editable copies.
Describe the proposed implementation and its failure paths
For each interface, state what calls it, what inputs are accepted, which identity is checked, what durable state can change, and how the caller knows the outcome. If two services cannot update atomically, name the gap and choose a recovery strategy. Record what a timeout before a reply actually tells the application. Correct design distinguishes a known failure from an unknown remote outcome. It also identifies where to observe and reconcile the operation, and which retry can happen safely.
For Returns, read PRD-returns-r2 and record the approved scope for R-01 through R-04. The support application receives an approval for a synthetic eligible paid order. The server checks the actor’s role and the eligibility rule before preparing a payment operation record. It ties an approval ID to the original payment, order and requested amount. The local write establishes which logical operation was accepted. The selected payment connector's supported idempotency key and lookup mechanism determine whether an external effect can be safely repeated or queried. Validate those capabilities in a documented fixture or approved sandbox before committing to this design.
If the connector cannot reliably establish an outcome after a lost reply, leave the operation in a recoverable pending state and escalate through the project's approved reconciliation path. Don't generate a new key or tell the customer it failed unless there is evidence. A repeat approval with the same payload returns the existing status or result. A changed payload under the same approval ID is a conflict. An unauthorized or ineligible request must produce no payment request and leave durable financial state unchanged. Logging should capture a correlation ID and outcome without exposing payment credentials or unnecessary personal information.
A design record can use this inline structure.
Design: DESIGN-returns-r1 | Inputs: PRD-returns-r2, A-01 provisional
Entry point: Authorized support approval for a paid order.
Mapping: R-01 authorize, check eligibility, record operation, confirm payment.
Mapping: R-02 approval identity, payload binding, replay and status lookup.
Mapping: R-03 no payment dispatch or committed refund on denied input.
Mapping: R-04 uncertain result stays pending until authoritative reconciliation.
Current constraints: Existing support roles, account partition, payment adapter.
State: received -> pending -> confirmed or failed with evidence.
Ambiguous response: retain pending and reconcile using approved lookup.
Dependency: Idempotency behavior verified against the target sandbox or documented gap.
Rollback: stop new approvals; reconcile existing pending operations first.
Run the readiness review against evidence
Review the design for correctness before beginning implementation. Follow one criterion from actor to result and back to the observed data. Inspect the current repository before declaring a behavior already handled. Compare the intended contract with existing callers, data and old fixtures. Review duplicate or concurrent requests, interrupted work, recovery, and the newest and oldest supported record types. If a change can become visible in several environments, record what must be verified separately in each.
Use a readiness table with issue ID, affected criterion, classification, evidence, proposed resolution, responsible owner, and blocking scope. A technical question is closed by documentation, observable repository behavior, or an authorized test. A business decision remains provisional until its governing process resolves it. A-01 provisionally allows a refund through 30 elapsed 24-hour days, inclusive, measured from the recorded payment time to the recorded request time using UTC. The exact cutoff comes from the requirement and assumption register, and the implementation records which revision it applies. Keep changes to live payments on hold when that policy or their operational permission is unsettled.
For a positive readiness case, verify a permitted sandbox approval inside the window returns a successful result and stores the reference tied to the expected payment. For a negative case, simulate a lost reply after the adapter may have accepted the request. Check that the next action reconciles pending work with the same stable approval identity. Add a two-request concurrency case and verify only one operation can progress to a refund effect. If those semantics cannot be shown in the target environment, state precisely which criterion remains blocked. A stub that returns a canned success cannot establish external recovery behavior.
Declare readiness by scope. A missing credential or unavailable integration can leave the gateway behavior open while local PRD review and deterministic validation proceed. Move design findings that affect expected behavior back into the PRD with rationale and ownership. Record minor compatible design refinements in the design itself. For a new policy revision, identify which already-tested behavior needs revalidation, for example when A-01 changes the cutoff to 45 days.
Hand off a design that can be resumed
Save the design and requirement revisions, linked criteria, decision evidence, held scopes and the first approved implementation slice. Include the data or schema migration plan where relevant. Prefer a backwards-compatible change that supports the requirements, and name rollback or forward-correction limits. Payment effects are not undone by rolling code back. If a failed rollout leaves pending operations, ensure an owner can determine their state before any replay.
In a fresh session, read the canonical records, compare the design with repository state, and verify that cited evidence and approved scopes are current. If a handoff claims a connector check ran, locate its sanitized result before relying on it. Preserve test failures and unresolved questions with the next action. When requirements change beyond the current design, update the record before describing implementation as conforming.
Upstream license
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
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.
Enso Method Requirements Intake and Testable PRDs
Use the Enso Method to turn source material and stakeholder decisions into an authoritative product requirements document with verifiable acceptance criteria.