One-click install
npx skills add https://github.com/btseytlin/ultrapack --skill uplan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: uplan
Source: https://github.com/btseytlin/ultrapack/tree/main/plugins/up/skills/uplan
Command: npx skills add https://github.com/btseytlin/ultrapack --skill uplan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

uplan converts an already-validated task design into a concrete, engineer-ready implementation plan so the next stage can execute without redoing the thinking.

Core Features & Use Cases

  • Lean implementation planning: Produces the ## Plan section of docs/tasks/<slug>.md with exact file/line targets, interfaces, and phase-by-phase commit scope.
  • Scope discipline: Ensures scope is decided in ## Design and flags cases where planning would require re-opening design or changing scope.
  • Execution-ready contracts: Defines plan entries that up:uexecute will treat as the contract, including invariants/principles/assumptions (IV/PC/AS/UK) referenced by ID and a behavior-focused test strategy.

Quick Start

Ask for a plan right after completing the task’s Design section, e.g. run uplan to populate the ## Plan section for your current docs/tasks/<slug>.md.

Frequently Asked Questions about uplan

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

FAQPage Schema
How do I create an implementation plan from a validated design document?▼

Implementation planning converts an approved design into actionable tasks by defining exact file/line targets, interfaces, and phase-by-phase commit scope. This process populates the plan section of your task file for immediate engineering execution.

What is the best way to structure git workflow phases for feature development?▼

Git workflow phases for feature development are structured by defining plan entries with phase-by-phase commit scope. This ensures each implementation phase maps to specific file locations and interface contracts for controlled, incremental code generation.

Do I need a finalized design before generating an implementation plan?▼

Yes, a finalized design is required before generating an implementation plan. Planning relies on strict scope discipline established during the design phase and will flag any cases where planning would require re-opening the original design decisions.

How do you define test strategy and interface contracts for execution-ready tasks?▼

Interface contracts and test strategy are defined using strict ID adherence for invariants, principles, and assumptions. This behavior-focused approach ensures the output plan acts as a direct, executable contract for subsequent task execution.

Can implementation planning handle scope changes during code generation?▼

Implementation planning enforces strict scope discipline and does not handle scope changes during code generation. It actively flags scenarios where the planning process would require re-opening the design or altering the previously decided scope.