技术规格说明书生成器 - AI驱动，快速创建PRD、API设计、架构文档

technical-specification by aj-geddes/useful-ai-prompts

251 周安装量

141 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill technical-specification

开发技术文档产品管理

🇨🇳中文介绍

技术规格说明书

概述

创建全面的技术规格说明书，用于定义软件项目的系统需求、架构、实现细节和验收标准。

使用场景

功能规格说明书
系统设计文档
需求文档 (PRD)
架构决策记录 (ADR)
技术提案
RFC (征求意见稿)
API 设计规格
数据库模式设计

快速开始

最小工作示例：

# Technical Specification: [Feature Name]

**Document Status:** Draft | Review | Approved | Implemented
**Version:** 1.0
**Author:** John Doe
**Date:** 2025-01-15
**Reviewers:** Jane Smith, Bob Johnson
**Last Updated:** 2025-01-15

## Executive Summary

Brief 2-3 sentence overview of what this spec covers and why it's being built.

**Problem:** What problem are we solving?
**Solution:** High-level description of the solution
**Impact:** Expected business/user impact

---

## 1. Background

### Context

Provide background on why this feature is needed:

// ... (see reference guides for full implementation)

参考指南

references/ 目录下的详细实现：

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

指南	内容
Functional Requirements	功能需求
Non-Functional Requirements	非功能需求
Database Schema	数据库模式
API Data Models	API 数据模型
Authentication Endpoints	认证端点
Rate Limiting	速率限制
Phase 1: Core Authentication	Phase 1: Core Authentication (Week 1-2), Phase 2: Email Verification (Week 3), Phase 3: Social Login (Week 4), Phase 4: Security Features (Week 5) (+1 more)

🇺🇸English

Technical Specification

Overview
When to Use
Quick Start
Reference Guides
Best Practices

Overview

Create comprehensive technical specifications that define system requirements, architecture, implementation details, and acceptance criteria for software projects.

When to Use

Feature specifications
System design documents
Requirements documentation (PRD)
Architecture decision records (ADR)
Technical proposals
RFC (Request for Comments)
API design specs
Database schema designs

Quick Start

Minimal working example:

# Technical Specification: [Feature Name]

**Document Status:** Draft | Review | Approved | Implemented
**Version:** 1.0
**Author:** John Doe
**Date:** 2025-01-15
**Reviewers:** Jane Smith, Bob Johnson
**Last Updated:** 2025-01-15

## Executive Summary

Brief 2-3 sentence overview of what this spec covers and why it's being built.

**Problem:** What problem are we solving?
**Solution:** High-level description of the solution
**Impact:** Expected business/user impact

---

## 1. Background

### Context

Provide background on why this feature is needed:

// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

Guide	Contents
Functional Requirements	Functional Requirements
Non-Functional Requirements	Non-Functional Requirements
Database Schema	Database Schema
API Data Models	API Data Models
Authentication Endpoints	Authentication Endpoints
Rate Limiting	Rate Limiting
Phase 1: Core Authentication

Best Practices

✅ DO

Include acceptance criteria for each requirement
Provide architecture diagrams
Document API contracts
Specify performance requirements
List risks and mitigations
Include implementation timeline
Add success metrics
Document security considerations
Version your specs
Get stakeholder review

❌ DON'T

Be vague about requirements
Skip non-functional requirements
Forget about security
Ignore alternatives
Skip testing strategy
Forget monitoring/observability
Leave questions unanswered

Weekly Installs

218

Repository

aj-geddes/usefu…-prompts

GitHub Stars

121

First Seen

Jan 21, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

opencode188

gemini-cli178

codex173

cursor168

claude-code154

github-copilot149