agent-workspace

Define standardized .notes/.agents directory conventions for agent task context.

Updated Oct 28, 2025
One-click install
npx skills add https://github.com/SnowboardTechie/dotfiles --skill agent-workspace-snowboardtechie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-workspace
Source: https://github.com/SnowboardTechie/dotfiles/tree/main/dot-config/opencode/skills/agent-workspace
Command: npx skills add https://github.com/SnowboardTechie/dotfiles --skill agent-workspace-snowboardtechie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Agents across Muse, Sage, Archivist, and Pyre often juggle task context, drafts, and research caches in a cluttered workspace. This skill defines a standardized directory convention using .notes/.agents/ to separate long-term knowledge from ephemeral working state, reducing confusion and improving task hygiene.

Core Features & Use Cases

  • Establishes a consistent .notes/.agents/ structure for per-task context, progress, and drafts.
  • Supports project-local organization within multi-tool agent workflows (Muse, Sage, Archivist, Pyre) and facilitates lifecycle transitions.
  • Enables clear separation between permanent notes and ephemeral task work to improve findability and collaboration.

Quick Start

Create the trunk-wide .notes/.agents layout and begin storing per-task context, drafts, and research caches under Muse, Sage, Archivist, and Pyre workflows.

Frequently Asked Questions about agent-workspace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize ephemeral task context separately from permanent notes in a knowledge-management workflow?

To organize ephemeral task context separately from permanent notes, use a standardized .notes/.agents/ directory structure to isolate per-task progress and drafts from long-term knowledge, improving findability and task hygiene across multi-tool agent workflows.

How does an agent workspace structure handle lifecycle transitions across different workflows?

An agent workspace handles lifecycle transitions by applying a standardized .notes/.agents/ working-directory convention across Muse, Sage, Archivist, and Pyre workflows, specifying lifecycle patterns to support consistent progression of per-task context and drafts.

Do I need a specific Git setup to support task-context management in worktrees?

You do not need a specific Git setup; the task-context management conventions specify worktree resolution logic to support reliable collaboration in both trunk and worktree setups.

What is the best way to separate agent research caches from permanent knowledge in Obsidian?

The best way to separate agent research caches from permanent knowledge in Obsidian is implementing a .notes/.agents/ structure, which establishes a consistent layout for per-task context, progress, drafts, and research caches.

Why does my agent workspace get cluttered with drafts and task context across multiple workflows?

Your agent workspace gets cluttered because agents across Muse, Sage, Archivist, and Pyre juggle task context and drafts without a standardized directory convention to separate long-term knowledge from ephemeral working state.