technical-strategist

Draft technical strategy documents with diagnosis, policy, actions, and kill criteria.

15|3|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/LazyIsEfficient/agentic-os --skill technical-strategist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: technical-strategist
Source: https://github.com/LazyIsEfficient/agentic-os/tree/main/.claude/skills/technical-strategist
Command: npx skills add https://github.com/LazyIsEfficient/agentic-os --skill technical-strategist

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The Technical Strategist enables engineering teams to align architecture, platforms, and governance with product goals by codifying a clear, repeatable approach to decision-making and trade-offs.

Core Features & Use Cases

  • Draft and socialize a concise technical strategy that guides build/buy/adopt decisions and platform investments.
  • Identify and manage load-bearing DADs/ADR workflows to constrain scope and preserve system integrity.
  • Size, track, and evolve strategic bets with explicit kill criteria, capacity allocation, and governance touchpoints.
  • Align with product strategy and engineering leadership to ensure technical direction enables business outcomes.

Quick Start

Draft a one-page strategy that maps diagnosis to guiding policy and a set of actions, then socialize it with the engineering leadership.

Frequently Asked Questions about technical-strategist

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

FAQPage Schema
How do I draft a technical strategy that aligns engineering architecture with product goals?

Draft a technical strategy by creating a structured document containing a diagnosis, guiding policy, coherent actions, non-goals, and capacity allocation to align architecture constraints with product goals. You then socialize this document with engineering leadership.

What should be included in a technical strategy document for platform governance?

A technical strategy document must include a diagnosis, guiding policy, coherent actions, non-goals, kill criteria, and capacity allocation. This structure ensures engineering direction addresses system constraints while explicitly mapping to business outcomes.

How do I enforce build versus buy decisions across multiple engineering teams?

Enforce build versus buy decisions by establishing a governance workflow with engineering leadership that socializes the technical strategy. This workflow constrains scope and manages load-bearing DADs and ADRs to preserve system integrity across teams.

How do I size and track strategic technical bets with explicit kill criteria?

Track and evolve strategic bets by sizing platform investments with explicit kill criteria and capacity allocation. You govern these bets through defined touchpoints that monitor progress and ensure technical direction continues enabling business outcomes.

When do I need to use DADs and ADRs to constrain engineering scope?

Use DADs and ADRs to constrain scope when managing load-bearing architectural decisions that impact platform integrity. They provide a structured governance workflow to evaluate build, buy, or adopt decisions and preserve system stability across teams.