Tech Design | Agent Skills Atlas

About this skill

Generate a technical design document as a markdown file, given a PRD (or PRD-shaped description). Use this skill whenever the user asks for a tech design, technical design doc, architecture doc, implementation design, engineering design, RFC, or wants to "design the implementation of" / "figure out how we'd build" / "spec out the architecture for" a feature. Trigger on phrases like "write a tech design for the PRD at ...", "design the implementation of X", "how would we architect this", "turn this PRD into a design". This is the step after a PRD — it converts product intent into engineering specifics (components with real file paths, data model, API contracts, existing patterns to reuse). It is not the right fit for product/requirements docs (use prd-generator) or for breaking work into tasks (use task-dag).

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.

Installation guide →

Review, license & listing details

Review the source before using this skill

This is an imported listing. We haven’t certified its safety, license, or compatibility. Skills may include executable scripts.

Automated security scan: Partial

Only SKILL.md was scanned. Supporting files and scripts were not checked. No safety grade has been assigned.

0 potential findings · Scanned 11/4/2026 · Scanner 0.2.1

Content SHA-256: f309d013cd5aeeba900bbce125a6ecc7dcd940b8b887f8ad502df57ff7634804

About scan coverage and limitations

Original listing metadata

Original name

tech-design

Original description

Generate a technical design document as a markdown file, given a PRD (or PRD-shaped description). Use this skill whenever the user asks for a tech design, technical design doc, architecture doc, implementation design, engineering design, RFC, or wants to "design the implementation of" / "figure out how we'd build" / "spec out the architecture for" a feature. Trigger on phrases like "write a tech design for the PRD at …", "design the implementation of X", "how would we architect this", "turn this PRD into a design". This is the step *after* a PRD — it converts product intent into engineering specifics (components with real file paths, data model, API contracts, existing patterns to reuse). It is *not* the right fit for product/requirements docs (use `prd-generator`) or for breaking work into tasks (use `task-dag`).

About this listing

Category: Product & design
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.