Two Plugins, One System

Chapter 39 uses two plugins working together. The first — Anthropic's official Productivity plugin — handles the basic infrastructure: task tracking, memory files, and a visual dashboard. The second — the Agentic Office plugin — adds the professional intelligence layer that transforms basic tracking into executive-grade workplace awareness.

They are not competing tools. They are the storage layer and the intelligence layer of the same system. You need both.

This lesson installs both plugins, runs the initialisation commands, and verifies that the full infrastructure is in place before Lesson 3 begins the real work.

The Division of Responsibility

Before installing anything, it is worth being precise about what each plugin does — and what it deliberately does not do.

Concern	Official productivity	Custom agentic-office
Task list CRUD	/productivity:start, /productivity:update	—
Memory hot cache	CLAUDE.md (working session memory)	—
Memory deep storage	memory/ directory	—
Visual dashboard	dashboard.html (board view)	—
Four-layer professional memory	—	work.local.md
Task intelligence	—	Brain dump → P1/P2/P3 sort
Delegation quality	—	Delegation records + handoff comms
Morning digest	—	Daily briefing assembly
Meeting support	—	Three-phase model (before/during/after)
Executive dashboard	—	RAG status across all projects
Cross-domain context	—	Context loading for other domain agents
Persistent agents	—	4 agents (Chief of Staff, Memory Keeper, Meeting Intelligence, Work Tracker)

The boundary is precise by design. The official plugin responds to natural language triggers like "add a task," "remember this," "who is," and "start." The custom plugin responds to triggers like "brain dump," "prioritise," "delegate," "daily digest," and "workplace memory." There is no overlap — the two plugins never compete for the same input.

Why Two Plugins?

The official Productivity plugin is Anthropic's supported infrastructure layer — it handles the file system, the dashboard, and basic task and memory operations. It is well-maintained and reliable. The custom Agentic Office plugin builds the professional intelligence layer on top of that infrastructure — adding the context-aware reasoning, delegation quality, meeting intelligence, and agent orchestration that transform basic tracking into a Digital Chief of Staff. Separating infrastructure from intelligence means each plugin stays focused, maintainable, and upgradeable independently.

Install the Official Productivity Plugin

In Cowork:

1. Open the Cowork sidebar
2. Navigate to Customize → Browse plugins
3. Find Productivity in the plugin list
4. Click Install

In Claude Code (alternative):

claude plugins add knowledge-work-plugins/productivity

Once installed, the plugin makes four skills available: task-management, memory-management, and the /productivity:start and /productivity:update commands.

Run /productivity:start

The first command initialises your task and memory infrastructure. Run it now:

/productivity:start

Claude will create four things:

Created	Purpose
TASKS.md	The task list — Claude reads and writes to this file; add tasks naturally and the skill keeps it structured
CLAUDE.md	The hot cache — Claude's working session memory, loaded at the start of every conversation
memory/	The deep storage directory — longer-form memory files that persist between sessions
dashboard.html	A local HTML file providing a board view of your tasks and a live view of Claude's workplace knowledge

After running /productivity:start, you will be prompted for some initial context: your role, your team, your current priorities. This seeds the initial CLAUDE.md with your working memory. Answer these questions — they will save you time in later lessons.

Expected output (abbreviated):

✓ Created TASKS.md
✓ Created CLAUDE.md
✓ Created memory/ directory
✓ Created dashboard.html — open in your browser to see your workspace

Tell me about your work context to get started:
What is your role and organisation?
Who are your key team members?
What are your current top priorities?

Open dashboard.html in your browser. At this point it will be sparse — a few placeholder sections for tasks and memory. By Lesson 10, it will show a fully populated executive dashboard. For now, it confirms that the official plugin infrastructure is working.

Install the Agentic Office Plugin

The Agentic Office plugin is hosted in the Panaversity business plugins marketplace.

In Cowork:

1. Open the Cowork sidebar
2. Navigate to Customize → Browse plugins → Personal
3. Click the + button
4. Select Add marketplace from GitHub
5. Enter: https://github.com/panaversity/agentfactory-business-plugins
6. Find Agentic Office in the plugin list
7. Click Install

Once installed, nine skills become available: workplace-context, workplace-search, task-intelligence, delegation, digest, meeting-intelligence, progress-tracker, context-loader, and executive-brief. Four agents also become available: chief-of-staff, memory-keeper, meeting-intelligence-agent, and work-tracker.

Run /agentic-office:setup

The setup command creates your workplace memory template:

/agentic-office:setup

