Agent skill · duc01226
tech-spec
[Documentation] Use when (re)generating the DERIVED technical spec view over code + tests, or reporting canonical §8 TC/test-code drift. A GENERATOR — it projects code + tests into a regenerable per-component view and NEVER authors business content. Modes generate|audit|sync. Per-mode procedure lives in references/{author,sync}.md.
What it needs
About 9k tokens when loaded.
What this skill does
<!-- PROMPT-ENHANCE:STEP-TASK-ANCHOR:START --> [BLOCKING] Execute skill steps in declared order. NEVER skip, reorder, or merge steps without explicit user approval. [BLOCKING] Before each step or sub-skill call, update task tracking: set inprogress when step starts, set completed when step ends. [BLOCKING] Every completed/skipped step MUST include brief evidence or explicit skip reason. [BLOCKING] If Task tools are unavailable, create and maintain an equivalent step-by-step plan tracker with the same status transitions. <!-- PROMPT-ENHANCE:STEP-TASK-ANCHOR:END --> Quick Summary Portability: the technical root is read from docs/project-config.json → specRoots.technical.path (declared authorship: "derived", m1Policy: "exempt"). NEVER hardcode a root. {TechRoot}/{Service}/{Component}.md is a pattern — {Service} and {Component} are placeholders resolved from the repo, never literal names. [IMPORTANT] TaskCreate — Break ALL work into small tasks BEFORE starting (one task per emitted artifact). Goal: Generate, on demand, a regenerable single-writer technical view — per-component derived specs (use-case inventory, TC↔test map, cross-service topology) — projected FROM code and test annotations (TestSpec for business TC joins, TechnicalSpec for technical-only joins when present), so an engineer can read a component's technical surface without ever forking a second, hand-maintained source of truth. Code and tests are the source of truth; this skill only projects them. Summary: Purpose: a DERIVED-view generator ONLY — greps handlers/consumers/jobs/producers and test annotations to emit {TechRoot}/{Service}/{Component}.md; it NEVER authors business content. Code + tests stay the source of truth. Main steps (run in order): Step 0 Scope Gate — AskUserQuestion (service/component + mode), BLOCKING before any read; no source to derive from → STOP. Step 1 Derive facts — grep the use-case inventory, the TestSpec/TechnicalSpec joins, the topology. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills duc01226/tech-spec--fcd57f