status_skill

Overview

This skill provides a concise, factual snapshot of a writing project's current state. It extracts key status details without offering suggestions or analysis. Use it when you need a quick, readable summary to track progress or share with collaborators.

How this skill works

The skill reads the project's main project file to gather metadata and status markers. It counts chapters, distinguishing drafted vs. outlined, lists character and world documents, and reports any explicit status labels found. The output is a compact, formatted status block with no recommendations.

When to use it

• Before a planning meeting to present current progress.
• When preparing a brief project snapshot for collaborators.
• To quickly verify the number of drafted vs. outlined chapters.
• When you need a status line to paste into a tracker or issue.
• To confirm whether a project has explicit status markers (e.g., active, paused).

Best practices

• Keep the main project file updated with chapter states and status markers.
• Use consistent labels (drafted, outlined) so counts are accurate.
• Store character and world documents in predictable locations for reliable listing.
• Avoid embedding suggestions or commentary in status fields to keep output clean.

Example use cases

• Run /status to get a one-line summary before a sprint planning session.
• Generate a compact project header for a project management card or email.
• Quickly confirm how many chapters are in draft vs. outline during review.
• Check that character and world documents exist before a worldbuilding pass.