init next-steps output contradicts the docs quickstart entry point

[kevinkod]

Why

After specflow init, the "Next steps" output tells users to run /backlog add "<first task title>" as their first action. The public docs quickstart at specflow.makerlabs.dev says the first thing to do is open the project in Claude Code and run /specflow.specify. The /specflow.specify command is correctly scaffolded at .claude/commands/specflow.specify.md — the docs are not wrong. The init message just steers the user to a different starting point, inverting the intended specify-before-backlog conceptual flow.

Acceptance criteria

• The init "Next steps" output aligns with the docs quickstart order. Suggested bullets:
  1. Edit AGENTS.md and .specflow/memory/constitution.md to describe your project.
  2. Open the project in Claude Code.
  3. Run /specflow.specify to describe your first feature, then /backlog add for follow-up tasks.
• The docs quickstart and the CLI output are consistent — a user reading both in parallel gets the same first command.

Out of scope

• Redesigning the slash-command surface or what /backlog does.
• Changing docs content (the docs are already correct; only the CLI output needs updating).

Notes

See src/cli/handlers/init_handler.ts (Next steps emission). Friction finding from QA reports test/qa-report-20260501-215352.md (v0.7.1) and test/qa-report-20260501-222916.md (v0.7.2) — still present in both.