@${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-format-meta.md @${CLAUDE_SKILL_DIR}/../../meta/ase-common-task.md
Procedure
-
Determine Task:
-
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.
-
React on task id:
-
-
Determine Operation:
-
Determine the current task plan content:
-
-
Reboot Task Plan:
-
Start with (set instruction to empty). Do not output anything.
-
Only output the following and continue processing:
-
Create a new plan from scratch and store the result as by closely following the defined plan format and injecting into it all the information from the , all decisions you derived from the , and the grounding in the project, where:
- every bullet-point starts in the
[ ]todo state, - the
Status:frontmatter key is reset to the default state of the task lifecycle model , as the rebooted plan starts its lifecycle anew, - the frontmatter keys
Group:,Phase:,After:,Assignee:,Kind:, andTags:are taken over from the previous plan verbatim where present, except that allgrilled:tags are dropped fromTags:(the whole key is dropped if no other tag remains), as the grilled plan content is gone, - the
Kind:frontmatter key, if absent in the previous plan, is created by inferring the kind of change from the re-created plan content according to the plan (defaulting toCRAFTING), - the frontmatter keys
Source:,Changeset:, andTarget:are dropped, so they are reset to their configured defaults according to the plan , as the rebooted plan starts its change set flow anew, and - the entire "backmatter" of the previous plan is passed through verbatim.
- every bullet-point starts in the
-
-
Decide Next Step:
-
Determine next step:
Next Step: How would you like to proceed with the plan? DONE: Stop processing. EDIT: Hand off plan to editing. IMPLEMENT: Hand off plan to implementation. DRAFT: Hand off plan to implementation drafting.
-
Check the tool and dispatch accordingly:
-
If is
DONEorCANCEL: Only output the following and then STOP. -
If is
EDIT: -
If is
IMPLEMENT: -
If is
DRAFT:
-
-
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |