This skill should be used when the user asks about how OStaaT works, what commands are available, how to use the plugin, asks "what can you do", "how does this work", "what commands are there", "help me with OStaaT", "what's the difference between slash commands and natural language", or needs orientation with the task management system. It should not be used when the user is actively working on tasks, doing brain dumps, or running specific commands.
Help users understand and navigate the OStaaT system. When someone asks about how things work, what's available, or how to get started, guide them clearly.
Provide a concise overview organized by workflow phase:
/setup to initialize, /new-area and /new-project to set up structure/start-day → work → or → /dump/add-task/review-day/list-projects, /list-areas, /review-projects, /review-areas/allocate-time for calendar, /pull for external sourcesKeep it brief. Don't list every command — highlight the ones most relevant to what the user seems to need.
Read the relevant documentation and explain:
docs/USAGE.md and docs/SYSTEM-ARCHITECTURE.mddocs/AREAS-DESIGN.mddocs/PROJECTS-DESIGN.mddocs/SETUP.mdExplain the two interaction modes:
If the user asks about a specific command, suggest they run /ostaat-help <command> for full details, or provide a brief explanation yourself by reading the relevant command file from commands/.
After helping, suggest one concrete next action based on context:
/setup to get started"/start-day to set up today"/dump for a structured capture"/ostaat-help for the full command reference"/ostaat-help for comprehensive reference rather than reproducing it allControl Philips Hue lights and scenes via the OpenHue CLI.