How deeply does Prompt Engineering in Practice cover acceptance criteria?

Frames criteria as testable review questions without detailing a scoring procedure.

Acceptance criteria

As explained in Prompt Engineering in Practice

Defined conditions that a result must satisfy to be considered acceptable.

Acceptance criteria state what counts as a good or correct result. In a prompt specification, they let both the user and the model judge the response; they should be testable. Keep them distinct from constraints, which limit the output’s format or scope. section 1.6.1

Feature proposal analysis

A specified analysis prompt asks for technical feasibility, user effect, and implementation risk, then requires a recommendation and confidence level. These requirements make the expected result more assessable than an open-ended request for an opinion. section 1.6.1

How Prompt Engineering in Practice covers it

liveBook manning.com

Read Prompt Engineering in Practice on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

BDD in Action, Second EditionAn acceptance criterion is a condition that a feature or user story must satisfy to be accepted as complete.
liveBook manning.com

Collaborative Software Design: How to facilitate domain modeling decisionsAcceptance criteria are business conditions that an implementation must satisfy for a requirement or user story to be accepted.
liveBook manning.com

Delivering Machine Learning Projects: From design to deploymentAcceptance criteria are conditions that a delivered system or project result must satisfy to be accepted.
liveBook manning.com

Build Financial Software with Generative AI (From Scratch)Conditions that define when a software feature or project outcome is considered complete and acceptable.
liveBook manning.com

Effective Platform EngineeringAcceptance criteria are conditions that a software change must satisfy to be considered acceptable.

Compare how 6 books explain acceptance criteria →

Related concepts

definition of doneused by · A definition of done is an agreed set of criteria that work must satisfy to be considered complete.
user storypart of · A user story is a concise requirement describing a desired software capability, interaction, or outcome from a user’s or stakeholder’s perspective.
business ruleequivalent to · A business rule is a domain-specific policy, condition, or constraint that governs valid data, decisions, actions, or behavior in an organization or its systems.
capabilitymeasures · A capability is an ability or permitted function that enables a person, organization, or system to perform an activity or achieve an outcome.
business contextpart of · Business context is the organizational, operational, market, and strategic circumstances, objectives, and constraints that shape the meaning and priorities of a business activity or decision.
executable specificationproduces · An executable specification is a machine-runnable description of expected system behavior that can automatically verify whether an implementation satisfies its requirements.

This explainer was generated by Manning's knowledge graph from the text of Prompt Engineering in Practice. The section links point to the parts of the book it draws on.