handsoff

Automate the ultrapack hands-off workflow with reversible git operations and decision logging.

47|12|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/btseytlin/ultrapack --skill handsoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handsoff
Source: https://github.com/btseytlin/ultrapack/tree/main/plugins/up/skills/handsoff
Command: npx skills add https://github.com/btseytlin/ultrapack --skill handsoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hands-off mode lets you run the full ultrapack workflow without repeated approvals, while still minimizing risk by choosing the most reversible actions and producing an explicit decision log.

Core Features & Use Cases

  • Fewer prompts after Design: automatically proceeds through planning and execution with fewer user questions once the task design is set.
  • Reversibility-first safety: prioritizes additive edits, dedicated branches/worktrees, and avoids destructive git operations (e.g., no resets, no force-push, no mass deletes without one-at-a-time handling).
  • Transparent outcome reporting: records every auto-choice in the task file’s Conclusion under Hands-off decisions and defers any ambiguous or non-conservative steps into a Deferred log for later user review.
  • Mode-driven behavior: activates only when the task file includes Mode: hands-off, otherwise it follows the interactive workflow.

Quick Start

Set your task file header to Mode: hands-off, then ask the agent to run the workflow end-to-end for your feature using /up:make.

Frequently Asked Questions about handsoff

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

FAQPage Schema
How do I automate end-to-end coding workflows without repeated approval prompts?

Hands-off workflow orchestration minimizes post-design user prompting by automatically proceeding through planning, execution, and verification phases while maintaining explicit reversibility guarantees and decision logging.

What is the safest way to run automated code execution with git branch protection?

Automated workflow execution enforces mandatory safe git practices by using dedicated branches and worktrees, prioritizing additive edits, and avoiding destructive operations like resets, force-pushes, and mass deletes.

How do I track automated decisions made during a hands-off task execution?

Automated task execution records every auto-choice rationale in a Hands-off decisions log within the task file's Conclusion section, deferring ambiguous or non-conservative steps into a Deferred log for later review.

Can I run hands-off task planning without losing interactive control over ambiguous requirements?

Yes, the workflow defers ambiguous required inputs into a Deferred section for later user review, allowing the core execution to proceed automatically while preserving transparent outcome reporting for non-conservative steps.

How do I activate hands-off mode for an automated make and execution workflow?

Set your task file header to Mode: hands-off, then ask the agent to run the workflow end-to-end using the /up:make command to trigger automated design, planning, execution, verification, and review.

What are the limitations of running hands-off automated workflows for complex tasks?

The hands-off mode only activates when the task file explicitly includes Mode: hands-off; otherwise it follows the interactive workflow, and it cannot perform destructive git operations or force-push code changes automatically.