The handoff file
Long coding discussions often contain decisions that cannot be reconstructed from source code alone. Agentic Workspace turns those settled requirements into a self-contained file under .tasks/, ready for a fresh coding session to implement without needing the original conversation.
The handoff records the objective, relevant context, decisions, constraints, completion criteria, and verification requirements. Ordinary file-level choices stay with the implementation session.
Repository structure
Stable project knowledge stays in AGENTS.md. Active implementation contracts live in .tasks/. Reusable instructions live in .agents/skills/. These files belong to the project, so they can be reviewed with the code and remain available when the model, tool, or chat session changes.
A handoff is created after planning is settled, then implementation starts by naming that file. Several handoffs can coexist in the repository, with the active one chosen directly by the user.
Using it across coding tools
The core tooling uses POSIX shell and plain Markdown, so the handoffs are not tied to one agent harness. Installer checks preserve existing user configuration, repeated setup is idempotent, and the included commit workflow stages only explicit paths.
Agentic Workspace is the current successor to OpenCode Dispatcher. The earlier package explored larger orchestrated agent teams; this version reduced the idea to the part that remained useful across tools: a durable boundary between discussion and implementation.