orchestrate
Priotize
When & Why to Use This Skill
This Claude skill orchestrates the technical writing process by intelligently prioritizing chapter creation and managing documentation workflows. It analyzes repository structures, identifies missing or placeholder content via README outlines, and ensures a systematic 'leaf-to-root' writing approach. By automating task selection and link publishing, it streamlines the maintenance of complex documentation projects and ensures content consistency.
Use Cases
- Documentation Gap Analysis: Automatically scan a project's root README to find unlinked chapters and verify if their corresponding files contain actual content or just placeholders.
- Structured Content Prioritization: Use a 'priorities.md' file or directory hierarchy to determine the most logical order for writing, focusing on child topics before parent summaries.
- Automated Publishing Workflow: Convert plain-text outline entries into active hyperlinks immediately after a chapter is written, maintaining an up-to-date table of contents.
- Efficient Repository Management: Prevent redundant work by checking for existing content across multiple directories before initiating new writing tasks.
| name | orchestrate |
|---|---|
| description | Priotize |
| license | Apache |
Prioritize
There are hundreds of potential chapters to write. To decide where to begin, first check the 'priorities.md' file in the root directory of the repository. If there are line items under 'Prioritize', start working through the chapters listed there. Otherwise, start working via alphabetical order by directory. Note, if there are line items under 'skip', skip those directories.
Generally, we want to work from the leaf directories upward. So for a given topic that has child topics, if all of the child topics are written, it is time to write the chapter for that general topic.
Finding Chapters That Need Work
Use the root ReadMe.md outline to identify chapters needing work. Items without links (plain text without parentheses) need chapters written. Before writing a new chapter:
- Check the root ReadMe.md outline for items that are NOT hyperlinks
- Navigate to the corresponding directory and check if the ReadMe.md exists
- If the ReadMe.md exists, check if it has actual content or is empty/placeholder
- Only write content for chapters that are empty or missing
This avoids wasting time scanning directories - the outline is the source of truth for what's complete.
Publish
Once finished with the chapter, open the root directory's ReadMe.md outline and convert the chapter name to a link to the ReadMe.md that you just modified.