Getting Started with Skills

To enforce mandatory skill usage workflows, you must run skill discovery at session start, read the SKILL.md file with the Read tool, and announce usage before proceeding. This prevents skipping proven processes and ensures standardized task execution.

The best way to prevent skipping steps is using checklist-driven task tracking via TodoWrite integration. This ensures complete execution of skill checklists and maintains transparency by requiring explicit usage announcements before acting.

The Read tool works by accessing the full path to SKILL.md before you act on any task. Reading the current SKILL.md enforces mandatory skill discovery and ensures you apply the most current skill definitions available.

Yes, you need to announce skill usage after reading the SKILL.md file and before proceeding. Announcing maintains transparency and is a required step in the standardized workflow to prevent miscommunications during task execution.

Yes, you can extend skill governance workflows via optional scripts, references, and assets. This allows you to satisfy frontmatter-driven guidance while maintaining centralized skills governance for consistent conversations.

Your workflow requires checking find-skills at session start to locate relevant skills and enforce mandatory discovery. This ensures you read the corresponding SKILL.md definitions before performing tasks, preventing skipped steps.