ase-task-preflight

@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.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-tenets.md @${CLAUDE_SKILL_DIR}/../../meta/ase-common-code.md

Procedure

1. Determine Task:

   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 task id:

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. Internalize the tenets stated by the plan:

3. Create Implementation Draft:

   1. Perform a preflight of the implementation of by creating a draft for a corresponding, complete artifact change set which would fully implement the task plan . Store this artifact change set in unified diff format in .

      Create this draft with the same rigor as the final implementation of the companion skill ase-task-implement, because that skill later takes the draft over 1:1 -- the user is assumed to review the draft in between. Hence read the current content of every artifact the draft touches before drafting its hunks, so all context lines match the artifacts exactly and the diff would apply cleanly, and honor the task plan and the internalized tenets just as the final implementation would. Only the actual modification of the artifacts and the verification phase are deferred to ase-task-implement.

   2. Append this artifact change set to the end of the with the following . If a section named ## IMPLEMENTATION DRAFT already exists from a previous run of this skill, replace this entire existing section.

      Set to a run of backtick characters one longer than the longest backtick run occurring anywhere inside , but to at least three, so a diff which itself carries fenced code blocks (e.g. one over Markdown artifacts) cannot terminate the block prematurely.

      IMPLEMENTATION DRAFT

      text

   3. Update with the current time in ISO-style format, which has to be determined by calling the ase_timestamp(format: "yyyy-LL-dd HH:mm") tool of the ase MCP server and using the text field of its response. Update the Modified: ... frontmatter key of with the new value, creating the whole key at its position in the key order of the plan if the plan does not carry it yet. Do not output anything.

      Additionally add the value preflighted to the Properties: frontmatter key of if it is still absent, keeping all already present values and creating the whole key (with the single value preflighted) if the plan carries none. Do not output anything.

   4. Finally, call the ase_task_save(id: "<ase-task-id/>", text: "<task-content/>") tool of the ase MCP server to save the updated task plan content. This ase_task_save MCP tool call is the only permitted way to persist the plan -- NEVER write the plan file via Write/Edit or by executing a shell command. Do not output anything related to this MCP tool call except the following :

4. Decide Next Step:

   1. Determine next step:

      Next Step: How would you like to proceed with the plan? DONE: Stop processing. EDIT: Hand processing off to editing. IMPLEMENT: Hand processing off to implementation.

   2. Check the tool and dispatch accordingly:

      • If is DONE or CANCEL: Only output the following and then STOP.

      • If is EDIT:

      • If is IMPLEMENT: