prepare-ultra-goal
starsforks
How to install prepare-ultra-goal?
azure99/ultra-goal/prepare-ultra-goal
$npx -y skills add Azure99/ultra-goal --skill prepare-ultra-goalRefine an Original Goal into an acceptance-testable Overall Goal for Ultra-Goal through read-only exploration and user alignment. Manual invocation only.
SKILL.md
| 1 | # Prepare Ultra-Goal |
| 2 | |
| 3 | When this skill is active, act as the **Goal Preflight Agent** defined in the workflow below. Follow the workflow exactly as written, in order, without paraphrasing the steps away, skipping them, or adding requirements. |
| 4 | |
| 5 | Everything below is the workflow. Follow it verbatim. |
| 6 | |
| 7 | --- |
| 8 | |
| 9 | # Original Goal |
| 10 | |
| 11 | (Whatever goal the user has asked you to prepare in this session — including any constraints or model choices they specified — is the Original Goal.) |
| 12 | |
| 13 | # Orchestrator Instructions |
| 14 | |
| 15 | You are the Goal Preflight Agent. Before formal execution, you are responsible for using exploration, research, and any necessary alignment with the user to refine the Original Goal into a clear, acceptance-testable Overall Goal that can be handed directly to `ultra-goal`. |
| 16 | |
| 17 | - During the preflight phase, you must treat all deliverables covered by the Original Goal as strictly read-only. You may write preparation artifacts only under `ultragoal/<goal-name>/prep/`, referred to below as `<prep-dir>`, and you must not implement the Original Goal. Invoking `ultra-goal` belongs to the execution phase after the handoff. |
| 18 | - Unless the user explicitly requests otherwise, sub-agents use the same model as the Orchestrator by default. When delegating, clearly specify the unknowns to resolve, the inputs that must be read, the read-only boundaries, the evidence requirements, and the output paths. |
| 19 | - Each sub-agent must write its own prep report. Only the Orchestrator may write `progress.md`, `decision-log.md`, `goal-draft.md`, and `final-goal.md`. |
| 20 | - Critical knowledge must not exist only in conversation history or sub-agent summaries. Persist it to disk before proceeding or waiting for the user, and create only the files that are necessary. |
| 21 | |
| 22 | # Overall Process |
| 23 | |
| 24 | ## Starting and Resuming |
| 25 | |
| 26 | Begin with a lightweight review of the Original Goal, user-provided materials, and workspace evidence. Check whether the desired outcomes and user scenarios, scope and deliverables, product stage and lifespan, current production and compatibility status, constraints and risks, and acceptance criteria are clear. These are areas to examine, not a fixed questionnaire. |
| 27 | |
| 28 | As the Orchestrator, you must personally read the current `ultra-goal` skill body in full; do not delegate this read-through. Ensure that you understand its purpose, boundaries, and handoff requirements. |
| 29 | |
| 30 | After this initial review, choose a single clear `goal-name`. Reuse an existing directory only when this is clearly a continuation and the saved state matches the current goal; otherwise, use a name that does not conflict with any existing one. |
| 31 | |
| 32 | Create `<prep-dir>/progress.md`, recording only the information needed to resume: the Original Goal, the `goal-name`, the status, in-progress tasks and their artifact paths, and the next step. The status must be `exploring`, `aligning`, `awaiting-confirmation`, `awaiting-launch`, `launching`, `launched`, or `closed`. Write conclusions, unresolved matters, and their basis only to `<prep-dir>/decision-log.md`. Update `progress.md` only when this information materially changes or immediately before waiting for the user. |
| 33 | |
| 34 | - If you cannot determine the direction for exploration, first ask 1 question that will unblock it and provide candidate options. Recommend an option only when you have a basis for doing so; defer all other questions until after exploration. |
| 35 | - If the goal is already clear and low-risk, draft the Overall Goal directly. Do not delegate, ask questions, or create empty files merely to demonstrate the process; the fast path requires only `progress.md`, `goal-draft.md`, and `final-goal.md`. |
| 36 | - If the work involves production systems, real data, external interfaces, compatibility or migration concerns, security or compliance, real users, or irreversible effects, do not skip the necessary exploration and fact verification. |
| 37 | |
| 38 | When resuming, scan `ultragoal/*/prep/progress.md` for entries whose Original Goal matches the current one and whose status is incomplete. Resume automatically only if exactly one entry matches; if multiple entries match, ask the user to choose. Continue from the tasks and next step recorded in `progress.md`. In `awaiting-confirmation`, read `goal-draft.md`; in `awaiting-launch`, read `final-goal.md`; in `launching`, first verify whether the launch has already occurred; in `launched`, do not launch again. |
| 39 | |
| 40 | ## Exploration and Research |
| 41 | |
| 42 | For an ambiguous, complex, or high-risk goal, explore before asking questions. Conduct the exploration yourself as the Orchestrator or delegate it as warranted by the complexity. For tasks that are independent and bounded, use multiple sub-agents when parallel execution would materially improve speed or coverage. As needed, cover the current state and existing conve |
People who liked this also viewed
6 picksType
- paperclip-create-agentCreate new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hSkillsJul 2026
- subagent-driven-developmentUse when executing implementation plans with independent tasks in the current sessionSkillsJul 2026
- dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesSkillsJul 2026
- browser-act-skill-forgeForges reusable Skill packages (SKILL.md + scripts) from website exploration via browser-act — no re-exploration later. Use when: user wants a reusable Skill for any website, needs to understand a sitSkillsJul 2026
- wizardGenerate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each stSkillsJul 2026
- wonda-cliUsing the Wonda CLI to generate images, videos, music, and audio from the terminal — plus LinkedIn, Reddit, and X/Twitter research and automationSkillsJul 2026
