auto-goal

Creates and tracks session goals through the OMP goal tool or slash commands.

111|73|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/autopus-ai/autopus-adk --skill auto-goal-autopus-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-goal
Source: https://github.com/autopus-ai/autopus-adk/tree/main/.omp/skills/auto-goal
Command: npx skills add https://github.com/autopus-ai/autopus-adk --skill auto-goal-autopus-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing goals inside an OMP (Oh My Pi) AI coding session requires knowing which goal surface is supported and how to hand off completed or blocked work. This Skill wraps goal creation, status checks, and completion or blocked handoffs into a single consistent entrypoint. ## Core Features & Use Cases - Goal Creation: Create a new session goal via the goal tool or the /goal slash command. - Status Tracking: Check the current state of an active goal within the OMP session. - Handoff Management: Route completed or blocked goals to the appropriate handoff flow without creating unsupported persisted state. - Use Case: During a long coding session, invoke /auto goal to register a new objective, later check its progress, and finally mark it complete or blocked so the next agent step can pick it up. ## Quick Start Ask the agent to create a new session goal by running /auto goal with a short description of what you want accomplished.

Frequently Asked Questions about auto-goal

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a goal in an OMP session?▼

Invoke /auto goal or /auto-goal with a description of your objective. The skill connects the request to the goal tool or the /goal slash command, depending on which surface the current session supports.

How do I check the status of a goal in OMP?▼

Run the auto-goal entrypoint with a status request. The skill confirms the current session's goal intent and reports the state through the supported goal surface.

What happens when a goal is completed or blocked?▼

The skill routes the goal to a completion or blocked handoff flow. It explicitly avoids creating unsupported persisted state and states any constraints when a surface is unavailable.

Does auto-goal work outside of OMP sessions?▼

No, the skill declares omp compatibility and relies on the OMP goal tool or slash commands. In other environments the goal surfaces it wraps are not available.

Why does auto-goal refuse to persist goal state?▼

The execution contract forbids creating unsupported persisted state. If the session does not support a given goal surface, the skill states the constraint instead of writing state the platform cannot read.