New: 97,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

Tech Spec

by iurysza in iurysza/module-graph

Produces implementation-ready technical specifications with concrete contracts, module boundaries, data flows, file changes, and test slices.

MITAuto-check passed

Install Tech Spec

skills CLI
$ npx skills add iurysza/module-graph --skill tech-spec -a claude-code

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

GitHub CLI
$ gh skill install iurysza/module-graph 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/iurysza/module-graph.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/tech-spec .claude/skills/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
tech-spec
GitHub stars
419
Token cost
~1.1k tokens
SKILL.md length
436 words
Files
1
Skills in repo
16
Repo updated
First seen
Licence
MIT

At a glance

Produces implementation-ready technical specifications with concrete contracts, module boundaries, data flows, file changes, and test slices.

  • Works in 6 steps: Establish current state → Compare real alternatives → Define contracts → …
  • Implementation handoffs
  • SKILL.md covers Choose the path, Build the spec, Required outline and Completion criteria
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Tech Spec is an agent skill from iurysza/module-graph. Produces implementation-ready technical specifications with concrete contracts, module boundaries, data flows, file changes, and test slices. Use for architecture or implementation handoffs.

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

The repository describes itself as: A Gradle Plugin for visualizing your project's structure, powered by mermaidjs. The licence is MIT.

When your agent uses it

  • Implementation handoffs

Example prompts

  • “Use the tech-spec skill to produce implementation-ready technical specifications with concrete contracts, module boundaries, data flows, file…”
  • “/tech-spec”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Establish current state
  2. Compare real alternatives
  3. Define contracts
  4. Trace behavior end to end
  5. Map files
  6. Plan vertical test slices

What it can do on your machine

Read from SKILL.md and the folder at commit 15b0135. 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 (its code samples are typescript and markdown).

    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

Tech Spec loads about 1.1k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 436 words of instructions outside code blocks.

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

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 iurysza/module-graph at commit 15b0135, republished under its MIT licence (© iurysza). 436 words, ~1,073 tokens.

