tn plugin
Techneering — open-source unified skills plugin: spec-driven development workflow (draft/forge/audit/vault) + execution discipline (redgreen/assemble/diagnose) + code review + frontend design. 16 skills covering the full development lifecycle.
How to install the tn plugin
Run both commands inside Claude Code. The first adds the marketplace once; the second installs the plugin.
/plugin marketplace add devnomad-byte/techneering
/plugin install tn@techneeringWhat's inside tn
18 parts read from the plugin's own files.
Agents 1
Call as @agent-tn:name- @agent-tn:code-reviewerinherit
|
Skills 16
Claude loads it when the task matches- assemble
Use when executing implementation plans with independent tasks in the current session
- audit
Verify implementation matches change artifacts — dual-layer verification of code vs spec compliance and code vs real requirements. Use after implementation is complete.
- blueprint
Use when you have a spec or requirements for a multi-step task, before touching code
- compass
Use when starting any conversation — establishes how to find and use Techneering skills, requiring skill invocation before ANY response including clarifying questions
- craft
Create distinctive, production-grade frontend interfaces with high design quality. Auto-stacked onto an implementation path when a task involves frontend/UI work — pages, components, layouts, styles, interactions. Also available on demand as tn:craft.
- diagnose
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
- draft
Propose a new change with all artifacts generated in one step. Use when the user wants to describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
- forge
Implement tasks from a change. Use when the user wants to start or continue implementation of an existing change.
- gate
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs — requires running verification commands and confirming output before making any success claims; evidence before assertions always
- inspect
Use after tn:audit passes, when completing major features, or before merging — dispatches a global cross-task code review covering consistency, architecture, and security (distinct from tn:assemble's per-task review)
- isolate
Use when starting feature work that needs isolation from current workspace or before executing implementation plans — creates isolated git worktrees with smart directory selection and safety verification
- redgreen
Use when implementing any feature or bugfix, before writing implementation code
- scout
Enter scout mode — a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
- ship
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work — guides completion by presenting structured options for merge, PR, or cleanup
- spark
You MUST use this before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
- vault
Archive a completed change — delta spec merge and move to archive. Use when the user wants to finalize and archive a completed change.
Hooks 1
Runs on these events- SessionStartcommand
startup|resume|clear|compact
Using tn in Claude Code
Ask for an agent by name:
@agent-tn:code-reviewerSkills need no command. Claude reads them when your request matches what they describe.
Update, turn off or remove
- Update the plugin (shell)
- claude plugin update tn@techneering
- Refresh the marketplace
- /plugin marketplace update techneering
- Turn it off for now
- /plugin disable tn@techneering
- Remove it
- /plugin uninstall tn@techneering
Skills in tn
- assembledevnomad-byte/techneering
Use when executing implementation plans with independent tasks in the current session
4 files13stars - inspectdevnomad-byte/techneering
Use after tn:audit passes, when completing major features, or before merging — dispatches a global cross-task code review covering consistency, architecture, and security (distinct from tn:assemble's per-task review)
2 files13stars - redgreendevnomad-byte/techneering
Use when implementing any feature or bugfix, before writing implementation code
2 files13stars - auditdevnomad-byte/techneering
Verify implementation matches change artifacts — dual-layer verification of code vs spec compliance and code vs real requirements. Use after implementation is complete.
13stars - blueprintdevnomad-byte/techneering
Use when you have a spec or requirements for a multi-step task, before touching code
13stars - compassdevnomad-byte/techneering
Use when starting any conversation — establishes how to find and use Techneering skills, requiring skill invocation before ANY response including clarifying questions
13stars - craftdevnomad-byte/techneering
Create distinctive, production-grade frontend interfaces with high design quality. Auto-stacked onto an implementation path when a task involves frontend/UI work — pages, components, layouts, styles, interactions. Also available on demand as tn:craft.
13stars - diagnosedevnomad-byte/techneering
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
13stars - draftdevnomad-byte/techneering
Propose a new change with all artifacts generated in one step. Use when the user wants to describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
13stars - forgedevnomad-byte/techneering
Implement tasks from a change. Use when the user wants to start or continue implementation of an existing change.
13stars - gatedevnomad-byte/techneering
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs — requires running verification commands and confirming output before making any success claims; evidence before assertions always
13stars - isolatedevnomad-byte/techneering
Use when starting feature work that needs isolation from current workspace or before executing implementation plans — creates isolated git worktrees with smart directory selection and safety verification
13stars - scoutdevnomad-byte/techneering
Enter scout mode — a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
13stars - shipdevnomad-byte/techneering
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work — guides completion by presenting structured options for merge, PR, or cleanup
13stars - sparkdevnomad-byte/techneering
You MUST use this before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
13stars - vaultdevnomad-byte/techneering
Archive a completed change — delta spec merge and move to archive. Use when the user wants to finalize and archive a completed change.
13stars
tn plugin questions
How do I install the tn plugin?
In Claude Code run /plugin marketplace add devnomad-byte/techneering, then /plugin install tn@techneering.
What does the tn plugin include?
tn bundles 1 agent, 16 skills, hooks.
Which agents come with tn?
code-reviewer. Call one with @agent-tn:code-reviewer.
How do I update or remove the tn plugin?
Update it with claude plugin update tn@techneering in your shell, or from the Installed tab of /plugin. Remove it with /plugin uninstall tn@techneering.
What license is the tn plugin under?
MIT, as stated in the plugin's manifest.