fix(quick-dev): preserve tracking identifiers in spec slug

[alexeyv]

Summary

• Step-01 slug derivation now instructs the LLM to lead with tracking identifiers (story numbers, issue IDs, ticket IDs) when present
• Tightened from "numbered" to "tracking" to avoid false positives on domain numbers (retries, 2FA, HTTP codes)
• Added inline examples (3-2-digest-delivery, gh-47-fix-auth) to anchor consistent behavior

Test plan

• Invoke quick-dev with an intent referencing a story number (e.g. "story 3-2: add digest delivery") — slug should lead with 3-2
• Invoke quick-dev with an intent containing incidental numbers (e.g. "add 3 retries") — slug should NOT lead with 3
• Invoke quick-dev with a GitHub issue reference (e.g. "Customizations for Lovable user #47 fix auth") — slug should lead with gh-47

🤖 Generated with Claude Code

[augmentcode]

🤖 Augment PR Summary

Summary: Updates quick-dev Step-01 guidance so spec slugs preserve tracking identifiers (story/issue/ticket) by prefixing them when present.
Details: Clarifies wording to reduce false positives from incidental numbers and adds concrete examples (e.g., 3-2-digest-delivery, gh-47-fix-auth).

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 1 suggestion posted.

Comment augment review to trigger a new review at any time.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: bc2b6da1-8667-4874-89c9-c226d39ecb94

📥 Commits

Reviewing files that changed from the base of the PR and between ac5cb9d and 7cf6772.

📒 Files selected for processing (1)

• src/bmm-skills/4-implementation/bmad-quick-dev/step-01-clarify-and-route.md

---

📝 Walkthrough

Walkthrough

Documentation update clarifying slug generation logic in the Plan-code-review routing path. The specification now documents that kebab-case slugs are conditionally prefixed with tracking identifiers (e.g., story/issue/ticket IDs) to produce results like 3-2-digest-delivery or gh-47-fix-auth.

Changes

Cohort / File(s)	Summary
Documentation Update src/bmm-skills/4-implementation/bmad-quick-dev/step-01-clarify-and-route.md	Clarified slug-generation behavior in the Plan-code-review path to document conditional prefixing of kebab-case slugs with referenced tracking identifiers.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly describes the main change: preserving tracking identifiers in the spec slug derivation process, which matches the core modification in the changeset.
Description check	✅ Passed	The description is directly related to the changeset, explaining the slug derivation changes, the terminology shift from 'numbered' to 'tracking', and providing concrete examples and test cases.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/preserve-id-in-slug

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}