Skip to content

ederfmatos/claude-voice-bridge / .claude/skills/cy-create-techspec

cy-create-techspec

Verified

Creates a Technical Specification by translating PRD business requirements into implementation designs through interactive technical clarification. Use when a PRD exists and needs a technical plan, or when technical architecture decisions need documentation. Do not use for PRD creation, task breakdown, or direct code implementation.

FileKindSize
SKILL.mdskill md9.1 KB
references/adr-template.mdmarkdown1.1 KB
references/techspec-template.mdmarkdown3.2 KB

references/techspec-template.md

View on GitHub
# TechSpec Template

Use this template to structure every Technical Specification. Fill each section based on technical clarification outcomes and codebase exploration. Omit sections that do not apply and note the reason.

## Executive Summary

Brief technical overview in 1-2 paragraphs:
- Key architectural decisions
- Implementation strategy and approach
- Primary technical trade-offs

## System Architecture

### Component Overview

Main components, their responsibilities, and relationships:
- Component name, purpose, and boundaries
- Data flow between components
- External system interactions

## Implementation Design

### Core Interfaces

Key service interfaces with code examples. Limit each example to 20 lines or fewer:
- Interface definitions and contracts
- Method signatures with parameter and return types
- Error handling conventions

### Data Models

Core domain entities and their relationships:
- Entity definitions with field types
- Request and response types for APIs
- Database schemas or storage structures

### API Endpoints

API surface organized by resource:
- Method, path, and description
- Request format and required fields
- Response format and status codes

## Integration Points

External services and system boundaries. Include only when the design integrates with systems outside the codebase:
- Service name and purpose of integration
- Authentication and authorization approach
- Error handling and retry strategy

## Impact Analysis

Table of components affected by this implementation:

| Component | Impact Type | Description and Risk | Required Action |
|-----------|-------------|---------------------|-----------------|
| [component] | [new/modified/deprecated] | [what changes and risk level] | [action needed] |

## Testing Approach

### Unit Tests

- Strategy and key components to test
- Mock requirements and boundaries
- Critical scenarios and edge cases

### Integration Tests

- Components to test together
- Test data requirements and setup
- Environment dependencies

## Development Sequencing

### Build Order

Ordered implementation sequence respecting dependencies:
1. [First component] - no dependencies
2. [Second component] - depends on step 1
3. [Continue with dependency chain]

### Technical Dependencies

Blocking dependencies that must be resolved before implementation:
- Infrastructure requirements
- External service availability
- Team deliverables or shared components

## Monitoring and Observability

Operational visibility for the implementation:
- Key metrics to track
- Log events and structured fields
- Alerting thresholds and escalation

## Technical Considerations

### Key Decisions

Significant technical choices with rationale:
- Decision: what was chosen
- Rationale: why this option
- Trade-offs: what was given up
- Alternatives rejected: what else was considered and why not

### Known Risks

Technical challenges and mitigation strategies:
- Risk description and likelihood
- Mitigation approach
- Areas requiring further research or prototyping

## Architecture Decision Records

ADRs documenting key decisions made during PRD brainstorming and technical design:
- [ADR-NNN: Title](adrs/adr-NNN.md) — One-line summary of the decision
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall