← ClaudeAtlas

workforce-setuplisted

Build the Workforce OS structure in the user's own Notion — one task database, Domains, goals, knowledge, logs and an agent control room. Use when the user wants to set up Workforce OS, build a second brain for their work in Notion, or rebuild the structure. Requires Notion access.
aniklavida/workforce-os · ★ 1 · AI & Automation · score 74
Install: claude install-skill aniklavida/workforce-os
# Workforce OS — Setup Build the structure in the user's **own** Notion. Nothing is copied from anyone else's workspace. ## Before you start Confirm you have Notion write access. If not, stop and tell the user how to connect it — do not build a partial structure. Ask where it should live: a new top-level page, or inside an existing one. ## Ask first — five short questions, then build Do not build a generic workspace and hand it over. Ask these, and build from the answers: 1. **What are the main areas of your life right now?** (Their Domains — expect three to eight. Their words, not yours: "Australia", "my company", "day job".) 2. **What should your assistant call you?** 3. **Where do you want the daily message — right here in this chat, or somewhere else your agent already delivers messages?** Workforce OS has no chat adapter of its own; delivery uses whatever surface the connecting agent already has. 4. **What is the one thing you are actually working toward?** (Becomes their goals page. One line is enough.) 5. **Which agents do you have, or want?** (If they don't know, create only the Assistant.) If they give short or vague answers, that is expected — **write them up properly yourself.** Never make them fill a form. ## What to create ### The task database — the spine One database. Everything routes through it. | Property | Type | Notes | |---|---|---| | Task | Title | | | Status | Status | `Planned` · `In progress` · `Done` — shared by user and agents | | Assign