Standing instructions
Use AGENTS.md for project conventions, relevant checks, and guidance about how to work in the repository. Support and instruction precedence depend on the coding agent.
Day Shift and AGENTS.md
Keep repository conventions and task evidence connected.
AGENTS.md gives compatible coding agents standing repository instructions. Day Shift adds records for a particular change: its objective, allowed paths, validation results, implementation summary, and continuation state. The two can work together.
Different questions
What should the agent know, and what happened on this task?
The current work agreement
Use a task record to name the requested result, its allowed scope, acceptance criteria, and check results. A later session can inspect the current state without reconstructing a conversation.
A concrete example
A test command alone does not record its result.
Your standing instructions might require the game-rule tests before review. A specific game task then records which behaviors must change, the files in scope, the tests actually executed, and the remaining review concerns. In Day Shift, that evidence stays connected to the task.
Deciding what to add
Let the review and handoff needs set the scope.
AGENTS.md and existing tools may suffice
A small change can have clear requirements in an issue, a complete pull request, and reliable CI. Extra task artifacts may add more work than they save.
Evaluate Day Shift when continuity is costly
Consider it when work spans sessions, tools, or contributors and the next person needs to recover the task boundary, failed attempts, validation evidence, and remaining work.
Both instructions and task records depend on the workflow being followed. Day Shift does not sandbox arbitrary external agents, guarantee instruction compliance, or replace CI and human review.
About the creator
Created and maintained by Tianna McCoy. Published by TNSDS. Tianna develops Day Shift and maintains its repository workflow and product evidence.