ase-code-resolve

@${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 <skill name="ase-code-resolve"> Resolve Problem </skill> <expand name="getopt" arg1="ase-code-resolve" arg2="--auto|-a --dry|-d --quick|-Q --next|-n=(none|DONE|EDIT|GRILL|PREFLIGHT|IMPLEMENT)..."> $ARGUMENTS </expand> <if condition="<getopt-option-quick/> is equal `true`"> The `--quick`/`-Q` flag is a *shorthand alias*: set <getopt-option-auto/> to `true`, <getopt-option-dry/> to `true`, and <getopt-option-next/> to `IMPLEMENT,DELETE`. Do not output anything. </if> <objective> *Resolve* the following problem: <problem><getopt-arguments/></problem> </objective> @${CLAUDE_SKILL_DIR}/../../meta/ase-format-task.md @${CLAUDE_SKILL_DIR}/../../meta/ase-tenets.md Procedure --------- You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any filesystem-modifying tool during this entire skill. The *only* permitted way to persist artifacts is via `ase_task_save(...)`. <flow> 1. <step id="STEP 1: Reason About Problem"> 1. If <problem/> matches the regexp `^[PT]\d+$` (i.e. a bare issue identifier like `P1`, `P2`, `T1`, `T2`, ...), set <problem-id><problem/></problem-id> and <ase-task-id><problem/></ase-task-id>, then call the `ase_kv_get(key: "ase-issue-<problem-id/>")` tool of the `ase` MCP server to retrieve the previously persisted ...