One-click install
npx skills add https://github.com/einargudnig/dotfiles --skill think-einargudnig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: think
Source: https://github.com/einargudnig/dotfiles/tree/main/claude/skills/think
Command: npx skills add https://github.com/einargudnig/dotfiles --skill think-einargudnig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms vague product or architecture ideas into a validated, non-code plan so teams avoid premature implementation mistakes and misaligned engineering work.

Core Features & Use Cases

  • Structured Decisioning: Provides 2–3 distinct approaches with concise tradeoffs and a recommended path including a minimal option.
  • Rigorous Validation: Runs four attack-angle checks (dependency failure, scale, rollback cost, premise collapse) and adapts the plan if any check fails.
  • Clear Handoff Criteria: Lists key decisions, unknowns with owners, required credentials and services, and explicit acceptance criteria before implementation.
  • Use Case: Ideal for designing a new feature, choosing an architecture, or planning a cross-team component where approval and rollback strategy are essential.

Quick Start

🥷 Help me design and validate a plan for adding a multi-tenant billing feature, showing 2-3 options, tradeoffs, attack-angle checks, and a recommended approach with rollback steps.

Frequently Asked Questions about think

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

FAQPage Schema
How do I turn rough architecture ideas into an approved technical proposal before coding?

Turn rough ideas into approved technical proposals by generating 2–3 actionable approaches, comparing tradeoffs, running rigorous validation checks, and establishing a final approval checkpoint before implementation begins.

What is the best way to validate rollback strategies and premise collapse for a new feature design?

Validate rollback strategies and premise collapse for new feature designs by applying attack-angle validation checks that test dependency failures, scale limits, rollback costs, and premise collapse to adapt the plan proactively.

How do I compare multiple implementation options with tradeoffs for system design planning?

Compare multiple implementation options for system design planning by evaluating 2–3 distinct approaches with concise tradeoffs, selecting a recommended path that includes a minimal viable option to ensure flexibility.

Can I use this planning process for cross-team architecture decisions that require clear handoff criteria?

You can use this planning process for cross-team architecture decisions because it lists key decisions, concrete unknowns with designated owners, required services, and explicit acceptance criteria for a frictionless handoff.

When do I need to run attack-angle validation checks during technical proposal planning?

Run attack-angle validation checks during technical proposal planning when multiple implementation options exist and risks like dependency failure, scale limitations, rollback cost, and premise collapse must be compared before coding starts.

Why avoid premature implementation mistakes when designing a multi-tenant billing feature?

Avoid premature implementation mistakes when designing a multi-tenant billing feature by generating a validated, non-code design plan that aligns engineering work through structured decisioning and explicit acceptance criteria.