New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Write Tech Spec

by Terry-Mao in Terry-Mao/AICodingFlow

Write a code-grounded technical spec for a substantial or ambiguous feature in this repository.

MITAuto-check passedDevelopment

Install Write Tech Spec

skills CLI
$ npx skills add Terry-Mao/AICodingFlow --skill write-tech-spec -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Terry-Mao/AICodingFlow write-tech-spec --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Terry-Mao/AICodingFlow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/write-tech-spec .claude/skills/write-tech-spec && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
write-tech-spec
GitHub stars
167
Token cost
~785 tokens
SKILL.md length
418 words
Files
1
Skills in repo
30
Repo updated
First seen
Licence
MIT

At a glance

Write a code-grounded technical spec for a substantial or ambiguous feature in this repository.

  • Works in 5 steps: Problem — the technical problem and its… → Relevant code — files, symbols, entry… → Current state — how the system works and… → …
  • Development work in your project
  • SKILL.md covers Decide and research, Write the spec and Right-size and maintain
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Write Tech Spec is an agent skill from Terry-Mao/AICodingFlow. Write a code-grounded technical spec for a substantial or ambiguous feature in this repository.

Its SKILL.md is about 790 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. The repository describes itself as: Setup a AI Coding Flow. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/write-tech-spec”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Problem — the technical problem and its product relationship.
  2. Relevant code — files, symbols, entry points, and current ownership.
  3. Current state — how the system works and limitations that matter.
  4. Proposed changes — affected modules, types/APIs/state, data flow,
  5. Testing and validation — map tests, manual checks, screenshots/videos,

What it can do on your machine

Read from SKILL.md and the folder at commit 7703e16. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Write Tech Spec loads about 785 tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 418 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~28
When it runs · the whole SKILL.md, loaded when a task matches
~785

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Terry-Mao/AICodingFlow at commit 7703e16, republished under its MIT licence (© Terry-Mao). 418 words, ~785 tokens.

