Knowledge Work Plugins: give a work assistant a shared task file
Choose productivity, plain Markdown or a shared task service
Select a workflow according to ownership, collaboration and context needs rather than the size of the plugin collection.
What you will learn
- Use plain files when the task is simple
- Choose a shared service for shared guarantees
- Write a conditional decision
Before you start
- Basic command-line and configuration reading
- Ability to work in a disposable authorized environment
Design an independent parser preview that exposes unsupported Markdown and conflicting headings before a dashboard save.
Key takeaways
- Personal portability and team coordination are different requirements.
- A connector does not prove full synchronization.
- Adoption should follow an observed task.
Use plain files when the task is simple
Plain Markdown is enough when you only need a personal checklist and are comfortable editing it directly. Adding a host assistant becomes useful when interpreting workplace shorthand or extracting proposed commitments is the actual burden.
The productivity plugin offers a file-backed board and a documented memory convention. Evaluate whether those conventions reduce your work on a real, approved sample. Installing every role plugin is unnecessary for a narrow personal task workflow.
Choose a shared service for shared guarantees
A team that needs per-user permissions, durable history or coordinated editing should evaluate its existing project-management service as the source of truth. The inspected task file and board do not establish those guarantees.
A connector can complement that service, but verify creation, update and identity mapping for the chosen integration. Do not claim universal bidirectional synchronization from the README’s broad workflow description.
Write a conditional decision
Choose a small pilot when local portability and editable context matter more than multi-user coordination. Choose direct service use when the main requirement is accountable team state. Record the decision using your observed task accuracy and correction burden.
A positive trial remains limited to the host version, plugin revision and connectors tested. Leave deployment undecided if permissions or data handling are unresolved. Popularity and the number of role folders do not answer those questions.
Decision guide
| Criterion | Option A | Option B |
|---|---|---|
| Best when | You need predictable behavior and easy auditing | You need adaptive optimization and have reliable telemetry |
| Main risk | May leave performance on the table | Can become difficult to explain or debug |
Implementation steps
- 1
Name whether the source of truth is a personal file or shared service.
- 2
Compare one approved task across candidate workflows.
- 3
Record the tested boundaries and remaining conditions.
Copy-ready example
{
"selectionRecord": true,
"sourceOfTruth": "choose file or shared service",
"needsConcurrentEditing": null,
"testedConnector": null,
"decision": "pending observed trial"
}Frequently asked questions
Must I replace my existing task manager?
No. Keep it when its collaboration guarantees are important and test only the additional assistant workflow.
Should all plugins be installed together?
A narrowly scoped trial is easier to inspect and authorize.
Sources
- Knowledge Work Plugins / README.mdSource checked 2026-09-18
- Knowledge Work Plugins / productivity/README.mdSource checked 2026-09-18
- Knowledge Work Plugins / productivity/skills/task-management/SKILL.mdSource checked 2026-09-18
- Knowledge Work Plugins / productivity/.mcp.jsonSource checked 2026-09-18