Agent skill · writing content · aiskillstore
document-writing-coordination
This skill should be used when the user asks to "coordinate document writing", "manage doc writers", "create a design document with multiple writers", "orchestrate documentation", "delegate doc sections", "cos for documentation", "chief of staff for docs", or needs to break a large document into sections and delegate writing to multiple agents via VibeKanban.
Why this skill is useful
Provides a structured workflow for coordinating document writing that includes specific task templates and delegation rules not commonly found in general documentation practices.
What it needs
Requires vibekanban account access. About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Document Writing Coordination via VibeKanban Coordinate multi-section document creation by delegating to doc writer agents through VibeKanban task management. The coordinator (Chief of Staff) plans and monitors but never writes content directly. Core Principles Role Separation Role Responsibility Does NOT --------------------- ---------------------------------- ------------------ Coordinator (You) Outline, delegate, monitor, review Write content Doc Writers Write assigned sections Plan or coordinate Reviewer (You) Approve/reject, ensure consistency Implement fixes Workflow Overview Phase 1: Document Outline Creation Explore First Before creating the outline, thoroughly explore the codebase: Create Skeleton Document Write the document outline with: Table of contents with all sections HTML comments in each section describing scope "TODO: Section pending" placeholder for content Clear section numbering (1, 2, 3.1, 3.2, etc.) Example section scaffold: Phase 2: Task Creation Task Description Template Each VK task MUST include: Key Task Properties Title format: Doc: Section X.Y - Section Name Context: Succinct, self-contained for fresh agent Skill requirement: Explicit doc-coauthoring skill invocation Delegation rule: Word limit triggers for cascading VK tracking: Include task ID for status updates Creating Tasks via MCP Phase 3: Spawning Attempts VK Attempt Requirements To spawn agents via VK startworkspacesession: Critical: Requires repoid from VK project configuration. Use listrepos to retrieve, or ask user to configure repository in VK dashboard first. Fallback: Task Tool If VK repos not configured, use hybrid approach: 1. Update VK task status to inprogress 2. Spawn agent via Task tool with full context 3. Update VK to inreview when agent completes Phase 4: Monitoring Status Polling Poll VK every ~60 seconds during active work: Status Report Format Phase 5: Review Process When Task Reaches inreview 1. Read the updated document section 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/document-writing-coordination