ase-task-condense

@${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

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:

      Set (remember the loaded plan content for the strictly-shorter check in step 3).

3. Condense Task Plan:

   1. Apply the condense ruleset to , producing a shorter . The goal is to make the plan require as little reading as possible while all semantics remain fully preserved and unchanged. Honor the following ruleset strictly:

      1. Preserve-exactly (never alter): the plan structure (the frontmatter block with its Id:, Created:, Modified:, Status:, Properties:, and Kind: keys, the headings #/##, all three ## CONTEXT, ## CHANGES, and ## VERIFICATION sections, and the - **<aspect/>**: bullet labels), all code spans and code blocks, technical terms, file paths, identifiers, numbers, severities (LOW/MEDIUM/HIGH/ACCEPTED), and the *<aspect/>* emphasis highlighting convention.

      2. Compress free-text only (the **WHAT**/**WHY** prose and each bullet's <specification/> text):

         • Drop filler ("just", "really", "basically", "simply"), pleasantries, and hedging ("I think", "maybe", "perhaps").
         • Use shorter synonyms and common abbreviations.
         • Use → for causality and - for short subsequent facts.
         • Drop articles ("a", "an", "the") and replace conjunctions with short separate clauses where this shortens the text without introducing ambiguity.
         • Re-wrap the shortened free-text to the ~100-character- per-line convention of the plan , but never break a line inside an inline code span.
         • Merge genuinely-redundant bullets (the same aspect restated) and drop pure duplication -- but only when truly redundant; never lose a distinct aspect.

      3. Persona override: this condense ruleset always wins for the plan content. This ruleset-based compression is applied regardless of the currently active session persona style.

      4. Hard guardrail -- semantics preserved EXACTLY: condensing only shortens wording. It MUST NOT drop, merge (except truly-redundant bullets per sub-item 2), reorder, or alter any factual claim, requirement, file path, rule, or example. If a shortening would change meaning, keep the longer wording.

   2. Persist only if smaller: call the ase_text_metric(text: "<text/>") tool of the ase MCP server once for the condensed and once for , and take the chars field of each result, so the comparison rests on a measured length instead of an estimate.

4. Decide Next Step:

   1. Determine next step:

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

   2. Check the tool and dispatch accordingly:

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

      • If is EDIT: Only output the following and then call the tool Skill(skill: "ase:ase-task-edit", args: "<args/>") to invoke the ase:ase-task-edit skill in order to edit the condensed plan. Immediately stop processing the current skill once the Skill tool was used.

      • If is IMPLEMENT: Only output the following and then call the Skill(skill: "ase:ase-task-implement", args: "<args/>") tool to apply the plan.

      • If is PREFLIGHT: Only output the following and then call the Skill(skill: "ase:ase-task-preflight", args: "<args/>") tool to apply the plan.