This source did not publish a separate summary. Review SKILL.md before using the skill.
SKILL.md
Tech Radar
Produce a complete technology radar document for an engineering team. The radar gives the team a shared, explicit position on every significant technology in their stack — what to standardize on, what to experiment with, what to evaluate, and what to actively stop using. Follow the ThoughtWorks Tech Radar format: four quadrants (Techniques, Tools, Platforms, Languages & Frameworks) each with four rings (Adopt, Trial, Assess, Hold). Each technology entry ("blip") gets a ring assignment, a one-paragraph rationale, and a date. Include a decision trail showing what moved and why, and a maintenance process the team can run to keep the radar current.
Required Inputs
Ask for these if not already provided:
Team or company name — for the document header
Current tech stack — list every significant technology, tool, language, and platform the team currently uses
Technologies under active evaluation — tools or frameworks the team is currently trying or considering
Technologies to deprecate or move off — anything the team wants to stop using or is actively migrating away from
Strategic technology bets — any technologies the company has made a deliberate bet on (e.g., "we're all-in on Kubernetes" or "migrating to event-driven architecture")
Team context — team size, product domain, and any constraints (regulatory, compliance, vendor lock-in concerns)
If a technology is mentioned without a ring placement, use the rationale inputs to determine the appropriate ring. When uncertain between two rings, ask.
Output Format
Technology Radar: [Team / Company Name]
Edition: [Month Year]
Maintained by: [Team Name / Architecture Guild / CTO Office]
Review cadence: Bi-annual (every 6 months)
Next review: [Month Year + 6 months]
How to Read This Radar
This radar reflects [Team / Company Name]'s current thinking on technologies we use, evaluate, and retire. Use it to make consistent technology choices, onboard new engineers, and have structured conversations about the stack.
Quadrants categorize the type of technology:
Quadrant
What belongs here
Techniques
Methods, patterns, and practices (e.g., trunk-based development, event sourcing)
Tools
Software tools used in the development and delivery process (e.g., linters, CI systems, observability platforms)
Platforms
Infrastructure and hosting environments (e.g., AWS, Kubernetes, Snowflake)
Languages & Frameworks
Programming languages and application frameworks (e.g., Go, React, FastAPI)
Rings express our recommendation:
Ring
Meaning
What to do
Adopt
Industry-proven, working well for us — our standard choice
Use by default for new work; no special justification needed
Trial
Worth pursuing — we are experimenting with it in limited production use
Use in a bounded context with architectural oversight; share learnings
Assess
Worth exploring — we have not used it in production yet
Spike, prototype, or research; do not use in production without a review
Hold
Do not start new work with this technology
Complete existing commitments; do not expand use; plan migration
Quadrant 1: Techniques
Adopt
Technology
Since
Notes
[Technique name, e.g., Trunk-based development]
[Month Year]
[One sentence: why we adopted it and what it replaced]
[Technique name]
[Month Year]
[One sentence rationale]
[Technique name]
[Month Year]
[One sentence rationale]
[Technique name] — Adopt
[One paragraph rationale. Explain what problem this technique solves, why it works well in your context, and what the team should know before applying it. Reference any internal experience — e.g., "We rolled this out across 8 services in 2024 and saw a 40% reduction in merge conflicts."]
[Repeat for each Adopt-ring technique.]
Trial
Technology
Since
Notes
[Technique name]
[Month Year]
[One sentence: what we're testing and where]
[Technique name] — Trial
[One paragraph. What are we trialing? In which teams or services? What hypothesis are we testing? What would cause us to move it to Adopt vs. Hold?]
Assess
Technology
Since
Notes
[Technique name]
[Month Year]
[One sentence: why we're interested]
[Technique name] — Assess
[One paragraph. Why is this interesting to us? What would we need to see to move it to Trial? Who is responsible for the assessment?]
Hold
Technology
Since
Notes
[Technique name]
[Month Year]
[One sentence: why we're stopping and what replaces it]
[Technique name] — Hold
[One paragraph. Why are we putting this on hold? What is the migration path? What is the target end-state for teams still using it?]
Quadrant 2: Tools
Adopt
Technology
Since
Notes
[Tool name, e.g., GitHub Actions]
[Month Year]
[One sentence rationale]
[Tool name]
[Month Year]
[One sentence rationale]
[Tool name] — Adopt
[One paragraph rationale. Why is this our standard tool? What does it do well in our context? Any configuration or usage patterns the team should follow?]
[Repeat for each Adopt-ring tool.]
Trial
Technology
Since
Notes
[Tool name]
[Month Year]
[One sentence: what we're testing]
[Tool name] — Trial
[One paragraph rationale and trial scope.]
Assess
Technology
Since
Notes
[Tool name]
[Month Year]
[One sentence: why we're evaluating it]
[Tool name] — Assess
[One paragraph: what sparked interest, who is evaluating, and timeline.]
Hold
Technology
Since
Notes
[Tool name]
[Month Year]
[One sentence: what replaces it]
[Tool name] — Hold
[One paragraph: deprecation rationale and migration path.]
Quadrant 3: Platforms
Adopt
Technology
Since
Notes
[Platform name, e.g., AWS EKS]
[Month Year]
[One sentence rationale]
[Platform name]
[Month Year]
[One sentence rationale]
[Platform name] — Adopt
[One paragraph. What does this platform provide? What are the boundaries of its use? Any internal golden-path setup the team should follow?]
[Repeat for each Adopt-ring platform.]
Trial
Technology
Since
Notes
[Platform name]
[Month Year]
[One sentence: scope of trial]
[Platform name] — Trial
[One paragraph rationale and trial boundaries.]
[Platform name] — Hold
[One paragraph: what triggered the hold decision, migration target, and timeline.]
Quadrant 4: Languages & Frameworks
Adopt
Technology
Since
Notes
[Language/Framework, e.g., Go]
[Month Year]
[One sentence rationale]
[Language/Framework]
[Month Year]
[One sentence rationale]
[Language/Framework] — Adopt
[One paragraph. What is this language or framework used for? What are the team's proficiency expectations? Any frameworks or libraries that go alongside it as part of the standard choice?]
[Repeat for each Adopt-ring language or framework.]
