--- /dev/null
+## PR Checklist
+Please check if your PR fulfills the following requirements:
+
+- [ ] The commit message follows the ground rule
+- [ ] Tests for the changes have been added (for bug fixes / features)
+
+
+## PR Type
+What kind of change does this PR introduce?
+
+<!-- Please check the one that applies to this PR using "x". -->
+
+- [ ] Bugfix
+- [ ] Feature
+- [ ] Code style update (formatting, local variables)
+- [ ] Refactoring (no functional changes, no api changes)
+- [ ] Build related changes
+- [ ] CI related changes
+- [ ] Documentation content changes
+- [ ] Other... Please describe:
+
+
+## Why need this change?
+
+<!-- Please describe the current behavior that you are trying to fix or improve, -->
+<!-- or link to a relevant issue (Github issue, KONA, PLM, etc.) -->
+
+- Issue Number: << Github issue URL, KONA ID, PLM ID, etc. >>
+- << Abnormal operation due to A ... >>
+- << App wants D but we provide up to C ... >>
+- ...
+
+
+## Changes made
+
+<!-- Update Version when PR type is Bugfix or Feature, otherwise you can remove it -->
+<!-- Versioning Rule: It follows Semantic Versioning. (https://semver.org) -->
+<!-- Major Version is fixed to 1, since ESPP's managed API always guarantee compatibility.-->
+<!-- Minor Version is increased when new ESPP managed API is created or Feature is implemented.-->
+<!-- Patch Version is increased when there is internal modification or Bugfix.-->
+
+- Version: << 1.X.Y >>
+
+<!-- Write detailed explanation about your change below -->
+
+- << Changed A to B ... >>
+- << Modified C to D ... >>
+- ...
+
+## Test Scope / Change impact
+
+<!-- Provide the test scope when PR type is Bugfix or Feature -->
+<!-- Provide change impact if there is managed API modification -->
+
+- << Run MAPI TC with updated test code ... >>
+
+
+
+## Other information