v0.8.0 templates still reference dot-notation slash commands (/speckit.plan) while skills are hyphen-named (/speckit-plan)

[phantom-suzuki]

Summary

After specify init (v0.8.1.dev0 / templates v0.8.0), the installed skills use hyphen-named slash commands (/speckit-plan, /speckit-specify, etc.) as defined in .claude/skills/speckit-<name>/SKILL.md, but several template and workflow files still reference the old dot-notation (/speckit.plan, /speckit.tasks, etc.).

This mismatch confuses both automated reviewers (CodeRabbit flagged it on a downstream PR) and human readers who try to run the referenced commands.

Affected files (in a fresh specify init . --ai claude)

• .specify/templates/plan-template.md — lines 6, 42, 43, 44, 45, 46, 47
• .specify/templates/checklist-template.md — lines 7, 13
• .specify/templates/tasks-template.md — line 32
• .specify/workflows/speckit/workflow.yml — lines 30, 42, 54, 60

Repro

specify init repro --ai claude --no-git
cd repro
grep -rn 'speckit\.' .specify/templates .specify/workflows

Observe that the grep returns multiple dot-notation references (/speckit.plan, /speckit.tasks, etc.).

Expected

All references in templates and workflow commands should match the installed skill names (speckit-plan, speckit-tasks, etc., with a hyphen) so that:

1. Documentation inside generated spec/plan artifacts points to an actually invocable slash command.
2. The workflow.yml command: identifiers correspond to the hyphen-named skills.

Suggested fix

A mechanical rename (dot → hyphen) in:

.specify/templates/plan-template.md
.specify/templates/checklist-template.md
.specify/templates/tasks-template.md
.specify/workflows/speckit/workflow.yml

Confirm that .specify/workflows/speckit/workflow.yml's command: field is read as a skill identifier (hyphen) and not as a legacy command name (dot) — if the workflow runner needs a different identifier, the workflow format itself may need to clarify.

Environment

• specify-cli version: 0.8.1.dev0
• Template version: 0.8.0
• AI integration: claude

Context

Found during a scaffold migration (older layout → v0.8.0) on a downstream repository. CodeRabbit flagged the mismatch on the migration PR.

Related: #2339 (another v0.8.0 vendor regression in create-new-feature.sh).