technical-specification

Creates concise technical specification documents through 3-4 phase process. Guides through architectural decisions, system contracts, and technical design without getting bogged down in implementation details. Use when user wants to create a technical specification, needs to define how the system will be implemented technically, or is documenting architecture, data contracts, API specifications, and system components. Follows established feature development process with concise (5-10 page) specs focused on WHAT and WHY, not HOW to code. Optionally creates design brief for features with UI/UX complexity.

// tip: Run this command in your terminal to install the skill