Download SKILL.mdSave it as .claude/skills/write-tech-spec/SKILL.md (or your agent's skills folder).
name
write-tech-spec
description
Write a code-grounded technical spec for a substantial or ambiguous feature in this repository.

write-tech-spec

Translate approved product intent into an implementation plan that fits the existing codebase. This is a local shared skill; wrappers may provide exact inputs and output paths that take precedence.

Decide and research

Use it when work spans modules, has architectural tradeoffs, needs a migration or rollout plan, or benefits from review before implementation. Skip it for straightforward fixes, small refactors, and narrow UI changes with no technical ambiguity. Prefer a product spec first; an end-to-end prototype can be a better precedent when the implementation is still uncertain.

Before drafting, read the product spec when present and inspect the actual repository. Identify current behavior, relevant files/types/entry points, data or control flow, ownership boundaries, dependencies, risks, and validation constraints. Do not infer architecture that can be read from code.

When a code reference matters, pin it to the inspected commit SHA and include a repo-relative path with line numbers. Add a GitHub blob/<sha>/...#Lx-Ly link when the repository has an accessible remote; otherwise keep the local reference. Reference the product spec for behavior rather than restating it.

Write the spec

Use the following core sections, keeping each only as detailed as the decision requires:

  1. Problem — the technical problem and its product relationship.
  2. Relevant code — files, symbols, entry points, and current ownership.
  3. Current state — how the system works and limitations that matter.
  4. Proposed changes — affected modules, types/APIs/state, data flow, ownership boundaries, sequencing, and tradeoffs.
  5. Testing and validation — map tests, manual checks, screenshots/videos, or other evidence to the product behavior and its numbered invariants.
Show full SKILL.md (162 more words)Show less

Add these sections when they add signal:

  • End-to-end flow — when tracing the main path clarifies the change list.
  • Risks and mitigations — when there are real regression, migration, rollout, or compatibility hazards.
  • Follow-ups — when there is deferred technical debt or an open technical question.

For small changes, combine the problem, current state, and relevant code into a short context section when the wrapper permits it. Omit empty optional sections; do not pad the document with generic architecture prose. Evaluate parallel work only when the surrounding workflow explicitly allows delegation and it materially reduces time or isolates ownership; otherwise omit it.

Right-size and maintain

A single-file change may not need a tech spec; a multi-module feature is often about 80–150 lines; larger documents are justified by real cross-cutting risk. If implementation diverges from the plan, update tech.md in the same change when practical. An optional DECISIONS.md can capture major technical choices for large features, but is not required.

Related skills: write-product-spec, spec-driven-implementation, and implement-specs.

© Terry-Mao, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/write-tech-spec of Terry-Mao/AICodingFlow.

Open the folder on GitHubat commit 7703e16

Compare with similar skills

Write Tech Spec next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Write Tech Spec compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Write Tech Spec this skillTerry-Mao/AICodingFlow167—~785Automated safety check: PassMIT
Vercel Composition Patternssupabase/supabase111k59 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Vercel Composition Patterns

    supabase/supabase

    Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 59 repos~726 tokens
    DevelopmentAuto-check passed

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from Terry-Mao/AICodingFlow

All 30 skills in this repo

  • PR Walkthrough

    Terry-Mao/AICodingFlow

    Generate a local static interactive D3 walkthrough of a pull request.

    167 GitHub stars~2.1k tokensUpdated 4 days ago
    Auto-check passed

  • Update PR Review

    Terry-Mao/AICodingFlow

    Improve repo-local PR review companion skills from human feedback on bot reviews.

    167 GitHub stars~1.1k tokensUpdated 4 days ago
    Auto-check passed

  • Implement Issue

    Terry-Mao/AICodingFlow

    Implement a GitHub issue in this repository by applying the local shared implement-specs workflow with repository-specific issue, spec-context, and summary-file handling.

    167 GitHub stars~2.3k tokensUpdated 4 days ago
    Auto-check passed

  • Implement Specs

    Terry-Mao/AICodingFlow

    Implement an approved feature from the repository's product and tech specs, keeping specs and code aligned in the same change as implementation evolves.

    167 GitHub stars~1.7k tokensUpdated 4 days ago
    Auto-check passed

  • Review PR

    Terry-Mao/AICodingFlow

    Review a GitHub pull request from pinned prdescription.txt, prdiff.txt, and optional speccontext.md snapshots, then write and validate review.json.

    167 GitHub stars~1k tokensUpdated 4 days ago
    Auto-check passed

  • Update Dedupe

    Terry-Mao/AICodingFlow

    Learn repo-local duplicate issue guidance from recent maintainer duplicate closures and propose updates to the dedupe companion skill.

    167 GitHub stars~1.1k tokensUpdated 4 days ago
    Auto-check passed

Categories

Questions about Write Tech Spec

What does Write Tech Spec do?

Write a code-grounded technical spec for a substantial or ambiguous feature in this repository. Write Tech Spec is an agent skill from Terry-Mao/AICodingFlow. Write a code-grounded technical spec for a substantial or ambiguous feature in this repository.

When should I use Write Tech Spec?

Write Tech Spec fits situations like: development work in your project.

How do I install Write Tech Spec in Claude Code?

Run `npx skills add Terry-Mao/AICodingFlow --skill write-tech-spec -a claude-code`. Or copy the skill folder (.agents/skills/write-tech-spec in Terry-Mao/AICodingFlow) into .claude/skills/write-tech-spec in your project. Claude Code loads it when a task matches its description.

How do I install Write Tech Spec in Codex?

Run `npx skills add Terry-Mao/AICodingFlow --skill write-tech-spec -a codex`. Or copy the skill folder (.agents/skills/write-tech-spec in Terry-Mao/AICodingFlow) into .agents/skills/write-tech-spec in your project. Codex loads it when a task matches its description.

Can I use Write Tech Spec in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Terry-Mao/AICodingFlow --skill write-tech-spec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-tech-spec, .gemini/skills/write-tech-spec, .github/skills/write-tech-spec and .opencode/skills/write-tech-spec in your project.

What does Write Tech Spec need to run?

SKILL.md names no scripts, command-line tools or credentials: Write Tech Spec is instructions for the agent only.

Does Write Tech Spec access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Write Tech Spec safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Write Tech Spec use?

Write Tech Spec is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Write Tech Spec use?

About 785 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Write Tech Spec?

Skills that share tags, products or a category with Write Tech Spec: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Write Tech Spec?

Terry-Mao (a GitHub user) maintains it in Terry-Mao/AICodingFlow, which has 167 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 3, 2026.

Source: Terry-Mao/AICodingFlow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.