---
name: nanlabs-trd
description: >-
  WHAT, Draft and review a Technical Requirements Document (TRD) from the NaNLABS ClickUp template, typically after an agreed PRD. Covers architecture, data contracts, technical decisions, risks, and test strategy. English artifacts unless the user asks otherwise.
---

# TRD, Technical Requirements (WHAT)

**Canonical source:** the TRD template in ClickUp. Ask internally for the current link; use the local template below as the distributable source.

## Default guardrails (before any final content)

1. Apply **`nanlabs-output-handshake`**: confirm **where** the final TRD will live and that a **human** will review.
2. Then follow the steps below.

## When to use

- A **PRD is approved** (or the task is technical-only) and the team needs design-level agreement before build.
- You need **API/data contracts**, component boundaries, and **test strategy** aligned to NaNLABS standards.
- A client doc hub (e.g. **Operations** with PRD/TRD cross-links) requires **matching** document structure.

## Instructions

1. **Open the canonical TRD page** in ClickUp. Align sections: Scope, Architecture overview, Data model / API contracts, Technical decisions (link **ADRs** and spikes), Dependencies, Risks & constraints, Testing strategy, Implementation plan.
2. **Map from PRD:** user stories and AC from the PRD should appear as **addressed** in the TRD with clear technical response; if no PRD exists, state that explicitly and list assumptions.
3. For **ADRs** that block or explain design, use **`nanlabs-adr`** to structure the decision, then **link** the task or ADR in ClickUp/GitHub per your engagement.
4. Delegate **repo facts** to **`nanlabs-assistant`** (conventions, CI, existing patterns); cite sources.
5. For **ClickUp** updates, use **`clickup-cli`**; keep task comments **short** with links to the Doc (per `nanlabs-workflow-generic-project`).

## What not to do

- Do not dump the full template from ClickUp into the skill (drift risk).
- Do not skip **risks** and **testing** when the TRD is a handoff artifact.

## References

- `nanlabs-output-handshake`, destination and review
- `references/default-template.md`, local TRD template structure
- `references/example-api-migration.md`, TRD example for an API migration with phases and testing strategy
- `nanlabs-prd`, when work starts from product requirements
- `nanlabs-spike`, research findings used as design evidence
- `nanlabs-adr`, decision records linked from the TRD
- `nanlabs-development-workflow`, validation and traceability expectations
- `nanlabs-incident`, failure handling / incident implications when relevant
- `nanlabs-workflow-generic-project`, delivery gates and traceability
- `clickup-cli`, task / comment operations