Organize workspace policies by task

docs/planning.md

@@ -1,7 +1,9 @@
 # Planning and Progress
 
 - Read and follow [the workspace conventions](conventions.md) before preparing
-  or revising any roadmap or implementation plan.
+  or revising any roadmap or implementation plan. Also read the specialized
+  policy applicable to the planned work: [the Ansible house style](ansible.md),
+  [the testing house style](testing.md), or both.
 - Update [the MVP roadmap](roadmap/mvp.md) when a design question becomes a
   settled scope or architecture decision.
 - Discuss and select the next unit of work before planning implementation.
@@ -28,7 +30,9 @@
   GPT-5.6-Terra to execute sequentially. Number stages with consecutive
   integers beginning with `Stage 1`; do not skip numbers or use nested stage
   numbering. Each stage must identify its repository, preconditions, required
-  behavior, validation, completion criteria, and expected commit.
+  policy reading, behavior, validation, completion criteria, and expected
+  commit. Direct the implementing agent to reread the applicable policy
+  documents immediately before beginning each stage.
 - Resolve architectural choices during roadmap and plan review. Do not leave
   unresolved design judgment to the implementation agent.
 - Update [workspace status](status.md) when cross-repository work starts,