Menu
Drive Sloppy persistent session goals through extension-backed metadata instead of hardcoded planning policy.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Use GPT-5.5 and Claude Opus 4.7 ACP sub-agents in an iterative planner/auditor/implementer loop for development tasks.
Coordinate Sloppy child agents through the delegation provider without polling, including parent-side parallel work, result retrieval, and child-session cleanup.
Review skill usage, failures, and repeated procedures, then propose minimal skill changes through the skills provider.
Diagnose failed meta-runtime route dispatch and propose minimal route or endpoint repairs.
Design Sloppy meta-runtime topology changes through ordinary SLOP proposals instead of hardcoded repair policy.
Evaluate meta-runtime topology experiments using explicit evidence and promotion criteria.
Basé sur la classification professionnelle SOC
| name | persistent-goal |
| description | Drive Sloppy persistent session goals through extension-backed metadata instead of hardcoded planning policy. |
| version | 1.0.0 |
| metadata | {"sloppy":{"tags":["runtime","goal","extension"],"category":"runtime","extension":{"namespace":"goal","schema_version":1,"cleanup":{"mode":"ttl","ttl_ms":604800000,"description":"clear_goal removes live state immediately; completed goals are retained briefly for audit."}}}} |
Use this skill when a persistent session goal is active or when the runtime asks you to continue one.
/goal as the public projection and /extensions/goal as the durable backing metadata.slop_goal_update.progress when work moved forward and more work may remain.blocked when the next action cannot proceed without external input, missing credentials, missing files, or unavailable tools.complete only when the objective is genuinely satisfied and evidence is available.The runtime removes live goal metadata when clear_goal is invoked. Completed goal records may remain until their retention window expires so UIs and operators can inspect the outcome. Do not delete extension metadata merely because this skill was not loaded for a turn; request cleanup only when the goal is complete, obsolete, or explicitly cleared by the user.
Before marking complete, check that the requested outcome is visible in public state, files, tests, or provider results. If verification cannot be performed, report the limitation as evidence instead of claiming completion.