No description
Find a file
2026-04-11 08:06:33 +08:00
.obsidian feat: extract obsidian workspace template 2026-04-11 04:30:39 +08:00
00-home feat: extract obsidian workspace template 2026-04-11 04:30:39 +08:00
01-inbox feat: extract obsidian workspace template 2026-04-11 04:30:39 +08:00
10-research feat: extract obsidian workspace template 2026-04-11 04:30:39 +08:00
20-synthesis feat: extract obsidian workspace template 2026-04-11 04:30:39 +08:00
30-datasets feat: extract obsidian workspace template 2026-04-11 04:30:39 +08:00
40-experiments feat: extract obsidian workspace template 2026-04-11 04:30:39 +08:00
50-evaluation feat: extract obsidian workspace template 2026-04-11 04:30:39 +08:00
60-assets feat: extract obsidian workspace template 2026-04-11 04:30:39 +08:00
80-deliverables feat: extract obsidian workspace template 2026-04-11 04:30:39 +08:00
90-ops feat: extract obsidian workspace template 2026-04-11 04:30:39 +08:00
docs add skill doc for Agents & human 2026-04-11 08:06:33 +08:00
Projects & Tasks feat: extract obsidian workspace template 2026-04-11 04:30:39 +08:00
res feat: extract obsidian workspace template 2026-04-11 04:30:39 +08:00
看板 feat: extract obsidian workspace template 2026-04-11 04:30:39 +08:00
AGENTS.md add skill doc for Agents & human 2026-04-11 08:06:33 +08:00
README.md add skill doc for Agents & human 2026-04-11 08:06:33 +08:00

Workspace Template

This repository contains a domain-neutral Obsidian workspace template for research, synthesis, execution, and delivery work. Use it as a starter vault for a new subject area without inheriting any project-specific subject matter.

Two Layers

The template is organized into two connected layers:

  • Content layer: 00-home/, 01-inbox/, 10-research/, 20-synthesis/, 30-datasets/, 40-experiments/, 50-evaluation/, 60-assets/, 80-deliverables/
  • Management layer: res/, Projects & Tasks/, 看板/, and 90-ops/

Use the content layer for subject-matter notes and source material. Use the management layer for project tracking, task tracking, issue tracking, file classes, templates, and board views so operational metadata stays out of core notes.

Required Plugins And Capabilities

This template assumes four Obsidian capabilities are available:

  • Templater for folder templates and automatic note creation
  • Metadata Menu for file-class driven metadata editing
  • Dataview for indexed queries and dashboard-style views
  • Bases for the board files under 看板/

If you are setting up a fresh vault, install and enable all four before trying to use the management system.

Plugin Configuration

  • Templater

    • Set Template folder location to res/Templates
    • Enable Trigger Templater on new file creation
    • Add folder template rules for:
      • Projects & Tasks/Projects -> Template-Project
      • Projects & Tasks/Tasks -> Template-Task
      • Projects & Tasks/Issues -> Template-Issue
  • Metadata Menu

    • Set class Files Path to res/FileClasses/
    • Open each file-class note and define its fields in the order written in the note body
    • Use File or MultiFile field types for Project, ParentTask, RelatedNotes, Datasets, Experiments, and Deliverables
    • Replace the placeholder entries in res/Configs/People.md with the real collaborators, then point the People, Assignee, and Reporter pickers at res/Configs/People.md
  • Dataview

    • Enable JavaScript queries because the template includes a dataviewjs block
    • Confirm Projects & Tasks/ and 看板/ are indexed and not excluded
  • Bases

    • Open each .base file once in Obsidian so the app can render and validate the board view
    • If a board shows no results, check that the note frontmatter field names match the file-class names exactly

First-Time Setup

  1. Copy this template vault into a new workspace folder for your domain.
  2. Open the copied vault in Obsidian.
  3. Install and enable Templater, Metadata Menu, Dataview, and Bases.
  4. Apply the plugin configuration above.
  5. Open Project Task Management Guide and New Workspace Setup for the companion rollout notes.
  6. Fill in People with the current collaborators.
  7. Open the board files under 看板/ once so Obsidian can render them.
  8. Start from the hub notes listed below to make sure the workspace entry points are easy to reach on day one.

Using The Template For A New Domain

When you start a new domain:

  • keep the folder structure intact
  • rename or add notes inside the content layer to match the new domain
  • capture raw material in 01-inbox/Capture.md
  • develop synthesis in 20-synthesis/
  • publish outward-facing outputs from 80-deliverables/
  • manage execution through Projects & Tasks/ and the board files under 看板/

The template is designed so you can later use a kickstart prompt to shape the domain-specific note set without rebuilding the workspace architecture.

If you are using an agent or a skill-driven workflow with this template, start here:

The short version is:

  • use brainstorming before structural or workflow changes
  • use writing-plans before larger multi-step implementation work
  • use subagent-driven-development when executing a written plan
  • use verification-before-completion before claiming success, committing, or pushing
  • use obsidian-markdown, obsidian-bases, and obsidian-cli for Obsidian-specific work

Key Entry Points

These are the main files a repo reader can open first:

Obsidian Context

The vault still uses Obsidian-native structures such as file classes, wikilinks, .base board files, and templated note creation. The README stays repository-friendly, but the companion notes under 90-ops/ provide the deeper Obsidian-specific rollout details.