Carly Tech Spec

Co-author a technical design specification through structured conversation. Guides you through problem statement, goals, current state, proposed solution, alternatives, risks, and milestones — with a fixed template and coaching at each step. Use when writing a tech spec, design doc, technical proposal, or RFC.

9 starsWriting & Content Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add carlymr/carlys-claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add carlymr/carlys-claude-skills --skill carly-tech-spec
Manual install
git clone --depth 1 https://github.com/carlymr/carlys-claude-skills.git /tmp/carlys-claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/carlys-claude-skills/skills/carly-tech-spec ~/.claude/skills/carly-tech-spec

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Tech Spec Co-Authoring

Guide the user through writing a technical design spec using a fixed template. Work section by section, asking targeted questions and drafting iteratively.

## Step 1 — Setup

Read `references/template.md` (relative to this skill's directory) to load the template structure.

Ask the user:
1. What is this spec about? (one sentence)
2. Who is the audience? (engineering team, leadership, cross-functional, etc.)

Create a spec file in the working directory named `tech-spec-<short-name>.md` using the template skeleton from `references/template.md`. Fill in the title, author (ask if unknown), date, and set status to "Draft". Strip the guidance comments (lines starting with `>`) — those are only for your reference during authoring.

## Step 2 — Problem Statement

This is the most important section. Do not rush it.

A real problem statement describes **a pain that real users or customers are experiencing in their lives or work today** — something that's broken, frustrating, costly, or impossible for them right now. The test is: if no one ever built this product, would someone still be hurting? If yes, that's a problem. If no, there isn't one yet.

Ask the user to describe the problem in their own words. Then ask clarifying questions that drive toward concrete, external pain:
- "Who specifically is feeling this, and how do you know? What have they said or done?"
- "What are they trying to accomplish, and what's getting in their way today?"
Read the full skill on GitHub

Details

Skill name
carly-tech-spec
Path
skills/carly-tech-spec/SKILL.md
Repo updated
4 October 2026

FAQ

What does the Carly Tech Spec skill do?

Co-author a technical design specification through structured conversation. Guides you through problem statement, goals, current state, proposed solution, alternatives, risks, and milestones — with a fixed template and coaching at each step. Use when writing a tech spec, design doc, technical proposal, or RFC.

How do I install the Carly Tech Spec skill?

Claude Code plugin: /plugin marketplace add carlymr/carlys-claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Carly Tech Spec popular?

It lives in carlymr/carlys-claude-skills, which has 9 GitHub stars and 0 forks.

Related skills

Carly Code Review

9

carlymr/carlys-claude-skills

Comprehensive code review using 7 parallel specialized sub-agents (correctness, security, performance, simplicity, UX, codebase integration, documentation). Every finding needs a concrete failure scenario; Critical/Warning findings are then challenged by adversarial refuter agents before they reach the report. Repos can add their own reviewers via an `Extra reviewers:` list in CLAUDE.md. Use when reviewing code changes, pull requests, or local diffs. Supports local git diff (no arguments) or GitHub PR (pass PR number or URL as argument).

Git & Code Review

Carly Product Req

9

carlymr/carlys-claude-skills

Co-author a lightweight product requirements document through structured conversation. Guides non-technical teammates through problem statement, users, goals, success signals, and open questions — producing a short doc (~1 page) that's ready to hand off for a tech spec. Use when writing product requirements, a PRD, feature brief, or scoping a new product idea.

Writing & Content

Kallaway Content System

10

anthonysurfermx/creator-knowledge-engine

Use this skill to design content production workflows, build batch creation systems, plan posting schedules, structure teams, select platforms, pick a niche, avoid production anti-patterns, and scale a content operation. [trigger phrases: content workflow, batch, calendar, production, team, posting schedule, content machine, repurpose, publishing cadence, idea mining, volume strategy, niche selection, content ramp, short form system, content operator, editor stack, platform expansion, idea system, daily rep, season 1 season 2, quality vs quantity, content scientist, de-risk the rep, violent vo

Writing & Content

Kallaway Hooks

10

anthonysurfermx/creator-knowledge-engine

Use this skill to write viral hooks, scroll-stopping openings, and curiosity loops using Kallaway's proven frameworks. Trigger when the user asks to: write a hook, improve a hook, rewrite an intro, fix the first 5 seconds, write an opening line, make content scroll-stopping, write a YouTube hook, write a TikTok hook, write a Reels hook, write a LinkedIn hook, write a Twitter thread opener, create curiosity, write a video script opening, build tension in an intro, write a short-form hook, write a long-form hook, improve retention in the first seconds, write a desire-based hook, write a fear-bas

Writing & Content

Answer First

10

charlie947/skills-for-everyone

Shape every answer so the bottom line comes first. Sentence one is the answer, the number, the verdict or the one thing to do. Everything after it is support. Use when the user asks for output that is short, skimmable, action-led or "no waffle", and keep applying it for the whole conversation once invoked, not just one reply. Triggers on "answer first", "bottom line first", "no preamble", "no waffle", "keep it short", "just tell me what to do", "cut the fluff", "ADHD mode", or any request to stop burying the answer in paragraph four. It shapes Claude's replies to you, not writing you publish.

Writing & Content

Kallaway Packaging

10

anthonysurfermx/creator-knowledge-engine

Use this skill to create high-CTR titles, thumbnails, and content angles that maximize clicks and viewer conversion. Trigger phrases: title, thumbnail, CTR, click-through, headline, packaging, angle, positioning, topic selection, thumbnail design, title writing, content angle, hook design, caption first line, short-form hook, desire loop, interest loop, visual stun, thumbnail text, title thumbnail combo, clickbait, click bait, why nobody is clicking, my video has no views, packaging my content, improve my thumbnail, write me a title, generate title ideas, title options, thumbnail concept, thum

Writing & Content

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.