Community template

Technical specification

Structures a feature spec from engineering notes with edge cases and open questions.

WritingInternal teamStructured docDirect tone5 steps512 installs

SKILL.mdReady to download

1---
2name: "tech-spec"
3title: "Technical specification"
4description: "Structures a feature spec from engineering notes with edge cases and open questions."
5audience: "internal"
6format: "structured-doc"
7tone: "direct"
8triggers:
9  - "technical specification"
10  - "write the tech spec"
11  - "turn these notes into a spec"
12---
13
14## Overview
15This skill handles **Technical specification**. It produces structured doc output in a direct voice, written for internal team.
16When this skill is triggered, expect the user to provide: **Engineering notes, feature requirements, constraints, and edge cases**. If this input has not been provided, ask for it before proceeding — do not guess or use placeholder data.
17## Process
181. Define the problem, scope, and non-goals clearly at the top.
192. Describe the proposed solution, architecture, and main flows.
203. Call out edge cases, dependencies, and risks explicitly.
214. List open questions that need decisions before implementation.
225. Document rollout and validation considerations.. Confirm this step is complete before moving on.
23## Quality Standards
24- Use headings the team already recognises
25- Assign an owner to every action item
26- Flag blockers or risks with clear impact statements
27- Keep it under 500 words unless complexity demands more
28
29## What to Avoid
30
31- Do not hide critical assumptions or leave risk analysis implicit.
32
33## Example Triggers
34- "technical specification"
35- "write the tech spec"
36- "turn these notes into a spec"

Install in Claude

This page gives you the actual file. Download it, add it to a Claude project, then test one of the trigger phrases below.

1
Download the skill file
Save the ready-to-use markdown file as `SKILL.md` so Claude can ingest it cleanly.
2
Open a Claude project
Create a new project for this workflow or open the existing project where you want the skill available.
3
Add `SKILL.md` to project knowledge
Upload the file into the project's files or knowledge area so Claude can read the instructions every time.
4
Trigger the workflow naturally
Use one of the suggested trigger phrases or ask for the task directly to confirm Claude picks up the skill.
5
Refine and re-upload if needed
If the output is close but not right, edit the markdown file, upload the new version, and test again.

Try these prompts

Use a natural request like these to confirm the skill is wired correctly.

"technical specification"

"write the tech spec"

"turn these notes into a spec"

What you get

A ready-to-use markdown file, trigger examples to test with, and step-by-step install guidance so you can move from browsing to using the skill immediately.

Need a version tailored to your own workflow?

Build a custom skill, download it instantly, and publish it when you want a shareable link.

Build your own skill