crystallizelisted

# Crystallize ## Overview Use this skill to convert rough input into an implementation plan that another agent can execute without needing the original discussion. The output is a single ignored local Markdown file under the gitignored `plans/` directory. Do not implement the plan while crystallizing. Inspect, research, and reason; only write the plan artifact. ## Plan Artifact Create `plans/` if it does not exist: ```bash mkdir -p plans ``` Choose a unique filename: - Derive a lowercase hyphenated slug from the rough input. - Prefix it with a UTC timestamp from `date -u +%Y%m%d-%H%M%S`. - Use `plans/<timestamp>-<slug>.md`. - If the file already exists, append `-2`, `-3`, etc. Keep `plans/` and every plan file ignored and untracked. Do not add them to git, do not create a tracked placeholder, and do not include plan files in commits. ## Research Wave Launch parallel subagents before drafting the plan. Give each subagent the raw user input, any linked issue or document text, and explicit permission to inspect the workspace. Do not include your intended solution. Use these research roles unless a role is plainly irrelevant: - `CodebaseResearch`: identify affected crates, modules, APIs, tests, docs, and local patterns. Return concrete file paths and constraints. - `HistoryResearch`: use Moraine MCP tools directly when prior or active agent context may matter. Search past sessions by keywords, inspect relevant sessions, and return only actionable history. - `PublicPr