tech-blueprinting

tech-blueprinting is a skill for Claude Code from nanparth/ai-skill-hub. It costs 85 tokens per session (1,263 once invoked), scanned A, original, MIT.

A step-by-step workflow for creating technical documents through drafting, review, and reader testing. It also includes guidance for writing or updating READMEs, which explain how a software project works.

In plain words
What is it for?
Use it for specifications, product requirements documents, RFCs, decision records, implementation plans, development plans, and README files.
Why use it?
It gives you a repeatable way to gather context, organize a document, and check it for gaps before finishing.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions subagents.

Good fit Use it for specifications, product requirements documents, RFCs, decision records, implementation plans, development plans, and README files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nanparth/ai-skill-hub/tech-blueprinting
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add nanparth/ai-skill-hub --skill tech-blueprinting
Clone the repo
git clone --depth 1 https://github.com/nanparth/ai-skill-hub

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for tech-blueprinting

README.md
[![agentmods](https://agentmods.dev/badge/skills/nanparth/ai-skill-hub/tech-blueprinting/github.svg)](https://agentmods.dev/skills/nanparth/ai-skill-hub/tech-blueprinting)
Your own site
<a href="https://agentmods.dev/skills/nanparth/ai-skill-hub/tech-blueprinting"><img src="https://agentmods.dev/badge/skills/nanparth/ai-skill-hub/tech-blueprinting/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for tech-blueprinting

Your own site · 80×15
<a href="https://agentmods.dev/skills/nanparth/ai-skill-hub/tech-blueprinting"><img src="https://agentmods.dev/badge/skills/nanparth/ai-skill-hub/tech-blueprinting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 85 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,263 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00085 $0.01263
Opus 5 $0.00043 $0.00632
Sonnet 5 $0.00017 $0.00253
Haiku 4.5 $0.00009 $0.00126

Measured 10d ago against content hash 6cb33465fa0b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

tech-blueprinting scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

The scan reads SKILL.md. This mod also ships 4 executable files (scripts/helper.js, scripts/server.cjs, scripts/start-server.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

tech-blueprinting/SKILL.md · 106 lines

How it starts

The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Tech Blueprinting Workflow

A structured three-stage collaborative workflow for producing technical documents. Stages target predictable failure modes: missing context, disorganized drafting, and author blind spots.

Dependencies

The core writing workflow needs only file read/write access in the user's chosen project or output folder. The visual companion is optional and requires Node.js, shell support, and a local browser.

Loading Maps

Resource File Load when
Visual Companion workflows/visual-companion.md User accepts visual companion offer.
Spec Reviewer agents/spec-reviewer.md After near completion, before reader testing.
Reader Tester agents/reader-tester.md Stage 3 reader testing dispatch.
README Workflow workflows/readme-write.md User wants to write, update, or refresh a README.
README Template references/readme-template.md README workflow drafting.
README Self-Review references/readme-self-review.md README workflow quality check.
Plan Template references/plan-template.md Document type is an implementation plan.
Test Level Protocol shared/test-level-protocol.md Implementation assertions plus boundary signals.
Code Organization shared/code-organization.md Multi-file implementation or architecture spec.

Test Level Gate

Load shared/test-level-protocol.md and evaluate when any boundary signal is present in an implementation-oriented spec: subprocess spawn, IPC or HTTP boundary, filesystem state written then read, lock or PID coordination, external tool, cross-language boundary, CLI entrypoint, public schema, config, API payload, or file format change.

Skip when the work is a single module with pure logic and no I/O. Decide the test level before drafting and include the recommendation in the plan.

Document Type Routing

Before offering the three-stage workflow, check for a specialized workflow match.

Signal Route Why
User mentions README, usage docs, refresh docs, or document this skill Load workflows/readme-write.md READMEs follow a fixed source-reading and template workflow.
User mentions implementation plan, dev plan, task breakdown, or execute-ready plan Load references/plan-template.md before drafting Plans need task shape, commands, boundaries, and TDD-ready steps.

Read the full file on GitHub · 106 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 106 lines · 85 tokens per session scan A 6cb33465fa0b

Subscribe to this mod's changes

tech-blueprinting is a skill published in the GitHub repository nanparth/ai-skill-hub (23 stars, last pushed 18d ago), licensed MIT. It adds 85 tokens to every session and 1,263 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens