technical-spec-designlisted

Transforms product requirements into structured technical specifications. Auto-triggers when requirements are unclear, multiple implementation approaches exist, or component-level/architecture design is needed. Auto-trigger conditions: - User asks "how to implement a feature" - Requests design of technical specs / architecture / APIs / components - Mentions "multiple implementation approaches, need comparison" - Provides PRD / requirements description, wants technical specs - Requirements contain uncertainty or ambiguity NOT applicable for: - Simple bug fixes - Simple features with clear implementation path - Pure coding tasks (no design decisions)
wjszxli/technical-spec-design · ★ 2 · Web & Frontend · score 51

Install: claude install-skill wjszxli/technical-spec-design

# Technical Specification Design Skill ## 1. Input Contract Accepts the following input types: 1. Complete PRD document 2. Brief requirements description (may be incomplete) 3. Existing technical specification (for optimization/review) --- ## 2. Available Resources ### Core Templates | Resource | Purpose | Usage Scenario | | ---------------------------------------------------------------------------------- | -------------------- | ----------------------------- | | [`spec_template.md`](resources/spec_template.md) | Main spec template | Starting new technical specs | | [`component_template.md`](resources/component_template.md) | Component design | Designing individual components| | [`requirements_analysis_template.md`](resources/requirements_analysis_template.md) | Requirements analysis | Breaking down requirements | ### Examples | Resource | Purpose | | -------------------------------------------------------- | ------------- | | [`examples/sample_input.md`](examples/sample_input.md) | Sample PRD input | | [`examples/sample_output.md`](examples/sample_output.md) | Complete spec example | ### Scripts | Script | Purpose | Usage