design

Turn an idea into an approved design before implementation work starts.

89|7|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/nikhilsitaram/claude-caliper --skill design-nikhilsitaram
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/nikhilsitaram/claude-caliper/tree/main/skills/design
Command: npx skills add https://github.com/nikhilsitaram/claude-caliper --skill design-nikhilsitaram

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents wasted implementation work by forcing a clear, validated design before any code is written. It helps turn vague ideas into aligned decisions so teams can avoid rework, hidden assumptions, and scope creep.

Core Features & Use Cases

  • Problem framing: Clarifies what is broken or missing, who is affected, and why the change matters now.
  • Option comparison: Proposes a few viable approaches, weighs trade-offs, and recommends one path forward.
  • Design validation: Produces success criteria, architecture, test strategy, non-goals, and an implementation approach that can be reviewed before execution.
  • Use cases: Feature planning, behavior changes, component additions, configuration updates, and other software changes that need approval before building.

Quick Start

Use the design skill to help me define the problem, compare approaches, and draft an approved design for my feature before any implementation begins.

Frequently Asked Questions about design

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

FAQPage Schema
How do I create a validated software architecture plan before starting implementation?

To create a validated architecture plan, frame the problem, challenge assumptions, compare viable approaches, and define explicit success criteria, test strategy, and non-goals before writing any code.

What is the best way to prevent scope creep during feature planning?

Preventing scope creep during feature planning requires drafting an approved design that explicitly defines non-goals, clarifies assumptions, and establishes a reviewed implementation approach before execution begins.

How do I compare implementation approaches for a new software component?

Comparing implementation approaches involves proposing multiple viable paths, weighing their trade-offs, and recommending one option forward based on defined success criteria and scope estimation.

Can I use a structured design process for behavior changes and configuration updates?

Yes, a structured design process applies to behavior changes, configuration updates, component additions, and functionality modifications by forcing clear problem framing and validation before execution.

What should be included in a software design review to get approval?

A software design review for approval should include problem framing, option comparison, architecture, test strategy, non-goals, implementation approach, and scope estimation to ensure full alignment.

Why does my software project suffer from rework and hidden assumptions?

Software projects suffer from rework and hidden assumptions when teams skip design validation and start implementation without turning vague ideas into aligned decisions and explicit success criteria.