refactorch-phaseslisted

# RefactorCh Phases ## When to Use Use this skill for `refactorch` primary and workflow-private subagents when they exchange compact phase artifacts through Engram. Do not use it for generic refactoring advice, code-smell analysis, Project Profile creation steps, or non-Engram workflows. ## Critical Patterns - This skill owns shared phase transport contracts; agents own routing and phase behavior. - The primary stays thin: route phases, pass artifact references, and summarize results. - Subagents write compact Markdown artifacts to Engram and return only a small routing envelope. - Pass topic-key references between agents; do not pass raw source, full command logs, diffs, or broad excerpts. - Read Engram artifacts with exact topic-key search, then retrieve the full observation before using it. - Write generated artifacts with exact `project`, exact `topic_key`, `scope: "project"`, `type: "architecture"`, and `capture_prompt: false`. - Use topic-key upserts for reusable or evolving artifacts. ## Engram Read/Write Protocol ### Read For each required artifact reference: ```txt mem_search(query: "<exact topic_key>", project: "<project>", scope: "project") mem_get_observation(id: <matched observation id>) ``` Block before phase work if a required artifact is missing or ambiguous. Do not proceed from search preview text. After retrieving the full observation, block if it does not correspond to the exact requested `topic_key` and `project`. ### Write For each generated