{"CACHEDAT":"2026-04-14 02:21:04","SLUG":"handling-actions-documentation-esp-regarding-execution-information-xl2aNUU936","MARKDOWN":"# 1. Reopen the Action Before Working on It\n\nBefore editing or continuing work on any Action, **reopen it first**. The description may have been updated (e.g. corrected instructions, new participants, or added context). This avoids relying on separate reminders.\n\n\n---\n\n# 2. Check for Description Updates and Dependencies\n\n* **Execution-relevant information** is always in the **Description** — check for any recent updates.\n* **Watch for blocking or linked Actions**: Even if an Action looks ready, verify whether it's still blocked or depends on another task.\n* **Linked Actions** often contain important documents or context (also check Participants tab).\n\n\n---\n\n# 3. Update Key Execution Info in the Description\n\n* Always **document action-specific updates directly in the Description** (e.g. \"Update 2025-08-04\").\n* If important info is shared in a **comment on a related Action**, copy it into the **Description** here. Others may overlook comments when continuing the work.\n\n\n---\n\n# 4. [Document Relevant Information Systematically](/doc/what-to-document-where-qn6ah7fIMT)\n\n* **Action-specific info (required to complete the task)** → use the **Action Description**\n* **Discussions, clarifications** → use **Comments**\n* **Cross-project or long-term relevant info** → document in the **Wiki**, and:\n * Add a **link to the Wiki** in the Action Description\n * Include a \"**Last Update here: \\[date\\]**\" section\n * Copy the content into the Description so it remains **searchable in Hive**, while the **Wiki** holds the most up-to-date version","HTML":"
Before editing or continuing work on any Action, reopen it first. The description may have been updated (e.g. corrected instructions, new participants, or added context). This avoids relying on separate reminders.
\n