Hub
design-docs
Four commands for the writing a repository asks for before code — an ADR, an architecture map, a fitness function and a high-level design — each refusing to assert what the tree does not show.
Install
Staged first, the resolved commit pinned in .arcturn-install.json, then linked into the roots Arcturn scans. Nothing is linked before the pin.
To see the table below derived from the package itself rather than from this entry, run arcturn inspect sitharaj88/arcturn/kits/design-docs — it stages exactly as an install would, links nothing, and prints what it would add.
Source
- Repository
- sitharaj88/arcturn/kits/design-docs
- Maintainer
- Sitharaj Seenivasan
- Contents
- 4 skills
Usage
What you would type
Every command this package adds, in the form you would run it. A slash command is invoked by its own name; a pipeline goes through /workflow.
/adr-recordRecord one architecture decision as Proposed, with rejected alternatives only where the author supplied them or the repo shows they were tried./arch-mapMap a codebase from resolved imports at file:line — no node and no edge without ledger evidence, and every unresolvable wiring listed rather than drawn./fitness-functionTurn an architectural rule into a check and prove it bites — FAIL on a planted violation, PASS on HEAD, both transcripts, or the output is UNPROVEN CHECK./hld-draftDraft a high-level design as a scaffold with labelled holes — every constraint cited to a file:line or a quoted brief, everything else Assumed — unconfirmed.
Disclosure
What this would add to your machine
Read in the same vocabulary the installer uses: derived lanes, declared tools, stage counts, budgets, and whether any of it is executable code.
Skills
4
- /adr-record
- /arch-map
- /fitness-function
- /hld-draft
No executable code disclosed
This entry declares no extensions/. Verify it against the package itself with arcturn inspect — and note that the installer would confirm-gate executable code either way, whatever a listing says.