From c5517e1866f0bb6ac64cdeccd5dadf68981ca456 Mon Sep 17 00:00:00 2001
From: KtorZ <matthias.benkort@gmail.com>
Date: Mon, 4 Mar 2019 15:28:35 +0100
Subject: [PATCH] re-introduce 'Acceptance Criteria' as part of the issue
 template

---
 .github/ISSUE_TEMPLATE/task.md | 15 +++++++++++++--
 1 file changed, 13 insertions(+), 2 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/task.md b/.github/ISSUE_TEMPLATE/task.md
index db69a1156a0..fcc9a5a6589 100644
--- a/.github/ISSUE_TEMPLATE/task.md
+++ b/.github/ISSUE_TEMPLATE/task.md
@@ -6,7 +6,7 @@ about: Create a new Task
 
 # Context
 
-<!-- WHEN PROPOSED
+<!-- WHEN CREATED
 What is the issue that we are seeing that is motivating this decision or change. 
 Give any elements that help understanding where this issue comes from. Leave no 
 room for suggestions or implicit deduction.
@@ -15,13 +15,24 @@ room for suggestions or implicit deduction.
 
 # Decision
 
-<!-- WHEN PROPOSED
+<!-- WHEN CREATED
 Give details about the architectural decision and what it is doing. Be
 extensive: use schemas and references when possible; do not hesitate to use
 schemas and references when possible.
 -->
 
 
+# Acceptance Criteria
+
+<!-- WHEN CREATED
+Use standard vocabulary to describe requirement levels RFC-2119: Must-Should-May.
+
+e.g. 
+
+1. The API _must_ support creation of wallets through a dedicated endpoint.
+-->
+
+
 
 ---