Use when setting or revising the technical direction of an engineering organization — writing the technical strategy document, picking the load-bearing technical bets, deciding build vs buy vs adopt, deciding when to invest in shared platforms, declaring which DADs are core to the strategy, communicating direction to engineering and leadership, or pushing back on proposals that don't fit. Triggers on mentions of "technical strategy", "tech strategy", "technical vision", "platform investment", "build vs buy", "tech bet", "north star architecture", "technical principles", "technology choice", "technology stack decision", "platform-vs-product", or "load-bearing DAD". For macro system design (services, fault tolerance, capacity) see system-architect; for enforcement of the strategy at gates see standards-enforcer; for capturing decisions as ADRs/DADs see team-lead.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryEngineeringStars0
About this skill
Use when setting or revising the technical direction of an engineering organization — writing the technical strategy document, picking the load-bearing technical bets, deciding build vs buy vs adopt, deciding when to invest in shared platforms, declaring which DADs are core to the strategy, communicating direction to engineering and leadership, or pushing back on proposals that don't fit. Triggers on mentions of "technical strategy", "tech strategy", "technical vision", "platform investment", "build vs buy", "tech bet", "north star architecture", "technical principles", "technology choice", "technology stack decision", "platform-vs-product", or "load-bearing DAD". For macro system design (services, fault tolerance, capacity) see system-architect; for enforcement of the strategy at gates see standards-enforcer; for capturing decisions as ADRs/DADs see team-lead.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
Use when setting or revising the technical direction of an engineering organization — writing the technical strategy document, picking the load-bearing technical bets, deciding build vs buy vs adopt, deciding when to invest in shared platforms, declaring which DADs are core to the strategy, communicating direction to engineering and leadership, or pushing back on proposals that don't fit. Triggers on mentions of "technical strategy", "tech strategy", "technical vision", "platform investment", "build vs buy", "tech bet", "north star architecture", "technical principles", "technology choice", "technology stack decision", "platform-vs-product", or "load-bearing DAD". For *macro system design* (services, fault tolerance, capacity) see system-architect; for *enforcement of the strategy at gates* see standards-enforcer; for *capturing decisions as ADRs/DADs* see team-lead.
About this listing
Category
Engineering
Reported license
Not specified
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLI