diff --git a/skills/creating-tasks-through-lunatask/SKILL.md b/skills/creating-tasks-through-lunatask/SKILL.md
index 5d9f61c732bbc1f82ca33657625f2f976ac47781..d4c0366dcd80187daf7cdb936a241061c7c11423 100644
--- a/skills/creating-tasks-through-lunatask/SKILL.md
+++ b/skills/creating-tasks-through-lunatask/SKILL.md
@@ -31,13 +31,13 @@ Titles must be clear:
 
 Examples:
 
-- `Accept 'complete' as status alias in lune`
+- `Accept 'completed' as status alias in lune`
 - `Implement ACP event sink in Crush`
 - `Investigate why lune habit track silently fails`
 
 ### Status
 
-New tasks usually get status `later`.
+New tasks usually get status `later`. When beginning work on a task, update to `in-progress`, then completed when done (or use `done` shortcut).
 
 ### Note structure
 
diff --git a/skills/resuming-work-through-lunatask/SKILL.md b/skills/resuming-work-through-lunatask/SKILL.md
index 967cd22f2a42ba09a2f8ce4940e2f5b002aec16b..f27987d0c1f17b4914c4747cb0c08e6ba91373f4 100644
--- a/skills/resuming-work-through-lunatask/SKILL.md
+++ b/skills/resuming-work-through-lunatask/SKILL.md
@@ -38,7 +38,9 @@ Don't derail the primary task, but don't let useful observations vanish either.
 
 ## Workflow
 
-When you begin working on the task, update its status according to the area's workflow. When finished, mark it `complete`.
+When you begin working on the task, update its status according to the area's workflow. When finished, mark it `completed`.
+
+New tasks usually get status `later`, then `in-progress`, then lastly `completed`. Different workflows might have other stages, but those are core.
 
 ## Working around a Lunatask bug