Good tasks
Make tasks executable instead of vague.
Safety ruleKeep real user data local. Do not
publish private vault content, secrets, screenshots, or logs.
How to use this
A good task has a next action, definition of done, effort, energy, work mode, useful links, and enough context to resume later. Use task shaping for rough intent, then review before saving.
What remains explicit
Capture, AI, review, import, and agent suggestions require user
approval before durable writes. Configuration should point at
_WorkOS, and reference vaults should remain read-only
unless deliberately reconfigured.