think
Turns rough ideas into approved, decision-complete plans with validated structure before coding. Use when users ask in any language for planning, architecture, design direction, feasibility, value judgment, or whether a feature is worth doing before implementation. Not for bug fixes or small edits.
Profile →npx skills add tw93/Waza --skill think --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Think: Design and Validate Before You Build Prefix your first line with 🥷 inline, not as its own paragraph. Turn a rough idea into an approved plan. No code, no scaffolding, no pseudo-code until the user approves. Give opinions directly. Take a position and state what evidence would change it. Avoid "That's interesting," "There are many ways to think about this," "You might want to consider." ## Outcome Contract - Outcome: a rough idea becomes a decision-complete recommendation or implementation plan. - Done when: the goal, success criteria, constraints, chosen approach, rejected tradeoffs, tests, and handoff steps are concrete enough to execute without re-deciding. - Evidence: current repo state, project docs, live external docs when relevant, prior decisions, constraints, and explicit user preferences. - Output: one recommended direction or a handoff plan with assumptions and verification steps. ## Durable Context Preflight See [references/durable-context.md](references/durable-context.md) for when durable context is in scope and the redaction gate that applies before any of it becomes a durable rule. For `/think`: current repo state and live docs override memory. Lock durable
- Outcome Contract
- Durable Context Preflight
- Lightweight Mode
- Evaluation Mode
- Triage Mode
- Before Reading Any Code
- Check for Official Solutions First
- Propose Approaches
- Validate Before Handing Off
- Implementation Handoff
- Hard Rules
- Gotchas
- Output
- After Approval
What does the think skill do?
Turns rough ideas into approved, decision-complete plans with validated structure before coding. Use when users ask in any language for planning, architecture, design direction, feasibility, value judgment, or whether a feature is worth doing before implementation. Not for bug fixes or small edits.
How do I install it?
Run `npx skills add tw93/Waza --skill think --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From tw93/Waza, a repository with 6,760 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.