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.
Coordinates multi-section document creation by delegating to doc writer agents through VibeKanban task management.
/plugin marketplace add clementwalter/rookie-marketplace/plugin install chief-of-staff@rookie-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
examples/design-doc-outline.mdexamples/section-task.mdreferences/review-checklist.mdreferences/task-templates.mdCoordinate 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.
| 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 |
1. Explore codebase → Understand scope
2. Create outline → Scaffold document structure
3. Create VK tasks → One per section
4. Spawn attempts → Launch doc writer agents
5. Monitor → Poll status periodically
6. Review → Approve or send back
7. Consistency check → After each merge
8. Complete → When no pending tasks remain
Before creating the outline, thoroughly explore the codebase:
Use Task tool with subagent_type=Explore to understand:
- Project structure and components
- Key technologies and patterns
- Existing documentation
- Recent changes and evolution
Write the document outline with:
Example section scaffold:
## 3.1 Component Name
<!--
SCOPE: What this section covers
- Key topics to address
- Source files to reference
- Diagrams to include
-->
TODO: Section pending
Each VK task MUST include:
## Task
Write Section X "Section Title" of `/path/to/document.md`.
## Required Skill
**MUST use doc writer skill** - Invoke `document-skills:doc-coauthoring` skill before writing.
## Context
[2-3 sentences of essential background for a fresh agent]
## Scope
- [Bullet list of what to cover]
- [Specific topics]
- [Diagrams to create]
## Source Files to Reference
- `path/to/relevant/file.ts`
- `path/to/another/file.md`
## Output
Edit `/path/to/document.md` replacing "TODO: Section pending" under Section X with complete content.
## Delegation Rule
If this section exceeds [N] words, scaffold subsections and create new VK tasks using vibe_kanban MCP tools (project_id: [UUID]):
- X.1 Subsection A
- X.2 Subsection B
## VK Task ID: [task-uuid]
When done, mark task as "inreview" in VK.
Doc: Section X.Y - Section Namemcp__vibe_kanban__create_task:
project_id: [project-uuid]
title: "Doc: Section 1 - Executive Summary"
description: [full template above]
To spawn agents via VK start_workspace_session:
mcp__vibe_kanban__start_workspace_session:
task_id: [task-uuid]
executor: CLAUDE_CODE
repos: [{repo_id: [repo-uuid], base_branch: main}]
Critical: Requires repo_id from VK project configuration. Use list_repos to retrieve, or ask user to configure repository in VK dashboard first.
If VK repos not configured, use hybrid approach:
inprogressinreview when agent completesmcp__vibe_kanban__update_task:
task_id: [uuid]
status: inprogress
Task tool:
subagent_type: general-purpose
prompt: [task description]
run_in_background: true
Poll VK every ~60 seconds during active work:
mcp__vibe_kanban__list_tasks:
project_id: [uuid]
status: inprogress # or inreview, todo
## Backlog Status
| Section | Task ID | Status | Notes |
| --------------- | ------- | ---------- | ---------------- |
| 1. Exec Summary | 88e5... | inreview | Ready for review |
| 2. Repo Org | f722... | inprogress | Writing |
| 3.1 Benchmark | 371c... | todo | Blocked |
**Active**: 5/15 | **In Review**: 2 | **Done**: 8
inreviewdone, check doc consistencyinprogress with feedback taskCreate follow-up task or update description:
## Revision Required
**Issues Found:**
- [ ] Missing architecture diagram
- [ ] Incorrect API reference in line 45
- [ ] Inconsistent terminology (use "coprocessor" not "processor")
**Action**: Fix issues and return to inreview.
After each section merges to done:
Task is complete when:
done status| Tool | Purpose |
|---|---|
list_projects | Get project UUIDs |
list_tasks | View all tasks with status |
create_task | Create new section task |
update_task | Change status/description |
get_task | Get task details |
start_workspace_session | Launch agent (needs repo_id) |
list_repos | Get repository UUID |
todo → inprogress → inreview → done
↘ (rejected) → inprogress
references/task-templates.md - Full task description templatesreferences/review-checklist.md - Detailed review criteriaexamples/design-doc-outline.md - Sample document skeletonexamples/section-task.md - Complete task description exampleExpert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.