docs: clean up develop skill boilerplate and stale references

[jwaldrip]

Summary

• Enrich description frontmatter with trigger terms for better skill matching
• Remove 4 redundant sections (Name, Synopsis, Description, Implementation) that repeated "Comprehensive 8-phase workflow" verbatim
• Remove stale Usage section referencing non-existent /feature-dev command
• Update See Also to reference current skill names

All phase content, best practices, and example workflow preserved unchanged.

Inspired by observations in #77 (without the third-party CI dependency).

[railway-app]

🚅 Deployed to the han-pr-84 environment in han-team-platform

4 services not affected by this PR

• postgres
• redis
• api
• website

[claude]

Code Review

This is a clean, well-scoped documentation improvement. Changes are straightforward and correct.

What looks good:

• The enriched description frontmatter with natural-language trigger phrases (add a feature, implement a new capability, build functionality, develop a feature end-to-end) is a meaningful improvement for skill matching
• Removing the 4 redundant Name/Synopsis/Description/Implementation sections that all repeated the same one-liner is the right call — they added noise, not signal
• Removing the stale /feature-dev Usage section prevents user confusion (the command doesn't exist)
• The updated See Also references (/review, /test, /fix, /refactor) all verified to exist as actual SKILL.md files; the removed ones (/commit, /create-blog-post, tdd:test-driven-development, han-core:code-reviewer) don't exist as skill files

MINOR: Blog post trigger in description

The trigger phrase "write a blog post" at the end of the description summary could cause the develop skill to fire on generic blog-writing requests unrelated to feature development. It's accurate (phase 8 is a blog post), but a user asking "write me a blog post about X" might unintentionally invoke the full 8-phase workflow. Consider whether this is the intended behavior or if phase 8 is better left implicit.

Otherwise, no issues. LGTM.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!