ase-task-dissect

@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md

$ARGUMENTS

@${CLAUDE_SKILL_DIR}/../../meta/ase-format-task.md @${CLAUDE_SKILL_DIR}/../../meta/ase-common-task.md @${CLAUDE_SKILL_DIR}/../../meta/ase-common-dissect.md

Procedure

1. Determine Task and Hint:

   1. Set initially, with any leading and trailing whitespace stripped. Inherit the always existing from the current context. Inherit the always existing from the current context. Do not output anything.

   2. React on the task id:

      The lone token is the task id (with an optional and ignored trailing :), never a hint. Set (set task id to instruction, with any trailing : stripped) and (set instruction empty), call the ase_task_id(id: "<ase-task-id/>", session: "<ase-session-id/>") tool from the ase MCP server to switch the task, and then only output the following :

      Set (set instruction to text) and (set task id to id), call the ase_task_id(id: "<ase-task-id/>", session: "<ase-session-id/>") tool from the ase MCP server to switch the task, and then only output the following :

   3. React on the dissection hint:

      Set (set the dissection hint to the remaining instruction), with any leading and trailing whitespace stripped.

2. Determine Operation:

   1. Determine the current task plan content:

   2. If the is still empty, complain and tell the user to use the ase-code-resolve, ase-code-refactor, ase-code-craft, or ase-task-edit skills first to create a task plan. Then immediately stop processing this skill.

3. Dissect Task Plan:

   1. Derive the parts of the epic:

      <expand name="dissect-derive" arg1="ase-task-dissect" arg2="" arg3=""

      the individual bullet points of the ## CHANGES and ## VERIFICATION sections of the loaded plan

      Each ## VERIFICATION bullet point MUST land in the very part which carries the ## CHANGES bullet points it verifies.

      A single bullet point is not the smallest unit here: a bullet point which itself covers multiple domains or concerns MAY be split per rule 3 into two or more bullet point fragments, each of which is a complete bullet point of its own, is formed exclusively from the wording of the original bullet point, and is then assigned to a part like an ordinary bullet point. A split ## VERIFICATION bullet point follows the ## CHANGES bullet points its fragments verify, so its fragments MAY land in different parts.