think

Explore design approaches and generate SOW and Specification documents.

11|1|Updated Aug 6, 2025
One-click install
npx skills add https://github.com/thkt/dotclaude --skill think-thkt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: think
Source: https://github.com/thkt/dotclaude/tree/main/.ja/skills/think
Command: npx skills add https://github.com/thkt/dotclaude --skill think-thkt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill assists in deep design exploration, approach comparison, and the generation of Statement of Work (SOW) and Specification documents for complex tasks.

Core Features & Use Cases

  • Design Exploration: Compares multiple approaches with trade-offs and validates assumptions.
  • SOW & Spec Generation: Creates detailed SOW and Spec documents based on approved designs.
  • Task Decomposition: Breaks down complex features into manageable tasks with milestones.
  • Use Case: When faced with a new feature requiring significant architectural decisions, use /think to explore different implementation strategies, document the chosen design, and generate the necessary SOW and Spec for development.

Quick Start

Use the think skill to explore design options for implementing a new user authentication system.

Frequently Asked Questions about think

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

FAQPage Schema
How do I generate a Statement of Work and specification for a complex software feature?

To generate a Statement of Work (SOW) and specification, you must explore design approaches, validate assumptions, and decompose tasks into milestones. This process produces detailed SOW and Spec documents based on the approved architectural design.

What is the best way to compare architectural approaches and validate assumptions for a new feature?

Comparing architectural approaches involves exploring the code base, identifying trade-offs between multiple strategies, and applying self-challenge techniques. User review then validates these assumptions to arrive at an optimal design.

Can I use task decomposition to break down complex software features into manageable milestones?

Yes, task decomposition breaks down complex features into manageable tasks with defined milestones. It also identifies scope cut candidates to ensure the feature remains achievable within the architectural design.

When do I need design exploration before starting development on a new user authentication system?

Design exploration is needed when a new feature requires significant architectural decisions, such as implementing a user authentication system. It helps document the chosen design and generate the necessary SOW and Spec before development.

Does this design exploration approach support identifying scope cut candidates for complex tasks?

Yes, the design exploration approach supports identifying scope cut candidates for complex tasks. It utilizes task decomposition into milestones and user review to determine which features can be deferred without impacting the core architecture.