Bound the reusable work module
The work assignment is to make instructions reproducible, testable and maintainable. Define purpose, owner and permitted operating boundary before the first test.
The domain review baseline covers goal, context, boundaries, examples, output format and evaluation. Assumptions and missing information remain visible in the result.
Develop instructions using examples
- Describe the desired result and its acceptance criteria before writing the instructions themselves.
- Add only required context and define boundaries and handling of missing information.
- Test examples and a concrete output format against typical tasks and edge cases.
- Version instructions and tests and revise unclear rules using observed failures.
Demonstrate repeatability
A fixed test set shows that typical tasks produce the agreed output and edge cases keep missing information visible. Instruction changes have a documented review result.
Avoid: long prompt text without clear acceptance criteria. Additional text length does not improve reviewability while the expected output and acceptance decision remain unclear.
Decision matrix
| Decision point | Proceed when | Stop when |
|---|---|---|
| Assignment and inputs | Documented: goal, context, boundaries, examples, output format and evaluation. | Scope, data or accountability remains unresolved. |
| Repeatability | A fixed test set shows that typical tasks produce the agreed output and edge cases keep missing information visible. Instruction changes have a documented review result. | There is only an unevaluated demo without acceptance evidence. |
| Maintenance and boundaries | Owner, approval, fallback and next review date are defined. | Avoid: long prompt text without clear acceptance criteria. Additional text length does not improve reviewability while the expected output and acceptance decision remain unclear. |
Keep it verifiable
Primary sources
- Microsoft: RAG prompt engineeringSource checked:
- Agent Skills: SpecificationSource checked:
