Use macstack-dev:intake. It owns the loop; this command only routes into it.
Three ways material arrives, one loop
- A file in
inbox/ — a PDF, a spec, a screenshot, a spreadsheet. Anything.
- A stray file that appeared in
client/ — anything there that is not one of the
six documents is incoming material, not a document. Move it to inbox/ first.
- Text typed into this chat. "убери геолокацию", "клиент сказал, что счета должны
выходить 5-го". Write it to
inbox/<date>-<slug>.md before doing anything else.
The third is the one people forget to record. A correction that exists only in a chat
transcript has no source: six months later nobody can say who asked for it or when, and
the document says something nobody can trace. Write it down first, then work.
The loop, and none of it is optional
Land it. The file goes into inbox/ under an ASCII name and gets an entry in the
manifest. A source already committed in this repo is cited by path, never copied.
Nothing in inbox/ is ever edited afterwards.
Read it. Check size and first bytes before parsing — an iCloud placeholder reads
as empty and yields a confidently wrong delta. .xlsx is refused: ask for a CSV
beside it and write no log entry, so the file stays in the unprocessed set.
Work out the delta. Contradictions with what the documents already say, and
additions. For each contradiction: what it touches, and what it costs if we choose
wrong. A delta is a proposal, not an edit.
Ask, then decide. Every contradiction goes to the owner as a question with two
real options: the recommendation you would defend, and "write it into
OPEN-QUESTIONS.md and let the client answer". Never both silently.
Record the ruling in history/DECISIONS.md with its cost-if-wrong clause, written
NOW, before the outcome is known — a retrospective cost clause is worthless.
Apply in one direction: client/ → generated/ → macstack.json. Client prose
is edited through this gate and never rewritten silently; the generated documents are
rebuilt; the spec is synced. Never the reverse.
This gate is for material the CLIENT sent. The other direction — what the code turns
out to say — has its own gate in /macstack-dev:reconcile, which enforces the same
three stops, the first being a statement the client has already answered.
Write every edit to history/ledger.jsonl, keyed by the id of the statement that
changed, with was and now. That row is what lets the next review package show the
client what moved since they last read it. An edit with no row is a defect.
Open the work. What was decided and needs building becomes a task in
history/TASKS.md, then goes to the tracker with /macstack-dev:plan sync.
Answers coming back from a review package
Those arrive through /macstack-dev:review --read, which writes them into the ledger.
Then come here: an answer that asks for a change is ordinary incoming material. Do not
apply a client's comment straight to a document — a comment is a request, and what it
costs to be wrong about it is the owner's call.
1---2name: intake-23description: 'Take in anything the client sends — a document, a returned review package, or a correction typed straight into this chat — and merge it through delta → ruling → apply Arguments: [file in inbox/ | what to change, in your own words | (empty = whatever is unprocessed)].'4metadata:5 source: https://skillmd.com/skills/agents-store/intake-26---78Use `macstack-dev:intake`. It owns the loop; this command only routes into it.910## Three ways material arrives, one loop11121. **A file in `inbox/`** — a PDF, a spec, a screenshot, a spreadsheet. Anything.132. **A stray file that appeared in `client/`** — anything there that is not one of the14 six documents is incoming material, not a document. Move it to `inbox/` first.153. **Text typed into this chat.** "убери геолокацию", "клиент сказал, что счета должны16 выходить 5-го". Write it to `inbox/<date>-<slug>.md` before doing anything else.1718The third is the one people forget to record. A correction that exists only in a chat19transcript has no source: six months later nobody can say who asked for it or when, and20the document says something nobody can trace. Write it down first, then work.2122## The loop, and none of it is optional23241. **Land it.** The file goes into `inbox/` under an ASCII name and gets an entry in the25 manifest. A source already committed in this repo is cited by path, never copied.26 Nothing in `inbox/` is ever edited afterwards.27282. **Read it.** Check size and first bytes before parsing — an iCloud placeholder reads29 as empty and yields a confidently wrong delta. `.xlsx` is refused: ask for a CSV30 beside it and write no log entry, so the file stays in the unprocessed set.31323. **Work out the delta.** Contradictions with what the documents already say, and33 additions. For each contradiction: what it touches, and what it costs if we choose34 wrong. A delta is a proposal, not an edit.35364. **Ask, then decide.** Every contradiction goes to the owner as a question with two37 real options: the recommendation you would defend, and "write it into38 `OPEN-QUESTIONS.md` and let the client answer". Never both silently.3940 Record the ruling in `history/DECISIONS.md` with its `cost-if-wrong` clause, written41 NOW, before the outcome is known — a retrospective cost clause is worthless.42435. **Apply in one direction: `client/` → `generated/` → `macstack.json`.** Client prose44 is edited through this gate and never rewritten silently; the generated documents are45 rebuilt; the spec is synced. Never the reverse.4647 This gate is for material the CLIENT sent. The other direction — what the code turns48 out to say — has its own gate in `/macstack-dev:reconcile`, which enforces the same49 three stops, the first being a statement the client has already answered.50516. **Write every edit to `history/ledger.jsonl`**, keyed by the id of the statement that52 changed, with `was` and `now`. That row is what lets the next review package show the53 client what moved since they last read it. An edit with no row is a defect.54557. **Open the work.** What was decided and needs building becomes a task in56 `history/TASKS.md`, then goes to the tracker with `/macstack-dev:plan sync`.5758## Answers coming back from a review package5960Those arrive through `/macstack-dev:review --read`, which writes them into the ledger.61Then come here: an answer that asks for a change is ordinary incoming material. Do not62apply a client's comment straight to a document — a comment is a request, and what it63costs to be wrong about it is the owner's call.