think

Design, validate, and evaluate software architecture and feature proposals.

2|Updated Jul 22, 2026
One-click install
npx skills add https://github.com/0xUrsanomics/utopia-os --skill think-0xursanomics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: think
Source: https://github.com/0xUrsanomics/utopia-os/tree/main/knowledge/waza-skills/think
Command: npx skills add https://github.com/0xUrsanomics/utopia-os --skill think-0xursanomics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents wasted engineering effort by forcing a structured validation and design phase before any code is written, ensuring that proposed solutions are robust, well-reasoned, and approved.

Core Features & Use Cases

  • Design Validation: Transforms rough ideas into concrete, reviewed plans while identifying risks and dependencies.
  • Evaluation Mode: Provides objective value judgments on whether a feature or component should be built, kept, or removed.
  • Lightweight Mode: Offers quick, opinionated fixes for well-defined problems without the overhead of a full design cycle.

Quick Start

Use the think skill to analyze the proposed architecture for the new authentication module and provide a validation report.

Frequently Asked Questions about think

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

FAQPage Schema
How do I validate software architecture before writing code?

Evaluating feature proposals requires an objective validation phase to assess technical feasibility, identify dependencies, and mitigate risks. This structured design process ensures solutions are robust before implementation begins.

When should I use a design validation workflow for software planning?

A design validation workflow is needed when transforming rough ideas into concrete plans. It forces a structured evaluation phase to catch risks and verify dependencies before committing engineering effort.

What is the best way to evaluate if a software component should be built or removed?

The best way to evaluate if a component should be built or removed is using an objective evaluation mode that provides value judgments on feature viability. This assesses technical alignment with project goals during planning.

Can I get quick architectural fixes without a full design cycle?

Yes, you can get quick architectural fixes without a full design cycle by using a lightweight mode. This provides opinionated solutions for well-defined problems without the overhead of rigorous dependency verification.

Does software design validation require explicit approval before implementation?

Software design validation requires explicit user approval before implementation to ensure alignment with project goals. This prerequisite prevents wasted engineering effort by mandating a reviewed and approved planning phase.