diff --git a/agentydragon/prompts/developer.md b/agentydragon/prompts/developer.md
index 867d8d3cca..c476a5e58c 100644
--- a/agentydragon/prompts/developer.md
+++ b/agentydragon/prompts/developer.md
@@ -6,6 +6,7 @@ Use the task Markdown file under `agentydragon/tasks/` as your progress tracker:
 Before making any changes, read the task definition in `agentydragon/tasks/` and note that its **Status** and **Implementation** sections are placeholders.
 
 After reviewing, update the task’s **Status** to "In progress" and fill in the **Implementation** section with your planned approach.
+If the **Implementation** section is blank or does not describe your intended design and steps, populate it with a concise high‑level plan before proceeding.
 Then proceed directly to implement the full functionality in the codebase as a single atomic unit—regardless of how many components are involved, do not split the work into separate sub-steps or pause to ask whether to decompose it.
 
 Do not pause to seek user confirmation after editing the Markdown;
diff --git a/agentydragon/tasks/17-sandbox-precommit-permission-error.md b/agentydragon/tasks/17-sandbox-precommit-permission-error.md
new file mode 100644
index 0000000000..469c47e588
--- /dev/null
+++ b/agentydragon/tasks/17-sandbox-precommit-permission-error.md
@@ -0,0 +1,29 @@
+---
+id: 17
+title: Sandbox Pre-commit Permission Error
+status: Not started
+summary: Pre-commit hooks fail in sandbox due to inability to lock user gitconfig.
+goal: |
+  Investigate and resolve pre-commit setup failures in sandbox environments caused by permission errors on ~/.gitconfig so that pre-commit checks can run reliably within agent worktrees.
+---
+
+> *This task addresses scaffolding/setup for Agent worktrees.*
+
+## Acceptance Criteria
+
+- Pre-commit hooks detect sandbox environment and skip or override gitconfig locking.
+- Documentation in scaffold guides is updated to note pre-commit limitations and workarounds.
+- Verification steps demonstrate pre-commit hooks succeeding in sandbox without modifying user gitconfig.
+
+## Implementation
+
+**How it was implemented**  
+*(Not implemented yet)*
+
+**How it works**  
+*(Not implemented yet)*
+
+## Notes
+
+- The sandbox prevents locking ~/.gitconfig, leading to PermissionError.
+- Consider configuring pre-commit to use a repo-local config or skip locking by passing `--config` or setting `PRE_COMMIT_HOME`.
\ No newline at end of file
diff --git a/agentydragon/tasks/create-task-worktree.sh b/agentydragon/tasks/create-task-worktree.sh
index 8e5d5c25e1..1d957d7ea3 100755
--- a/agentydragon/tasks/create-task-worktree.sh
+++ b/agentydragon/tasks/create-task-worktree.sh
@@ -117,6 +117,11 @@ echo "Done."
 
 if [ "$agent_mode" = true ]; then
   echo "Launching codex agent for task $task_slug in $worktree_path"
+  prompt_file="$repo_root/agentydragon/prompts/developer.md"
+  if [ ! -f "$prompt_file" ]; then
+    echo "Error: developer prompt file not found at $prompt_file" >&2
+    exit 1
+  fi
   cd "$worktree_path"
-  codex "Read the task definition in agentydragon/tasks/$task_slug.md and update its **Status** and **Implementation** sections to make progress on the task. Continue editing the file until the task is complete."
+  codex "$(<"$prompt_file")"
 fi
\ No newline at end of file
diff --git a/agentydragon/tasks/task-template.md b/agentydragon/tasks/task-template.md
index fbf0d6c95e..36782be06c 100644
--- a/agentydragon/tasks/task-template.md
+++ b/agentydragon/tasks/task-template.md
@@ -18,12 +18,13 @@ goal: |
 List measurable criteria for completion.
 
 ## Implementation
-
 **How it was implemented**  
-Provide details on code modules, design decisions, and steps taken.
+Provide details on code modules, design decisions, and steps taken.  
+*If this section is left blank or contains only placeholder text, the implementing developer should first populate it with a concise high-level plan before writing code.*
 
 **How it works**  
-Explain runtime behavior and overall operation.
+Explain runtime behavior and overall operation.  
+*If this section is left blank or contains only placeholder text, the implementing developer should update it to describe the intended runtime behavior.*
 
 ## Notes