Skip to main content
Technology & EngineeringEnso Method88 lines

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.

Quick Summary3 lines
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/requirements-and-prdFull skill: 88 lines
Paste into your CLAUDE.md or agent config

Enso Method: Requirements Intake and Testable PRDs

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.

Establish the requirements record

Use this workflow when a team has a rough brief, stakeholder feedback, or a delivered feature whose intended behavior is hard to reconstruct. Produce a product requirements document (PRD) that a stakeholder can approve and an implementation team can test. Start by locating the repository's existing requirements directory and current revision. If a PRD or an approved change record already owns the capability, amend that record or link a replacement through the project's established process. A newly written document should not silently acquire authority over a working feature.

Collect only relevant material the project is authorized to use. Make a source register with stable IDs, such as SRC-01 for a policy revision and SRC-02 for the stakeholder's intake notes. Record the date, scope, author or role, and a location a reviewer can retrieve. For a lengthy transcript, record the short decision-bearing passage or summarize it faithfully and preserve its location. Keep private source material under its original access rules. A summary with no source or date has limited evidentiary value, especially when several revisions conflict.

For each statement, decide whether it is an observed fact, a decision made by someone with authority, a proposal, or an unanswered question. Technical facts belong in notes or design evidence, with the environment and test that supports them. Put a decision into requirements with its owner and source. Record a plausible but unsettled business answer in the assumption register, with a link back to the criterion it would change. If two authoritative sources disagree, ask who can resolve their scope or priority. Capture both until the conflict is resolved. A newer note can describe a different feature, market, role, or effective date.

Write criteria stakeholders can check

Use language that describes behavior from the caller's or operator's point of view. Each criterion should identify an actor, an event, the relevant state, and the observable result. Give the criterion a stable ID before implementation. Keep that ID when wording changes without changing the obligation. If a new obligation supersedes the old one, record both IDs and the effective revision. Avoid using a broad sentence such as “refunds are reliable” as the only acceptance condition.

Include negative paths that carry a distinct responsibility. For a refund, state what a denied caller can observe, whether the balance stays unchanged, whether any request reached the payment system, and how uncertain state is communicated. A status message alone does not prove the effect. Derive expected values from observable business consequences, and declare whether the check needs a deterministic fixture or a permitted sandbox. Production actions require their own authorization.

A reviewable PRD can use this shape.

Project: Returns
Requirement revision: PRD-returns-r2
Decision owner: Product Operations
Outcome: Support can process a fully eligible refund with recoverable evidence.
Scope: Single full refund to the original payment.
Non-goals: Partial refunds, store credit, and unattended live execution.
Source records: SRC-01 returns policy; SRC-02 authorized operations notes.
Criterion: R-01 | eligible support action | expected state and message
Criterion: R-02 | duplicate delivery | one refund for one approval
Criterion: R-03 | ineligible or denied action | payment unchanged
Criterion: R-04 | ambiguous external result | pending until reconciled
Open assumption: A-01 | eligibility cutoff | affects R-01 and R-03
Verification scope: synthetic records first; approved payment sandbox if needed

Work the Returns example

R-01 says that when a support representative with refund authority submits a full refund for an eligible paid order, the application records the approval and credits the original payment once. A customer-facing or support-facing completion indicator appears only after the application has confirmed the payment outcome. Test with a synthetic paid order inside the eligibility window and a permitted representative. Capture the resulting refund identity, amount, payment destination and local status. If sandbox payment access is unavailable, keep the external handoff case open and record the narrower verification actually performed.

R-02 says that duplicate delivery of the same approval returns the existing outcome or an explicit pending state and does not issue another refund. Test both an ordinary duplicate and a timeout that occurs after submission but before the reply. Verify the payment request count, persisted operation identity and visible state. A different amount or a different order sent under the same approval identity is a conflict. Do not resolve that conflict by pretending it is a retry.

R-03 says that an unsigned, unauthorized, or ineligible request does not change the payment, does not create a committed refund, and returns the appropriate safe result. Test a representative without the refund role and a valid representative with a qualifying order just outside the defined cutoff. Keep authorization and ineligibility separate in test records even if the interface deliberately avoids disclosing details to an unauthorized caller.

R-04 says that when a payment provider may have accepted the operation but its result is uncertain, the application preserves a pending state until authorized reconciliation establishes the outcome. The caller receives a pending status and the stable operation reference. Test an adapter that returns a timeout and later reports the original operation as successful. The same operation becomes confirmed without a second payment request. When no authoritative lookup is available, retain pending and record the unresolved evidence for an authorized operator.

A-01 records the provisional interpretation that eligibility lasts through 30 elapsed 24-hour days from the recorded payment time, evaluated using the recorded request time and a shared UTC clock. For the fixture, exactly 30 days is eligible and 30 days plus one second is ineligible. Link the rationale from the transaction policy and sample records. The assumption is useful for planning and approved fixture work. It does not convert evidence of common past behavior into an approved policy. If the stakeholder changes it to 45 days, update the canonical criterion references, boundary cases and affected phase records. Keep the old 30-day expectation in the revision history so a reviewer can explain the change.

Refine and hand off

Read the PRD once as a stakeholder and once as a verifier. Check that the outcome and scope are stated in ordinary language, that every meaningful claim is sourced or provisional, and that criteria can be checked without knowing which code the team plans to write. Compare against the current product. Name behaviors, users and records that must keep working, even if the new request does not mention them. Confirm that R-01 and R-03 share the same time rule and that R-02 covers repeated payment effects rather than only duplicated clicks.

Keep the requirements as the source of truth for permitted business behavior. Technical design can describe the chosen architecture, reference implementation details and surface constraints. If a constraint forces a product behavior change, amend the requirement first and record who agreed. Store open questions separately enough that readers can tell whether they are looking at obligations or candidates. Keep only a brief decision history in the PRD itself, with durable links to signed-off material when available.

Use the repository’s established paths. In a new Returns folder, keep the PRD in requirements.md, the design in technical-design.md, the assumption register in assumptions.md, and phase, evidence, and handoff records alongside them.

Hand off the PRD path and revision, known and pending decisions, criteria affected by assumptions, and the next check that establishes readiness. If evidence is missing, name the exact document, policy owner, or fixture operation needed. A blocked criterion can remain open while the team proceeds on separable, authorized work. When starting a later session, use the checked-in or otherwise authoritative requirements, read the decision history and current artifact state, and reconcile any work already completed before choosing the next step.

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

Get CLI access →