From 7172771da519be4f6ed46cbe70a3fe13e8351557 Mon Sep 17 00:00:00 2001
From: amaynez <78620790+amaynez@users.noreply.github.com>
Date: Sat, 13 Sep 2025 13:37:36 -0600
Subject: [PATCH 1/2] Create review.md

---
 templates/commands/review.md | 9 +++++++++
 1 file changed, 9 insertions(+)
 create mode 100644 templates/commands/review.md

diff --git a/templates/commands/review.md b/templates/commands/review.md
new file mode 100644
index 00000000..2e659e3f
--- /dev/null
+++ b/templates/commands/review.md
@@ -0,0 +1,9 @@
+---
+description: Review the tasks.md file to find inconsistencies between what we planned to do and what were planning to do next.
+---
+
+Now I want you to go and audit the implementation plan task.md and the implementation detail files.
+Read through it with an eye on determining whether or not there is a sequence of tasks that you need to be doing that are obvious from reading this.
+Because I don't know if there's enough here. For example, when I look at the core implementation,
+it would be useful to reference the appropriate places in the implementation details where it can find the information as it walks through each step in the core implementation
+or in the refinement.

From 897cbd339eede315bc9d845e0102f01be184da64 Mon Sep 17 00:00:00 2001
From: amaynez <78620790+amaynez@users.noreply.github.com>
Date: Sat, 13 Sep 2025 13:40:24 -0600
Subject: [PATCH 2/2] Create implement.md

---
 templates/commands/implement.md | 30 ++++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)
 create mode 100644 templates/commands/implement.md

diff --git a/templates/commands/implement.md b/templates/commands/implement.md
new file mode 100644
index 00000000..ab3c01c9
--- /dev/null
+++ b/templates/commands/implement.md
@@ -0,0 +1,30 @@
+---
+description: Implementation of tasks in the claude project. Use the tasks.md file to follow the plan
+---
+
+Implement the tasks listed in the tasks.md file from the spec directory the user provided.
+
+# Task Instructions
+
+Follow these instructions to execute the next task not marked as complete:
+
+## Executing Instructions
+
+- Before executing any tasks, ALWAYS ensure you have read the spec.md file and the optional plan.md, research.md, quickstart.md and data-model.mdfiles. Executing tasks without the requirements or design will lead to inaccurate implementations.
+- Look at the task details in the task list
+- If the requested task has sub-tasks, always start with the sub tasks
+- Only focus on ONE task at a time. Do not implement functionality for other tasks.
+- Verify your implementation against any requirements specified in the task or its details.
+- Once you complete the requested task, update the task.md file.
+- DO NOT ASSUME USER PREFERENCES OR REQUIREMENTS - ASK EXPLICITLY!
+
+Remember, it is VERY IMPORTANT that you only execute one task at a time.  
+
+IMPORTANT EXECUTION INSTRUCTIONS
+
+- You MUST NOT assume user preferences or requirements - always ask explicitly.
+- You MUST maintain a clear record of which step you are currently on.
+- You MUST NOT combine multiple steps into a single interaction.
+- You MUST ONLY execute one task at a time.
+- You MUST NOT skip any steps or assumptions.
+- You MUST verify your implementation against the requirements before moving on to the next step.