think

Transform rough ideas into structured plans with goals, constraints, and tradeoffs.

6.8k|402|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/tw93/Waza --skill think-tw93
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: think
Source: https://github.com/tw93/Waza/tree/main/plugins/waza/skills/think
Command: npx skills add https://github.com/tw93/Waza --skill think-tw93

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turns rough ideas into approved, decision-complete plans with validated structure before coding.

Core Features & Use Cases

  • Generate structured plans that include goals, constraints, decision criteria, and actionable next steps.
  • Provide evaluation of tradeoffs and recommended options for architectural and feature decisions.
  • Deliver a clear handoff artifact to engineers, product managers, and stakeholders, reducing rework and alignment risk.

Quick Start

Give me a rough idea and I will turn it into a decision-ready plan with concrete steps.

Frequently Asked Questions about think

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

FAQPage Schema
How do I turn a rough product idea into a decision-ready plan for stakeholders?

A decision-ready plan requires durable context and explicit decision criteria to transform rough ideas into structured outputs. It details goals, constraints, tradeoffs, tests, and handoff steps, ensuring alignment among engineers and stakeholders before implementation begins.

What is the best way to structure architecture reviews for feature ideation?

Structuring architecture reviews involves evaluating tradeoffs and providing recommended options based on clear decision criteria. This ensures feature ideation results in a concrete plan with validated architecture, actionable next steps, and a clear handoff artifact for engineering teams.

How do I create a handoff artifact that reduces rework for engineers?

Creating a handoff artifact requires detailing goals, constraints, tradeoffs, and tests within a structured plan. By providing explicit decision criteria and next steps, the artifact aligns product managers and engineers, minimizing rework and alignment risk during implementation.

Can I use this planning approach for strategic planning and not just feature decisions?

Yes, this planning approach applies to strategic planning, architecture reviews, and feature ideation. As long as durable context and explicit decision criteria are provided, it outputs a structured plan with goals, constraints, tradeoffs, and handoff steps for any strategic decision.

What do I need to provide to generate a plan with tradeoffs and recommended options?

You need to provide a rough idea and durable context. Explicit decision criteria are required to evaluate tradeoffs and generate recommended options, resulting in a structured plan that includes actionable next steps and a clear handoff for stakeholders.