RISEN 🟡
Need: A comprehensive response with a clear end goal and scope narrowing.
Explanation: Role → Instructions → Steps → End goal → Narrowing. An extended CRISPE with emphasis on step sequence and constraints.
Prompt format:
“Role: [who]. Instructions: [what to do]. Steps: [sequence]. End goal: [deliverable]. Constraints: [limits].”
QA usage example
“Role: QA consultant. Instructions: prepare a regression test plan. Steps: 1) critical paths, 2) priorities, 3) effort estimation. End goal: document ready for review. Constraints: max 20 test cases, happy path + top 5 production bugs.”
RISEN vs CRISPE — which to choose?
| Aspect | CRISPE | RISEN |
|---|---|---|
| Emphasis on | Role and response style | Step sequence and constraints |
| Better for | Reviews, analysis, expertise | Plans, documents, deliverables |
| Complexity | Medium | Medium-high |
RISEN works best when you have a concrete deliverable — a test plan, a report, a document for review — and you want to clearly define the scope.
Advanced example
“Role: Test Architect. Instructions: design a test strategy for microservices. Steps: 1) identify critical business paths, 2) propose testing levels (unit, integration, contract, E2E), 3) define tooling, 4) plan CI/CD integration. End goal: test strategy document ready for team presentation. Constraints: 12 microservices, Java 17 + Spring Boot, budget for max 2 commercial tools.”
In the next post: ReAct+ and Tree of Thought — entering advanced agent-level frameworks.