tech-design

Generate implementation-ready backend technical designs from PRDs or feature descriptions.

88|15|Updated May 25, 2026
One-click install
npx skills add https://github.com/open-octo/octo-agent --skill tech-design-open-octo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-design
Source: https://github.com/open-octo/octo-agent/tree/main/internal/skills/defaults/tech-design
Command: npx skills add https://github.com/open-octo/octo-agent --skill tech-design-open-octo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns incomplete product requirements or feature descriptions into accurate, context-free backend technical designs, reducing ambiguity, preventing invented interfaces and schemas, and closing unresolved implementation decisions before handoff.

Core Features & Use Cases

  • Structured Design Workflow: Guides the process through understanding requirements, exploring the codebase, resolving decisions, writing the design, and performing a rigorous self-review.
  • Traceable Technical Detail: Requires concrete APIs, fields, database columns, topics, cache keys, dependencies, and operational parameters to be verified against source code, documentation, or explicit user decisions.
  • Production Readiness: Covers architecture, data models, interfaces, testing, compatibility, security, availability, monitoring, rollout, rollback, and external dependencies. Use it when creating a backend technical proposal from a PRD or when documenting a multi-service feature for implementation.

Quick Start

Use the tech-design skill to explore the repository and produce an implementation-ready backend design for the feature description I provide.

Frequently Asked Questions about tech-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a PRD into a backend technical design?

A complete backend technical design from a PRD requires codebase exploration to verify traceable technical facts like APIs, database columns, and cache keys. It explicitly resolves implementation decisions and analyzes compatibility, security, and operational safeguards to prevent invented schemas.

What should a backend architecture proposal include for multi-service features?

A backend architecture proposal for multi-service features must cover data-model changes, message queues, configuration, APIs, and caches. It requires comprehensive self-review, compatibility analysis, availability monitoring, and explicit rollout and rollback strategies.

How to prevent invented interfaces and schemas when writing technical designs?

To prevent invented interfaces and schemas during technical design, require concrete APIs, fields, database columns, topics, and cache keys to be verified against source code or documentation. Explicit user decisions must resolve any technical ambiguities before handoff.

Can I use codebase exploration to resolve unresolved implementation decisions before handoff?

Yes, codebase exploration resolves unresolved implementation decisions before handoff by validating dependencies and interfaces against source code. This structured process reduces ambiguity and ensures the backend architecture is implementation-ready.

Does a production-ready technical design need rollback and security analysis?

Yes, a production-ready technical design requires security analysis, availability monitoring, and explicit rollback strategies. It must document operational safeguards and external dependencies to ensure safe multi-service architecture rollouts.