Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Design the output contract for a task extractor using only these invented note samples: [notes]. The application needs to identify requested actions and preserve what the note actually states.
Define the fields, their meanings, allowed status values, and the representation of a missing due date. Distinguish no task found from an extraction failure. Require a source-sentence reference for every extracted task, and define what happens when a date is contradictory or cannot be interpreted from the supplied context.
Provide a plain-language contract plus representative valid outputs. Include fixtures that have valid structure but violate meaning, such as an invented deadline or a citation to a different task.
If a schema is appropriate, identify which rules it expresses and which need application validation. Do not claim that a schema proves factual correctness or authorizes storing the result. Keep provider-specific syntax separate from the contract.Make this prompt yours
Use when extracted output feeds code. Adapt the schema to the actual provider and validate the task rules independently.
You might also hear
- task extraction contract
- missing date prompt
- semantic validation
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
Research sources reviewed .
Editorial review · October 28, 2026
Supported: Original, unexecuted extraction template. It preserves unknown dates and asks for application checks, consistent with structured-output limitations; format alone is not treated as truth.