office-structure

Organize the ~/office workspace with a directory taxonomy and Medallion architecture.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/HugoAlmeidaMoreira/zeus-agent --skill office-structure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: office-structure
Source: https://github.com/HugoAlmeidaMoreira/zeus-agent/tree/main/skills/office-structure
Command: npx skills add https://github.com/HugoAlmeidaMoreira/zeus-agent --skill office-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Office Structure Skill helps you understand the purpose and organization of the ~/office directory, enabling efficient navigation and consistent workflows across your personal knowledge base.

Core Features & Use Cases

  • Understand directory layout: journal/, backlog/, scripts/, devops/adr/, wsl/, inbox/.
  • Apply the Medallion Architecture for documents and tasks: landing, processed, transformed, outputs, workbench, archive.
  • Follow the Workbench Iteration & Archiving Workflow to preserve history non-destructively and consolidate iterations.

Quick Start

Review the ~/office directory structure and apply the archiving guidelines to a current project.

Frequently Asked Questions about office-structure

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

FAQPage Schema
What is the Medallion architecture for personal knowledge management?

The Medallion architecture structures documents and tasks into landing, processed, transformed, outputs, workbench, and archive layers. This enforces consistent workflow stages across your personal knowledge base.

How do I organize a Second Brain workspace directory structure?

Organize a Second Brain workspace by applying a directory taxonomy with folders like journal, backlog, scripts, devops/adr, wsl, and inbox. This taxonomy supports consistent navigation and knowledge governance across projects.

How do I archive project iterations non-destructively in a knowledge base?

Archive project iterations non-destructively by following the Workbench Iteration and Archiving Workflow. This workflow preserves history while consolidating iterations, moving completed work into the archive layer without data loss.

Does this directory taxonomy work for both personal knowledge and project workflows?

Yes, the directory taxonomy applies to both personal knowledge management and project workflows. It enforces consistent workspace structure, archiving guidelines, and governance across your ~/office directory.

What is the best way to map workspace workflows for consistent archiving?

The best way to map workspace workflows is applying a Medallion architecture with explicit archival guidelines. This ensures documents flow logically from landing to archive while preserving iteration history non-destructively.