techneering

⚒️ Techneering

Engineering, with ancient discipline.

Write the spec. Strike while it's hot. Ship with confidence.

tn: · a skills plugin for Claude Code and Codex

English · 简体中文

The problem

A model coding on its own will drift. It guesses when it should ask. It over-builds when it should stop. It forgets decisions made ten minutes ago, declares success without checking, and leaves you to discover — in review, in prod, at 2 a.m. — what it quietly got wrong.

The output looks like code. It isn't craft.

The discipline

Techneering wraps the model in a harness — Anthropic's word for the scaffolding around an agent — so its effort stays pointed where you aimed it. Sixteen skills walk a change from idea, through spec and code, to a verified, archived release.

The spec is the contract. The harness is the discipline. Every line of code traces back to a requirement; nothing ships on a hunch.

Four layers, one system

AI tooling has evolved through four layers. Most stop at one. Techneering was built for all of them.

These aren't separate features — they're the same system seen from four angles. And Techneering keeps the parts loop systems usually skip: explicit failure limits, generation ≠ evaluation, and a depth dial so a trivial tweak skips the full ceremony.

The 16 Skills

The names follow a forge workshop: the spec is raw material, the code is the forged product, and each skill is a station on the shop floor.

🧭 The Smithy — core flow

🧠 The Drawing Board — thinking & planning

🔨 The Anvil — execution

🔍 The Inspection Bench — quality gates

📦 The Shipping Dock — utilities

Quick Start

Techneering runs on both Claude Code and Codex. Same skills, same tn: prefix — pick your host.

Claude Code:

# 1. Register the marketplace
claude plugin marketplace add https://github.com/devnomad-byte/techneering.git

# 2. Install — project-scoped is recommended
claude plugin install tn@techneering -s project

# 3. Start Claude Code and strike
claude

Codex:

# 1. Register the marketplace (clones the repo as a source)
codex plugin marketplace add devnomad-byte/techneering

# 2. Install
codex plugin install tn@techneering

# 3. Start Codex and strike
codex

Then type /tn:scout to take it for a spin. On every session start, tn:compass is auto-injected (via the SessionStart hook on either host) — just say what you want to build and Techneering routes you to the right station.

How It Works

Techneering picks one of four paths based on change size, then walks you through it station by station:

Always available:

• scout — pure thinking, writes no files
• craft — auto-stacked when frontend work is detected

Inside forge, two skills chain automatically — blueprint breaks the work into tasks, assemble dispatches a fresh subagent per task with spec-compliance + code-quality review after each.

Every skill writes its progress to disk. Close the terminal, come back tomorrow — Techneering scans the files and resumes exactly where you struck off.

Design Philosophy

You drive the AI. Not the other way around.

This pattern — decompose, hand off via artifacts, separate generation from evaluation — comes from Anthropic's work on long-running agents. Techneering applies it to human-in-the-loop development: the harness keeps the AI disciplined, you keep the harness pointed at the right target.

The loop is the latest layer — a pattern Addy Osmani named in 2025: stop hand-prompting every step, design the system that does it. Techneering was built this way from the start — including the parts most loop systems skip: explicit failure limits (tn:diagnose stops after 3 failed fixes), generation ≠ evaluation (the writer never grades its own work), and a depth dial so trivial tweaks skip the full ceremony.

The Workspace

Running tn:draft generates a self-contained workspace at your project root. It is the source of truth; nothing lives only in chat.

techneering/
├── config.yaml          # tech stack · coding style · quality rules
├── specs/               # authoritative module definitions
├── changes/
│   └── <name>/          # one directory per change
│       ├── .tn.yaml
│       ├── proposal.md  # why  — the motivation
│       ├── specs/       # what — SHALL/MUST · WHEN/THEN
│       ├── design.md    # how  — decisions & trade-offs
│       └── tasks.md     # todo — checkbox-tracked, resumable
└── archive/             # finished changes, fully preserved

tn:audit traces every line of code back to a requirement. tn:vault merges finished specs into the main specs/, so knowledge compounds instead of evaporating.

Requirements

Pick one host (Techneering works on either, or both):

Runs on Windows 10/11 · macOS 12+ · Linux.

Star History