manage-documents
Manage Documents
Create and manage standalone workspace documents. These are distinct from initiative descriptions.
Do not use this skill for initiative description edits. Use patch-document with taskId via task-management for that. This skill manages documents by documentId.
Document model
Types: Requirement — specs, requirements, design docs | Task — task-scoped documents
Statuses: Draft (default) | Completed
Tool selection
| Goal | Tool |
|---|---|
| Create a new document | create-document |
| Fetch a document by ID | get-document |
| Replace document fields (title, content, status) | update-document |
| Search or filter document metadata | find-documents |
| Delete a document | delete-document |
update-document replaces whole fields by documentId. It is not for initiative descriptions — use patch-document with taskId for those.
Rules
- If
workspaceIdis unknown or the user has multiple workspaces, calllist-workspacesfirst. find-documentsis a discovery/list tool. It returns document metadata plusexcerpt, not fullcontent.- Use
find-documentsfor IDs, titles, statuses, task links, and excerpts. Useget-documentwith the selecteddocumentIdwhenever full document content is needed. get-document,update-document, anddelete-documentall requiredocumentId. Callfind-documentsfirst if you only have a title or filter criteria, then callget-documentbefore reading or summarizing the full body.- Do not use
update-documentfor initiative description edits. Usepatch-documentwithtaskIdinstead. - Do not call
delete-documentwithout explicit user confirmation — deletion is not reversible.
Create a document
create-document({
"workspaceId": "<workspaceId>",
"title": "Auth Flow Requirements",
"content": "## Overview\n\nFull markdown content here.",
"type": "Requirement",
"status": "Draft"
})
type is required. Allowed values: Requirement, Task.
Get a document
get-document({
"workspaceId": "<workspaceId>",
"documentId": "<documentId>"
})
Update a document
Replaces any provided fields. Omit fields you don't want to change.
update-document({
"workspaceId": "<workspaceId>",
"documentId": "<documentId>",
"title": "Updated title",
"status": "Completed"
})
Find documents
Filter by type, status, task link, or creator. The result is metadata plus excerpt only:
find-documents({
"workspaceId": "<workspaceId>",
"types": ["Requirement"],
"statuses": ["Draft"],
"taskId": "<taskId>",
"limit": 20
})
Use query for name/title search:
find-documents({
"workspaceId": "<workspaceId>",
"query": "auth spec"
})
If the user needs the document body after choosing a result, call:
get-document({
"workspaceId": "<workspaceId>",
"documentId": "<documentId>"
})
Delete a document
Only call after the user has explicitly confirmed.
delete-document({
"workspaceId": "<workspaceId>",
"documentId": "<documentId>"
})
More from onehorizonai/skills
work-summarizer
Turn One Horizon activity into a clean update for a manager, team, or stakeholder. Use when asked to "summarize my work", "write a status report", "create a weekly summary", or "brief my manager". Includes initiatives and blockers when provided. Requires One Horizon MCP.
24bug-triage-prep
Turn open bugs into triage notes a team can actually use. Use when asked "prepare bug triage", "summarize open bugs", or "prioritize defects for review". Requires One Horizon MCP.
23get-task-details
Fetch the full details for one known One Horizon task when the task ID is already available and the user needs exact task context. Prefer task-management when details are only one step in a larger operational request. Requires One Horizon MCP.
23initiative-summary
Turn initiative data into a clear status update. Use when asked "summarize these initiatives", "give me initiative status", or "prepare initiative update notes". Requires One Horizon MCP.
22handoff-notes
Turn current work into handoff notes someone else can pick up without guessing. Use when asked to "write handoff notes", "prepare transition docs", or "document my current ownership". Requires One Horizon MCP.
22list-taxonomy
Look up One Horizon taxonomy labels when the user explicitly asks for label IDs or available goals, products, releases, or components. Prefer task-management when taxonomy lookup is only one step in a larger operational request. Requires One Horizon MCP.
22