Back to Skills

orchestrate

Priotize

4starsUpdated 3/25/2026

Security Assessment

Safe(100/100)
Security Score100/100

About orchestrate

The 'orchestrate' skill is designed to streamline and prioritize the process of writing and managing documentation chapters within a repository. It addresses the challenge of determining which chapters should be written first and ensures that effort is focused efficiently, avoiding duplication or unnecessary work. By following a structured approach, this skill helps users maintain a clear overview of the documentation project, ensuring that all topics are addressed systematically from specific subtopics to broader chapters.

Key features of 'orchestrate' include the ability to consult a 'priorities.md' file to identify high-priority chapters, guidance on working through chapters alphabetically when no priorities are defined, and rules for skipping directories marked as 'skip'. It also provides a methodology for identifying chapters that require work by checking the root ReadMe.md outline and verifying the existence and content of corresponding ReadMe.md files. Additionally, it enforces a publishing step where completed chapters are linked in the main outline, ensuring that the documentation structure remains up to date.

This skill is particularly useful for technical writers, developers, and project managers involved in large documentation projects or knowledge bases with multiple interrelated topics. Use cases include managing documentation for software projects, educational content, or any structured repository where maintaining completeness and order is critical. By leveraging 'orchestrate', users can prioritize work effectively, reduce redundancy, and maintain a coherent documentation workflow.

FAQ

How do I determine which chapters to work on first?

Check the 'priorities.md' file in the root directory for chapters listed under 'Prioritize'. If none are listed, work through chapters alphabetically by directory while skipping any directories listed under 'skip'.

What is the recommended order for writing chapters?

Work from leaf directories upward, meaning subtopics should be completed before writing broader chapters that encompass them.

How do I identify chapters that need content?

Use the root ReadMe.md outline to find items that are plain text without links. Then verify if the corresponding directory's ReadMe.md exists and contains actual content. Only write new content for empty or missing chapters.

Do I need to update the main outline after finishing a chapter?

Yes. Once a chapter is complete, convert its name in the root ReadMe.md outline into a hyperlink pointing to the chapter's ReadMe.md.

Can this skill be used for any repository structure?

It is designed for repositories with a hierarchical directory structure and a root ReadMe.md outline. Repositories lacking these conventions may require adaptation.

Install orchestrate

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill