Tech Spec

Name: Tech Spec
Author: sd0xdev

ASecurity

Tech spec knowledge base. Full workflow from requirement analysis, code research to spec output.

191 stars
0 votes
0 copies
2 views
Added February 7, 2026

developmentgobashtestinggitapi

Works with

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned February 12, 2026

npx -y skills add sd0xdev/sd0x-dev-flow --skill tech-spec --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Tech Spec?

Add the live security badge to your README. It updates with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/sd0xdev-tech-spec/badge)](https://www.skillsdirectory.com/skills/sd0xdev-tech-spec)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: tech-spec
description: Tech spec knowledge base. Full workflow from requirement analysis, code research to spec output. 
Triggers: tech spec, feature design, requirement analysis.
allowed-tools: Read, Grep, Glob, Write, Bash(git:*)
---

# Tech Spec Skill

## Trigger

- Keywords: tech spec, technical specification, spec review, review spec, requirement analysis, feature design

## When NOT to Use

- Creating request documents (use /create-request)
- Code implementation (use feature-dev)
- Architecture consulting (use /codex-architect)

## Commands

| Command         | Purpose              | When                    |
| --------------- | -------------------- | ----------------------- |
| `/tech-spec`    | Produce tech spec    | Starting from scratch   |
| `/deep-analyze` | Deepen spec + roadmap | After initial concept   |
| `/review-spec`  | Review tech spec     | Spec confirmation       |

## Workflow

```mermaid
sequenceDiagram
    participant A as Analyst
    participant C as Codebase
    participant D as Document

    A->>A: 1. Requirement clarification
    A->>C: 2. Code research
    C-->>A: Related modules
    A->>A: 3. Solution design
    A->>A: 4. Risk assessment
    A->>A: 5. Work breakdown
    A->>D: 6. Output document
```

## Spec Structure

1. Requirement summary (problem + goals + scope)
2. Existing code analysis
3. Technical solution (architecture + data model + API + core logic)
4. Risks and dependencies
5. Work breakdown
6. Testing strategy
7. Open questions

## Verification

- Solution covers all requirement points
- Architecture diagrams use Mermaid
- Risks have mitigation strategies
- Work can be broken into trackable items

## References

- `references/template.md` - Spec template + review dimensions

## File Location

```
docs/features/{feature}/
├── tech-spec.md      # Technical spec
├── requests/         # Request documents
└── README.md         # Feature description
```

## Examples

```
Input: /tech-spec "Implement user asset snapshot feature"
Action: Requirement clarification -> Code research -> Solution design -> Output document
```

```
Input: /review-spec docs/features/xxx/tech-spec.md
Action: Read -> Research -> Review -> Output report + Gate
```