think

Create and validate structured five-section plans for features, architecture, and refactors.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/TLOGBen/baransu --skill think-tlogben
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: think
Source: https://github.com/TLOGBen/baransu/tree/main/plugins/baransu/skills/think
Command: npx skills add https://github.com/TLOGBen/baransu --skill think-tlogben

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps in defining and validating plans before jumping into code, ensuring that all parties are aligned on the intended outcome.

Core Features & Use Cases

  • Plan Definition: Create a structured five-section plan for any new feature, architecture decision, or refactor.
  • Alignment: Engage in a focused dialogue to ensure clarity on purpose, constraints, and success criteria.
  • Evaluation: Provide a single-line verdict on whether something should exist, be kept, or be removed.
  • Use Case: Before implementing a new feature, use this Skill to outline the plan, get feedback, and validate the approach.

Quick Start

Run the 'think' skill to create a plan for a new feature or architecture decision.

Frequently Asked Questions about think

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

FAQPage Schema
How do I define and validate a software development plan before writing code?

To define and validate a software development plan, outline your feature or architecture decision in a structured five-section plan to align intent, constraints, and success criteria before implementation begins.

What is the best way to align stakeholders on a new feature before implementation?

The best way to align stakeholders on a new feature is to use a focused dialogue mechanism that clarifies purpose and validates the approach, ensuring everyone agrees on the intended outcome before code implementation.

Can I evaluate whether an existing architecture decision should be kept or removed?

Yes, you can evaluate whether an architecture decision should be kept or removed by running the evaluation mode, which provides a focused verdict on whether something should exist, be kept, or be removed.

How does plan definition work for software refactoring and new architecture decisions?

Plan definition for refactoring and new architecture decisions works by creating a structured five-section plan that captures intent, constraints, and success criteria to validate the approach before any code is written.

What are the limitations of planning features before implementation?

The planning process focuses strictly on defining and validating plans before building code, meaning it does not execute code implementation itself but rather ensures alignment on purpose and success criteria prior to development.