skill-completion-rules

What problem does it solve?

This rule ensures consistent post-completion behavior for all skills, eliminating ambiguity about next steps after a task finishes.

Core Features & Use Cases

• Enforces a mandatory AskUserQuestion prompt after every skill completion to propose 2-4 next steps.
• Supports standard workflows across multiple skills, ensuring uniform handoffs and governance.
• Example: after completing /dev --build you are prompted to continue with /guard, refine design, or start a new task.

Quick Start

After a skill finishes, invoke AskUserQuestion with a concise summary of the completed work and a short list of next-step options. Example: "Task completed: design phase. Next steps: (1) proceed to /dev --tasks, (2) revisit design, (3) start a new task, (4) end session." The options should clearly indicate the recommended choice.