packaging-low-context-worklisted

# Packaging Low-Context Work ## Core Rule Context is the expensive asset. The side that holds it (this session, the product owner's head) does what only context can do — define semantics, set boundaries, make judgment calls, write acceptance criteria. Everything else ships out as **work packages an executor can complete without understanding the whole project**. Never solve a context gap by making the executor "read everything first" — the long onboarding chain (讲解→理解→拆解→实现) is exactly the cost this skill deletes; solve it by packaging the context they need into the task itself. The economics corollary for AI executors: expensive-context sessions must not burn themselves on legwork. Reading long files end-to-end, sweeping directories, running investigations, collecting evidence — write a clear task (读什么、核什么、产出什么格式) and send it to a cheap executor; keep only judgment-critical excerpts for direct reading. ## What Stays vs. What Ships | Stays with context | Ships as packages | |---|---| | Object vocabulary, domain semantics, boundary judgments | Engineering skeletons, scaffolding, generic components | | Spec, contracts, acceptance criteria | Mock APIs, list/detail page frames, display components | | Decisions and trade-offs | Investigations with defined output format | | Receipt verification and integration | Evidence collection, file sweeps, mechanical transforms | Litmus test for shippability: **could a competent stranger complete this correctly using only the card?** No