skills.rest
charly-vibes
charly-vibesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

design-practice

Apply a 6-phase design framework to analyze and solve problems.

1|Updated Jan 31, 2026
Search Tags:#design thinking#implementation planning#problem solving#software development#root cause analysis#framework
One-click install
npx skills add https://github.com/charly-vibes/wai --skill design-practice
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-practice
Source: https://github.com/charly-vibes/wai/tree/main/.agents/skills/design-practice
Command: npx skills add https://github.com/charly-vibes/wai --skill design-practice

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you thoroughly understand a problem by guiding you through a structured 6-phase design framework, ensuring a clear path from symptoms to a well-defined solution before implementation.

Core Features & Use Cases

  • Structured Problem Analysis: Systematically moves through Describe, Diagnose, Delimit, Direction, Design, and Develop phases.
  • Hypothesis Testing: Encourages generating and testing multiple hypotheses for root cause analysis.
  • Scope Definition: Clearly outlines what is in and out of scope to prevent creep.
  • Decision Matrix: Facilitates objective selection of the best strategic approach.
  • Use Case: When faced with a complex bug, use this Skill to meticulously document symptoms, identify the root cause, define the exact scope of the fix, choose the best implementation strategy, and create a detailed plan before writing any code.

Quick Start

Begin the design practice skill by describing the observed symptoms of the problem.

Frequently Asked Questions about design-practice

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

FAQPage Schema
How do I use a structured framework for root cause analysis before coding?▼

A structured problem-solving framework guides you through six phases—Describe, Diagnose, Delimit, Direction, Design, and Develop—to systematically identify root causes and define solutions before implementation.

What is the best way to define scope and prevent creep during software development?▼

Defining scope involves systematically delimiting boundaries during the problem-solving process, clearly outlining what is in and out of scope to prevent creep before tactical planning begins.

How do I select the best implementation strategy for a complex bug?▼

Selecting an implementation strategy uses a decision matrix to objectively evaluate approaches during the Direction phase, ensuring the best strategic path is chosen before detailed tactical planning.

When do I need hypothesis testing for problem solving in software development?▼

Hypothesis testing for problem solving is needed during the Diagnose phase of framework execution, encouraging the generation and testing of multiple hypotheses to accurately pinpoint root causes.

Can I apply this design thinking framework to routine coding tasks?▼

This design thinking framework is intended for complex problems requiring rigorous analysis, such as intricate bugs, rather than routine coding tasks that do not need systematic scope definition or decision matrices.

Related Skills

Explore More Software Engineering Skills→
ilandahanilandahan
9

aid-discovery

Validate problem space and stakeholder readiness before PRD initiation.

Community
Basic
Sungmin-ChoSungmin-Cho
10

deep-brainstorm

Generate a brainstorm plan document covering problem definition, approaches, and risks.

Community
Intermediate
DojoGenesisDojoGenesis
2

strategic-to-tactical-workflow

Generate development artifacts from a strategic question through an eight-phase workflow.

Community
Advanced
jchildreejchildree
1

systematic-debugging

Run systematic debugging sessions for complex technical issue resolution via /investigate command.

Community
Advanced