← ClaudeAtlas

work-brieflisted

Read-only scan of the code one task touches, written as a brief an orchestrator or agent plans from: scope, contracts, confirmed and suspected weak points, decisions with a recommendation, checks, done conditions.
viettdann/arclight-kit · ★ 0 · DevOps & Infrastructure · score 65
Install: claude install-skill viettdann/arclight-kit
# Work brief Map the code one task will touch and hand over the best way to do the task that the evidence supports: where the work goes, what changes and to what, what must not break, and which spots look weak. Every question left open costs the reader a round of work, and every current behavior kept without a reason is an improvement lost, so the brief settles what the evidence settles and leaves a person only the choices that are theirs. The brief is the whole product. The receiving agent has none of this session's context, so the brief carries the objective, the boundaries, and the output it expects; vague briefs make agents misread the task or redo each other's work. ## 1. Pin the task - Restate the task as one sentence of what has to change and why: `Cut the order export endpoint's memory use on 100k rows; output file stays identical`. - Take the target from the request, then the repo: the endpoint, job, module, or package it names. Find entry points, callers, and config yourself; don't ask for paths that are in the repo. - The code keeps running where it runs today (App Service, Functions, container, job host) unless the task names a new host. A target name that hints at the current host (`X.Hono` next to an Azure Functions project) means the same host with the new framework: on Functions, the framework is served through the Functions HTTP trigger (an adapter), not a server listening on its own port. When the request truly leaves the host open, that is the first Deci