The issue says what to build. A later discussion changes an important constraint. Bring the issue, decision and relevant repository context together before asking the coding agent to make the change.
“What changed in the requirement, and which behaviour must stay the same?”
02 /Research & business writing
Write from evidence your team can stand behind.
A brief may need internal decisions, meeting notes and external research. Keep those sources distinct, flag gaps and make it possible to check the claims in the final draft.
“What can we say about this project, and which sources support it?”
03 /Client & account work
Keep the latest commitment with the account.
A customer commitment may be split between an email, a meeting and a CRM note. Prepare the authorised context before drafting an update, with current commitments separated from earlier proposals.
“What have we agreed to deliver, and what is still open?”
04 /Support & commerce
Check which policy the answer relies on.
The policy has changed, but an old instruction remains in a thread or saved context. Compare the sources, review the correction and test the answer against the current policy before using the change more widely.
“Does this answer follow the policy that applies to this case?”
05 /Company continuity
Preserve why the team made the decision.
A new teammate or agent needs the reasoning behind the work, not only the final document. Link the decision to its owner, evidence, effective date and any later replacement.
“Which decision is current, and what was the reason behind it?”
Your next workflow
Bring us a task your team keeps repeating.
Show us the sources you rely on and how you judge a useful result. Put company memory and cost intelligence to work in your workflow.