Download SKILL.mdSave it as .claude/skills/tech-spec/SKILL.md (or your agent's skills folder).
name
tech-spec
description
Produces implementation-ready technical specifications with concrete contracts, module boundaries, data flows, file changes, and test slices. Use for architecture or implementation handoffs.
metadata.category
planning-architecture

Technical Specification

A tech spec is a typed architecture handoff. Types and call stacks define what changes; prose explains why.

This workflow is design-only. Do not implement. Write durable specs to ai-artifacts/specs/YYYY-MM-DD-<topic>.md unless the user or repository explicitly requires another location.

Choose the path

  • Convert context: use when conversation, docs, and code already define the problem and constraints.
  • Set up the goal first: use the setup-goal skill when important requirements, boundaries, or acceptance criteria remain unresolved.

Answer repository questions by inspecting the repository. Ask the user only for decisions.

Build the spec

1. Establish current state

Read relevant code, tests, docs, project instructions, domain vocabulary, and architectural decisions. Trace the existing entrypoint-to-effect flow.

Capture the problem, callers, goals, non-goals, constraints, invariants, affected systems, operational concerns, risks, and open questions. Do not invent missing requirements.

2. Compare real alternatives

Offer materially different designs. They should differ in ownership, interfaces, seam placement, call stack, runtime topology, or state model—not merely names.

For each option show:

  • domain and application types
  • public interfaces
  • module and adapter ownership
  • entrypoint-to-effect call stack
  • failure and cancellation behavior
  • persistence and transaction boundaries
  • testing seams
  • costs and risks

Choose the recommendation only after comparison.

3. Define contracts

Sketch every new or changed boundary in code:

ts
type Input = { /* parsed application values */ };
type Output = { /* caller-visible result */ };
type ExpectedFailure = FailureA | FailureB;

interface Capability {
  execute(input: Input): Promise<Result<Output, ExpectedFailure>>;
}

Cover domain values, state variants, request/response shapes, parsers, functions, ports, adapters, records, events, and public APIs as applicable. State what may cross each boundary and what must remain private.

4. Trace behavior end to end

For every affected behavior, show the call and data flow:

text
raw input
  -> protocol parser
  -> application/domain input
  -> service or domain operation
  -> outbound port
  -> adapter and external effect
  -> typed result or failure
  -> protocol projection

Include old versus proposed flow when changing an existing path. Add authorization, retries, cancellation, idempotency, transactions, observability, and runtime hops when reachable.

Show full SKILL.md (163 more words)Show less
5. Map files

List files to add, change, and delete. Give each file one clear responsibility tied to a contract or call-stack step.

6. Plan vertical test slices

Use red-green cycles, one behavior at a time:

  1. agree on the public seam;
  2. add one failing behavior test;
  3. write the minimum implementation to pass;
  4. repeat with the next behavior.

Cover happy paths, important failures, parser rejection, domain invariants, adapter contracts, persistence/runtime semantics, and end-to-end high-consequence flows. Avoid a horizontal “all tests, then all code” plan.

Required outline

markdown
# Title

## Summary
## Current State
## Goals
## Non-Goals
## Invariants and Constraints
## Alternatives
## Recommendation
## Domain Model and Types
## Interfaces and APIs
## Boundaries and Adapters
## Call Stacks and Data Flow
## Files to Add, Change, or Delete
## Red-Green Test Plan
## Risks and Open Questions

Compress sections that do not apply, but never omit changed contracts, call stacks, seams, or tests merely because they are difficult to specify.

Completion criteria

  • every requirement is grounded or marked open
  • alternatives are materially different
  • each changed boundary has a concrete contract
  • each behavior has an end-to-end call stack
  • each contract maps to a file or open question
  • the test plan proceeds in vertical red-green slices
  • another engineer can implement without guessing architecture

© iurysza, 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/tech-spec of iurysza/module-graph.

Open the folder on GitHubat commit 15b0135

Compare with similar skills

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.

Tech Spec compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tech Spec this skilliurysza/module-graph419—~1.1kAutomated safety check: PassMIT
Tech Contract Review Parth Desailawve-ai/awesome-legal-skills826—~4kAutomated safety check: PassCustom licence
Agent Specificationruvnet/ruflo74k3 repos~1.8kAutomated safety check: PassMIT
Contract Firstaffaan-m/ECC274k1 repos~2.4kAutomated safety check: PassMIT
Smart Contract Formal Verificationsickn33/agentic-awesome-skills47k1 repos~1.4kAutomated safety check: PassMIT
Smart Contract Upgrade Governancesickn33/agentic-awesome-skills47k1 repos~1.4kAutomated safety check: PassMIT

Similar skills

  • Tech Contract Review Parth Desai

    lawve-ai/awesome-legal-skills

    Contract Review for Tech and general contract. An agent skill from lawve-ai/awesome-legal-skills.

    826 GitHub stars~4k tokensUpdated 5 days ago
    Legal & ComplianceAuto-check passed

  • Agent Specification

    ruvnet/ruflo

    Agent skill for specification - invoke with $agent-specification

    74k GitHub starsUsed in 3 repos~1.8k tokens
    Product & Project ManagementAuto-check passed

  • Contract First

    affaan-m/ECC

    Coordinate frontend/backend or service-to-service work through one authoritative machine-checkable contract (OpenAPI, AsyncAPI, Protocol Buffers, or JSON Schema), with generated consumer types and…

    274k GitHub starsUsed in 1 repo~2.4k tokens
    Backend & APIsAuto-check passed

  • Smart Contract Formal Verification

    sickn33/agentic-awesome-skills

    Foundry and Soroban formal invariant verification register: state transition rules, boundary invariant properties, and symbolic execution checks.

    47k GitHub starsUsed in 1 repo~1.4k tokens
    Backend & APIsAuto-check passed

  • Smart Contract Upgrade Governance

    sickn33/agentic-awesome-skills

    Soroban WASM upgrade governance register: executable bytecode hash, timelocked migration delays, and multi-sig authorization quorum.

    47k GitHub starsUsed in 1 repo~1.4k tokens
    Backend & APIsAuto-check passed

  • Soroban Contract Audit

    sickn33/agentic-awesome-skills

    Soroban smart contract security audit register: authorization checks, panic pathways, integer overflows, and storage footprint verification for Stellar.

    47k GitHub starsUsed in 1 repo~1.4k tokens
    SecurityAuto-check passed

More from iurysza/module-graph

All 16 skills in this repo

  • Audio Transcribe

    iurysza/module-graph

    Transcribes local audio into Markdown with Gemini 3.5 Transcribe, including speaker labels and provider timestamps.

    419 GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Chatgpt Imagegen

    iurysza/module-graph

    Generates or edits raster images through OpenAI's Image API.

    419 GitHub stars~726 tokensUpdated today
    Auto-check passed

  • Gemini Tts

    iurysza/module-graph

    Generates spoken MP3 audio from text or Markdown with Gemini TTS.

    419 GitHub stars~968 tokensUpdated today
    Auto-check passed

  • Skill Cleaner

    iurysza/module-graph

    Audits installed Agent Skills for duplicates, unused candidates, loaded roots, oversized descriptions, and prompt cost.

    419 GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Brainstorming

    iurysza/module-graph

    Explores and validates a feature, component, workflow, or behavior change before implementation.

    419 GitHub stars~723 tokensUpdated today
    Auto-check passed

  • Domain Modeling

    iurysza/module-graph

    Maintains project domain language, context maps, diagrams, and architectural decisions under ai-artifacts.

    419 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Questions about Tech Spec

What does Tech Spec do?

Produces implementation-ready technical specifications with concrete contracts, module boundaries, data flows, file changes, and test slices. Tech Spec is an agent skill from iurysza/module-graph. Produces implementation-ready technical specifications with concrete contracts, module boundaries, data flows, file changes, and test slices.

When should I use Tech Spec?

Tech Spec fits situations like: implementation handoffs.

How do I install Tech Spec in Claude Code?

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

How do I install Tech Spec in Codex?

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

Can I use 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 iurysza/module-graph --skill 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/tech-spec, .gemini/skills/tech-spec, .github/skills/tech-spec and .opencode/skills/tech-spec in your project.

What does Tech Spec need to run?

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

Does 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 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 Tech Spec use?

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 Tech Spec use?

About 1.1k tokens (SKILL.md is roughly 4.3k 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 Tech Spec?

Skills that share tags, products or a category with Tech Spec: Tech Contract Review Parth Desai (lawve-ai/awesome-legal-skills, 826 stars), Agent Specification (ruvnet/ruflo, 74k stars), Contract First (affaan-m/ECC, 274k stars) and Smart Contract Formal Verification (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tech Spec?

iurysza (a GitHub user) maintains it in iurysza/module-graph, which has 419 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 7, 2026.

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