strategic-mindset

Assess code for tactical patterns and technical debt with the 10-20% investment rule.

11|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/codybrom/clairvoyance --skill strategic-mindset
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: strategic-mindset
Source: https://github.com/codybrom/clairvoyance/tree/main/skills/strategic-mindset
Command: npx skills add https://github.com/codybrom/clairvoyance --skill strategic-mindset

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies when working code prioritizes immediate functionality over durable software design, helping reveal shortcuts, technical debt, and tactical programming patterns before they become systemic problems.

Core Features & Use Cases

  • Strategic versus Tactical Assessment: Evaluate whether implementation choices improve the overall design or merely satisfy the current requirement.
  • Investment and Debt Analysis: Apply the 10-20% design investment rule, identify tactical tornado patterns, and estimate the effort needed for strategic improvement.
  • Forward-Looking Review: Project the consequences of repeating current shortcuts across future changes and recommend specific investments.
  • Use Case: Review a rushed feature or module to determine whether copy-paste fixes, missing abstractions, and undocumented dependencies are degrading the codebase.

Quick Start

Ask the strategic-mindset skill to assess the specified file, module, or codebase area for tactical programming patterns and recommend targeted design improvements.

Frequently Asked Questions about strategic-mindset

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

FAQPage Schema
How do I identify tactical programming patterns during a code review?

To identify tactical programming during a code review, assess whether implementation choices prioritize immediate functionality over durable software design. Look for shortcuts like copy-paste fixes, missing abstractions, and undocumented dependencies that degrade the codebase.

What is the 10-20% design investment rule for managing technical debt?

The 10-20% design investment rule estimates the specific effort needed for strategic improvement of rushed implementations. It projects the future consequences of repeating current shortcuts and recommends targeted investments to prevent technical debt.

How do I evaluate if my software design choices are strategic or tactical?

Evaluate software design choices by determining if they improve the overall system design or merely satisfy the current requirement. Strategic programming adds lasting design quality, while tactical programming signals a tactical tornado pattern that degrades the codebase.

Can I assess technical debt in a rushed feature without dedicated testing tools?

Yes, you can assess technical debt in a rushed feature by analyzing the specified module for tactical shortcuts. The evaluation identifies missing abstractions and undocumented dependencies, projecting future consequences and remediation effort directly from the code.

What are tactical tornado signals and how do they impact a codebase?

Tactical tornado signals are repeated shortcuts in code that prioritize immediate functionality over lasting software design quality. They impact a codebase by creating systemic problems, increasing technical debt, and making future changes significantly harder to implement.