This creates work.local.md from the plugin's template — an empty four-layer configuration file structured for your professional context.

The four layers in the template:

## Layer 1: Personal
  name, role, working_style, decision_making, current_focus,
  working_hours, primary_tools, communication_preference

## Layer 2: Team (People)
  people:
    - name, role, reports_to, communication, current_focus,
      priorities, note, sensitivity

## Layer 3: Projects
  projects:
    - name, codename, status, priority, owner, description,
      current_milestone, next_milestone, at_risk, decisions,
      key_contacts

## Layer 4: Organisational Memory
  terminology: { "Term": "Definition" }
  meeting_rhythm: [ recurring meetings ]
  culture: { values, decision_making, communication, unwritten_rules }

This file is empty now. Lessons 3, 4, and 5 will populate it layer by layer. By the end of Lesson 5, work.local.md will contain everything Claude needs to operate as a knowledgeable colleague — your working style, your key people, your active projects, your organisational terminology and culture.

Keep This File

work.local.md is your primary configuration asset for the rest of the chapter. Every lesson from here builds on it. Do not start a new file or delete this one.

How the Two Plugins Work Together

The official plugin's CLAUDE.md and memory/ files hold the raw working data. The custom plugin's work.local.md holds the structured, four-layer professional context.

Here is how they interact in practice:

A task is added → Official plugin's task-management skill writes it to TASKS.md. The task is stored and queryable.

A brain dump is processed → Custom plugin's task-intelligence skill reads the brain dump, pulls project context from work.local.md (Layer 3), and produces a P1/P2/P3 classified list. The classified tasks are written back to TASKS.md via the official plugin.

A morning digest is assembled → Custom plugin's digest skill reads today's tasks from TASKS.md (via official plugin), pulls the day's meetings from calendar context, reads current priorities from work.local.md Layer 1, and assembles a briefing that references the real people, projects, and priorities from Layer 2, 3, and 4.

The official plugin maintains the files. The custom plugin makes those files intelligent.

Verify Both Plugins Are Active

With both plugins installed and initialised, run a quick verification:

/productivity:update

You should see the official plugin triage any stale tasks and check memory for gaps. If you connected external tools (Slack, email, calendar) during setup, it will scan those sources.

Then:

/agentic-office:workplace-context
> What do you currently know about my organisation?

At this point, the response will be limited — work.local.md is empty. The skill will acknowledge this and offer to help you begin filling it in. This is the correct behaviour. It confirms the plugin is active and reading from work.local.md.

Both commands responding is your verification that the system is ready.

Try With AI

Use these prompts in Cowork or your preferred AI assistant.

Reproduce: Verify your plugin installation with these two commands and observe what each plugin knows.

/productivity:start

After running, confirm: TASKS.md, CLAUDE.md, memory/, and dashboard.html all exist. Then:

/agentic-office:setup

Confirm: work.local.md exists and contains the four-layer template structure.

What you are learning: The installation and initialisation steps are a one-time investment. After this lesson, both plugins run in every subsequent Cowork session — the infrastructure persists, the memory files persist, and every lesson from here builds on this foundation.

Adapt: If you already have a task list in another tool, test what the official plugin can see.

/productivity:update --comprehensive

If you have connected Slack, email, calendar, or a project management tool (Asana, Linear, Notion, Monday, ClickUp), the comprehensive update will scan for missed action items and suggest new memory entries. If you have not connected external tools, the update will work from what you have shared in the session.

What you are learning: The official plugin's MCP connectors are optional but powerful — they reduce the manual work of keeping TASKS.md current. Even without connectors, the plugin works well when you add tasks naturally in conversation. The connectors automate what the plugin can already do manually.

Apply: Open dashboard.html in your browser and observe the empty dashboard structure.

Open the dashboard.html file that /productivity:start created.
What sections does the empty dashboard have?
What data would need to exist for each section to be useful?
Which sections will be populated after Lesson 3?
Which sections require Lessons 10-14 to complete?

Ask Claude this question about the dashboard structure. The answer will give you a preview of the chapter's arc — the empty dashboard is a map of what you are building.

What you are learning: The dashboard starts empty because the memory starts empty. As you fill work.local.md in Lessons 3-5 and deploy skills in Lessons 6-11, the dashboard fills in. By Lesson 10, what is currently an empty template will be a real-time view of your professional context. The empty dashboard is motivating, not discouraging — it shows exactly what the chapter is building.

Flashcards Study Aid

---

Continue to Lesson 3: Workplace Memory Architecture →