| Type | Keywords | Prefix |
|---|---|---|
| session | session / compact / compress |
KNW- |
| template | template / tpl / template |
TPL- |
| recipe | recipe / rcp / recipe / steps |
RCP- |
| reference | reference / ref / reference |
REF- |
| decision | decision / dcs / adr / decision |
DCS- |
| tip | tip / note / tips / record |
TIP- |
| asset | asset / asset |
AST- |
| blueprint | blueprint / blueprint |
BLP- |
| document | document / doc / document |
DOC- |
Pass the full $ARGUMENTS to the workflow as its intent (the first capture argument is implied). The workflow infers one of the nine compatible types and writes through the canonical CLI.
Minimal ordinary creation is maestro knowhow add --type <type> --title "<title>" --content-file <path>: type, title, and content are the only required knowledge parameters. Keywords, sourceRef, relatedPaths, applicability, language, decision state, explicit ID, and tool are advanced optional metadata. Repository authority is host-owned: omit targetRepoId for current-repository writes; pass the exact host-supplied stable UUID only for an explicitly selected linked write with live knowhow write capability. Never derive identity from cwd/name/alias/path or persist those values as identity.