Prevent /spec Substitution With /interview In Speckit

Prevent /spec Substitution with /interview in Speckit

The Issue

When users invoke /spec, there's a chance that the operator might mistakenly use /interview instead. This substitution skips crucial steps, leaving users with no filed issues and confusion.

Why It Matters

The /spec command is a multi-step process: interview, plan approval, catalog, and epic creation. Substituting /interview silently short-circuits the last three steps, causing issues to go unnoticed.

The Solution

To fix this, we propose two targeted changes:

1. Update speckit:spec Skill

In the speckit:spec skill file, add a constraint:

When the user types /spec or triggers this skill by name, you MUST invoke this skill (speckit:spec), not speckit:interview directly. speckit:interview is a sub-skill called from within step 2 of this skill - never a substitute for it.

2. Add Note to speckit:interview Skill

In the speckit:interview skill file, add a note at the top:

Sub-skill notice: This skill is designed to be invoked by speckit:spec or standalone via /interview. If the user typed /spec, stop and invoke speckit:spec instead - do not run this skill directly.

By implementing these changes, we can prevent the substitution and ensure all steps of the /spec process are followed correctly.