think
The think skill transforms rough ideas into decision-complete implementation plans. It enforces a design-first workflow, requiring validation of goals, constraints, and tradeoffs before any code is written. It includes specialized modes for lightweight fixes, value judgments, and triage of multiple requests.
Is think safe to install?
Review the source first: our audit of think's source files found 3 shell commands, 0 external URLs, file reads and writes (high risk). Every command and URL listed appears verbatim in the skill's source. The skill executes shell commands and reads project files to validate context and state. It requires careful handling of project-specific configurations and environment variables.
How we audit skills: our security review methodology.
Who is this skill for?
Developers and project maintainers who need to validate architectural decisions, feasibility, or product direction before implementation.
What can you do with it?
- Planning new features or architectural changes
- Evaluating whether a feature or product is worth building or keeping
- Triage of multiple user requests or bug reports
- Determining the best technical approach for a problem
- Performing value judgments on product pivots or commercialization
How good is this skill?
Quality score: 5/10. The skill provides a comprehensive, structured framework for decision-making and planning. It includes clear operational modes and strict rules to prevent common agentic pitfalls like premature coding or ignoring project constraints.
What does the skill file contain?
# Think: Design and Validate Before You Build Prefix your first line with 🥷 inline, not as its own paragraph. **Update check (non-blocking).** Once per conversation, run `bash <skill-base-dir>/scripts/check-update.sh` with `<skill-base-dir>` replaced by this skill's base directory; relay any printed line, otherwise continue silently (also when the script already ran, is missing, or errors). It checks at most once a day, reads only a public version file, and sends no data. Turn a rough idea into an approved plan. No code, no scaffolding, no pseudo-code until the user approves. Give opinion...
Frequently asked questions
When should I use this skill instead of just writing code?
Use this skill when you need to plan architecture, design a feature, judge the value of a project, or triage multiple tasks. It prevents premature implementation by requiring a validated plan first.
Does this skill write code?
No. The skill produces an implementation plan. It explicitly forbids writing code, scaffolding, or pseudo-code until the user approves the plan.
How does it handle existing project rules?
The skill scans AGENTS.md, CLAUDE.md, and .claude/rules/*.md before outputting any plan. If a plan contradicts a hard rule, it surfaces the contradiction and stops for resolution.
Related skills
frontend-design
618.4KAI agents tasked with designing and building web interfaces who need to produce unique, high-quality visual identities rather than generic, templated designs
The frontend-design skill provides guidance for creating distinctive, intentional visual designs for web interfaces. It instructs the agent to act as a design lead at a small studio, focusing on avoiding templated defaults by making deliberate choices regarding typography, color palettes, layout, and motion. The skill emphasizes a structured process of brainstorming, planning, and self-critique before writing code.
brainstorming
256.4KDevelopers and project managers who need to define requirements, architecture, and design for software projects before writing code
A structured brainstorming framework that guides users through project exploration, design proposal, and specification before implementation. It enforces a strict design-first workflow, requiring user approval for designs and documentation before transitioning to the writing-plans skill.
simple
221.4KDevelopers and project managers who need a fast, lightweight decision-making process for feature design or component creation
A structured brainstorming framework for architectural and creative tasks that guides users from discovery to decision-making through a defined process flow.
writing-plans
174.7KSoftware engineers and AI agents tasked with implementing complex features from specifications
The writing-plans skill generates structured, task-based implementation plans for software development projects. It enforces a specific markdown format that includes architecture, tech stack, global constraints, and granular, test-driven development steps for each task.