materials-intake
Materials intake
A project collects materials from everywhere: a brief in the chat, a PDF from the client, a
screenshot, a chat export, a link to a cloud folder. Left as they came, they scatter over the
project root, docs/ and old messages. Three versions of the brief live side by side and nobody
knows which is current; a password sits in a committed file; the next agent builds on a draft as
if it were the agreed text, or cites our own retelling as the client's words. This skill keeps one
place for the materials and one inventory that says what is there and what it says, so any later
work starts from the current materials and knows how much weight each one carries.
Language
Everything the owner reads (the report, the inventory with its headings, the "what it is" part of file names) is written in the language the owner uses in the conversation. Codes, paths, commands and product names stay as they are. A project rule on language wins.
Where things go
The project's own rules on folders win. Without them: