udesign

Convert software ideas into validated design specifications with TDD decisions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

udesign prevents wasted effort by turning vague feature ideas into an explicit, reviewable design with tradeoffs, risks, and TDD guidance before any building starts.

Core Features & Use Cases

  • Validated spec drafting: produces the ## Design section for docs/tasks/<slug>.md with clear invariants, principles, assumptions, unknowns, and a TDD decision.
  • Scope control: checks whether the request is too large and prompts splitting into multiple tasks when needed.
  • Backwards-compat risk review: forces loud enumeration of breaking risks (or confirms greenfield) before planning proceeds.

Quick Start

Invoke udesign to design a change before writing any code by asking the agent to plan the feature and record the resulting design in the task file.

Frequently Asked Questions about udesign

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

FAQPage Schema
How do I create validated software design specifications before writing code?

Test-driven development decisions are determined by evaluating the validated design specification, which explicitly outputs a TDD yes/no decision alongside invariants, principles, and unknowns to guide the testing approach.

How do I assess backwards compatibility risks when planning software changes?

Large feature scopes are controlled by checking whether the request is too large and prompting the split into multiple resumable task files, ensuring the design specification remains manageable and focused.

How do I write a task file design section for feature development?

Specification drafting applies to feature development, component changes, and architecture moves, converting new software ideas into validated design specifications that are ready for planning and execution.

Do I need a git-centered workflow to plan component changes?

A git-centered workflow supports planning component changes by recording the resulting validated design in a task file, ensuring the specification is reviewable and integrated before execution begins.