pragman-workspacelisted

# Pragman Workspace Keep reusable context useful without blending organizations or exposing source content. A project has one primary workspace; explicitly ordered additional workspaces are advisory and never silently override it. ## Use this skill when - You work across clients, companies, ventures, or projects and need durable context without cross-boundary leakage. - A project needs one explicit primary workspace plus deliberately ordered advisory context. - Context sources, privacy, ownership, links, or conflicts should be validated before an agent relies on them. ## Acceleration payoff It prevents repeated context dumps and wrong-tenant assumptions by making reusable context indexed, layered, attributable, and reversible. ## Workflow 1. Identify the context boundary: personal, workspace, or linked project. Ask only for missing answers that change ownership, primary workspace, additional-workspace order, sensitivity, or canonical sources. 2. Inventory context by reference. Record a source ID, kind, locator, description, and sensitivity (`public < internal < confidential < restricted`). Do not copy a private corpus into configuration, chat, evals, or public artifacts. Never store credentials. 3. Choose exactly one primary workspace for a project. Attach additional workspaces only when the task needs them, in deliberate order. Treat their facts and provider rules as candidates; surface conflicts with source aliases and request a choice. 4. Locate `pragman` through th