Skill

tech-spec

Generates and reviews numbered tech specs for features, covering requirements, code analysis, solution design, risks, work breakdown, and testing. Auto-detects create/update via filesystem and git diff.

Git

documentation

npx claudepluginhub sd0xdev/sd0x-dev-flow --plugin sd0x-dev-flow

Tool Access

This skill is limited to using the following tools:

ReadGrepGlobBash(git:*)Write

Preview

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

Supporting Assets

references/feature-context-resolution.mdreferences/template.md

SKILL.md

Similar Skills

tech-spec:create

Creates technical specifications interactively by gathering requirements, exploring codebases, running planning interviews, drafting with Mermaid diagrams, expert review, and iteration. For new features or projects needing architecture and decisions.

1 file

tech-spec

quick-spec

Creates implementation-ready technical specifications via 4-step conversational workflow with tasks, acceptance criteria, and code investigation for feature planning.

4 files

skillkit-essentials

create-spec

Creates or updates SPEC.md documents from requirements, notes, or interview output, structuring into sections for goals, design, edge cases, security, testing, and success criteria. Use for feature specs.

1 file

amplify

Stats

Stars147

Forks20

Last CommitApr 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Tech Spec Skill

Trigger

Keywords: tech spec, technical specification, spec review, review spec, 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`	Create or update tech spec	Auto-detects create/update from filesystem state
`/deep-analyze`	Deepen spec + roadmap	After initial concept
`/review-spec`	Review tech spec	Spec confirmation

Context-Aware Mode (Upsert)

When invoked without a full requirement description, the skill auto-detects the target feature using the 5-level cascade from references/feature-context-resolution.md.

Filesystem State	Action
`docs/features/<key>/2-tech-spec.md` exists	Update mode: read existing spec, research code changes since last update, incrementally update changed sections
`docs/features/<key>/2-tech-spec.md` absent	Create mode: generate new spec from template
Feature not resolved	Gate: Need Human

In update mode, focus on sections affected by recent code changes (use git diff to identify). Preserve unchanged sections.

Workflow

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

Requirement summary (problem + goals + scope)
Existing code analysis
Technical solution (architecture + data model + API + core logic)
Risks and dependencies
Work breakdown
Testing strategy
Open questions

Output

Numbered tech spec document with sections: Overview, Requirements, Architecture, Implementation plan, Work breakdown, Testing strategy, 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}/
├── 2-tech-spec.md    # Technical spec (numbered per docs-numbering rule)
├── 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/2-tech-spec.md
Action: Read -> Research -> Review -> Output report + Gate