designing-workflowlisted

# Designing Workflow The canonical six-phase menu for rageatc-core-oss — every workflow subsets from these phases based on task characteristics. This skill covers structure (which phases, when); execution (agent coordination, logging, validation) lives in `orchestrating-work`. ## Phase Menu ### Phase 1: Preparation (always) Understand requirements, explore context, identify the execution approach. The full arc is Ideate → Understand → Solution → Brief, each step optional: - `ideating` — generate and explore ideas when the user doesn't yet have a clear task - `understanding-the-ask` — explore user intent through structured dialogue - `solutioning` — explore solution options when the approach is unclear - Exploratory research via subagents, reading referenced documents, clarifying ambiguities and constraints Outputs: clear understanding of requirements; decision record if solutioning was used; captured ideas if ideating was used. ### Phase 2: Planning (always — spend the most user time here) Create the execution plan for orchestrator and user — NOT for agents, who receive instructions at invocation. Leverage the plan agent, review the plan with the user, identify decision points, dependencies, agent sequence, and file paths. If planning is done right, everything else flows smoothly. Output: `work/<task-id>/plan.md`. ### Phase 3: Research (optional) Background investigation, fact-finding, evidence gathering. Include for novel domains, unfamiliar problem spaces, or fac