goalifylisted
Install: claude install-skill Aboudjem/goalify
# goalify
## Overview
Prepare the **best possible `/goal` execution file** in THIS session, then hand off so the user can
`/clear` and run it with `/goal <path>` in a fresh session that has full context to work in.
**Core principle — two phases, never mix them:**
- **PREPARE (here, now):** understand the project, scope the work, fan out research subagents, ask the
user only the decisions you genuinely can't infer (one interactive MCQ batch), then author a
self-contained, self-deleting goal MD. Keep your own output short.
- **EXECUTE (later, after `/clear`):** the user runs `/goal <abs-path>`; that fresh session does the
heavy autonomous work the MD describes (fanning out its own subagents) and deletes the MD when done.
You are doing the PREPARE phase. Do **not** start the heavy implementation here — produce the MD and the
handoff. The MD is where execution lives.
## Invocation
Triggered by natural language (e.g. "goalify this: <task>") or as the slash command `/goalify <task>`.
When invoked as a command, **`$ARGUMENTS`** is the task the user wants a `/goal` file for — treat it as the
objective and begin the PREPARE phase below. If no task is given, infer it from the recent conversation, or
ask once (one line) what to goalify.
## When to use / not
- **Use when:** a substantial, well-specified task should run autonomously in a clean session; the user
says "goalify", "prep a goal", "make the md for /goal", or wants research-backed scoping + a
self-deletin