Skip to content

rse/ase / plugin/skills/ase-task-reboot

ase-task-reboot

Verified

Reboot the current or given task plan by re-creating it from scratch. Use when the user calls to "reboot", "recreate" or "refresh" the "task", "plan", "spec", or "specification".

FileKindSize
SKILL.mdskill md10.1 KB
help.mdmarkdown4.5 KB

##  NAME

`ase-task-reboot` - Reboot a Task Plan

##  SYNOPSIS

`ase-task-reboot`
    [`--help`|`-h`]
    [`--next`|`-n` *option*[,...]]
    [`--ground`|`-G`]
    [*id*]

##  DESCRIPTION

The `ase-task-reboot` skill re-creates an existing task plan *from
scratch* by extracting the `DOM` and `IFC` bullet points of the
`SPECIFICATION (WHAT)` section (if present) from the current plan,
using them as the new instruction, re-deriving the `DESIGN (HOW)` and
`VERIFICATION (WHEN)` sections grounded in the relevant specification
(`SPEC`), source code (`CODE`), and infrastructure (`INFR`) files of the
project (naming the actual files and symbols to change, the actual build,
lint, and test procedures, and a `CHANGELOG.md` entry if such a file
exists), preserving the original creation
timestamp, the remaining frontmatter keys, and all attachments, and
writing fresh plan content via `ase_task_save`. As the rebooted plan
starts its lifecycle anew, its `Status:` key is reset to the default
state of the task lifecycle model, all of its bullet points start in
the `[ ]` todo state, all `grilled:` tags are dropped
from its `Tags:` key, and its `Source:`, `Changeset:`, and `Target:`
keys are dropped, so they read as their configured defaults
`project.task.default.{source,changeset,target}`. A plan in a finished
state of the task lifecycle model (like `CLOSED`, `INTEGRATED`, or
`CANCELLED`) cannot start its lifecycle anew and hence is refused
upfront, leaving it untouched.

A plan which does *not* follow the task format (or carries no `DOM` or
`IFC` bullet point) is rebooted from its entire body instead: all of
its existing content is *filed* into the `SPECIFICATION (WHAT)`,
`DESIGN (HOW)`, and `VERIFICATION (WHEN)` sections by classifying
each statement as a `DOM`, `IFC`, `ARC`, `IMP`, `REG`, or `CON` bullet
point, with no statement dropped and missing bullet points derived from
the existing content.

After the reboot, the user is asked whether to stop or hand off to
`ase-task-edit` or `ase-task-implement` (optionally with `--draft`),
unless `--next` pre-selects this choice.

##  OPTIONS

-   `--next`|`-n` *option*[,...]:
    Automatically answer the user dialog for the next step. *option*
    is a single token or a *comma-separated chronological list* of
    tokens; the *first* token is consumed by this skill, and any
    remaining tokens are *forwarded* (via `--next`) to the downstream
    skill so an entire pipeline can be pre-scripted in one shot.
    Recognized tokens at this skill: `none` (default, interactive
    answer required), `DONE` (stop), `EDIT` (hand off to
    `ase-task-edit`), `IMPLEMENT` (hand off to `ase-task-implement`),
    or `DRAFT` (hand off to `ase-task-implement --draft`). Example:
    `--next EDIT,DONE` reboots, hands off to editing, and the editing
    loop will exit immediately.

-   `--ground`|`-G`:
    Ground the re-created plan in facts instead of the world knowledge
    of the model alone: once before the re-creation, the sections
    re-derived from scratch -- `HOW` (`DESIGN`) and `WHEN`
    (`VERIFICATION`), plus `WHAT` (`SPECIFICATION`) for a plan without
    `DOM` or `IFC` bullet points -- are grounded in parallel. Their
    artifacts (`SPEC` and `DOCS` for `WHAT`, `CODE` and `INFR` for
    `HOW`, and the test and CI files for `WHEN`) are scanned for the
    project facts relevant to the plan, and the Internet/Web is searched
    for the established practices, standards, patterns, and pitfalls
    about it. If no usable facts are found, a warning is shown and the
    reboot falls back to model knowledge. It is forwarded on a hand-off
    to `ase-task-edit`, but not on a hand-off to `ase-task-implement`.

##  ARGUMENTS

-   *id*:
    The unique identifier of the task whose plan should be rebooted.
    If omitted, the *current* task id is used.

##  SCENARIOS

-   You want a task plan re-created from scratch
-   You want a fresh plan from the original specification
-   You want planning restarted after a plan degraded
-   You want a free-form or legacy plan filed into the task format
-   You want a fresh plan grounded in project and Web facts

##  EXAMPLES

Reboot the current task plan:

```text
❯ /ase-task-reboot
```

Reboot a specific task and hand off to editing:

```text
❯ /ase-task-reboot --next EDIT hello
```

Reboot the current task plan grounded in the project artifacts and the
Internet/Web:

```text
❯ /ase-task-reboot --ground
```

##  SEE ALSO

[`ase-task-edit`](../ase-task-edit/help.md), [`ase-task-implement`](../ase-task-implement/help.md),
[`ase-task-view`](../ase-task-view/help.md), [`ase-task-delete`](../ase-task-delete/help.md).
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
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: 194kUpdated Claude CodeCodexVerifiedInstall