---
name: ta-playbook
description: "What a Technical Architect reaches for in RBA Skills to scope technical workstreams, shape architecture in Envision, and govern the build through delivery."
disciplines:
  - engineering
tags:
  - playbook
  - role-guide
  - ta
author:
  name: Kassie Gibbons
  url: https://rba.com
---

# Technical Architect Playbook

TAs own technical direction — defining how things get built, reviewing they're built correctly, and making sure the solution scales, performs, and is maintainable after RBA leaves. You catch the SOW assumptions that will blow up in Create if nobody addresses them in Envision. This is your RBA Skills toolkit.

## Estimating — scope the technical workstreams

| Reach for | Why |
|---|---|
| **estimate-sow-builder** → `build-estimate` / `risk-weight-estimate` | Architecture and backend hours, with risk-weighted ranges. |
| **estimate-sow-builder** → `draft-sow` | Scope the technical workstreams accurately. |

## Envision — set technical direction

| Reach for | Why |
|---|---|
| **envision-toolkit** → `stakeholder-interview-guide` | Technical stakeholder and SME interviews. |
| **architecture-advisor** (`composable-architecture-options`, `platform-selection-scorecard`, `tco-analysis`, `integration-diagram`, `dxp-migration-roadmap`) | Compare options, score platforms, model TCO, and diagram integrations. |
| `write-an-adr` skill | Capture the decisions and their rationale. |

## Create & Deliver — govern the build

| Reach for | Why |
|---|---|
| `user-story-writer` skill | Flag technical stories that are too large or too vague. |
| **code-review-enforcer** → `pr-reviewer` / `standards-check` | Hold the build to standard in review. |
| **integration-scaffolder** → `integration-api-spec` / `integration-error-resilience` | Set the integration contract and resilience patterns. |
| **release-notes-generator** → `release-notes-developer` | Document what changed and how to deploy it. |
| **estimate-sow-builder** → `change-order-builder` | When technical complexity changes the scope. |

## TA Tips

- **Scope integration boundaries explicitly in the SOW.** Name the endpoints and which side RBA owns — not just "Salesforce integration."
- **Flag integration risks early in the RAID log.** Until API docs are confirmed, that's a real risk on every backend estimate.
- **Release notes are your accountability record.** Write them like someone will use them to troubleshoot at 2am — because they will.
- **Also explore:** **cloud-devops-accelerator** (landing zones, IaC, security baseline) and **security-readiness-reviewer** for production-readiness gates.