Hugo Nijhuis
98796ba537
Updated all skill descriptions with proper trigger terms following the pattern: "What it does. Use when [trigger terms]." Skills updated: - code-review: triggers on PR review, code quality, bugs, security - issue-writing: triggers on creating issues, bug reports, features - backlog-grooming: triggers on grooming, reviewing issue quality - roadmap-planning: triggers on planning features, breaking down work Updated docs/writing-skills.md: - Added YAML frontmatter requirements section - Documented required and optional fields - Added guidance on writing effective descriptions - Updated "How Skills are Loaded" to reflect model-invoked behavior - Added note about subagent skill access - Updated checklist with frontmatter requirements - Added reference to official documentation 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2.2 KiB
2.2 KiB
name, description
| name | description |
|---|---|
| issue-writing | Write clear, actionable issues with proper structure and acceptance criteria. Use when creating issues, writing bug reports, feature requests, or when the user needs help structuring an issue. |
Issue Writing
How to write clear, actionable issues.
Issue Structure
Title
- Start with action verb: "Add", "Fix", "Update", "Remove", "Refactor"
- Be specific: "Add user authentication" not "Auth stuff"
- Keep under 60 characters when possible
Description
## Summary
One paragraph explaining what and why.
## Acceptance Criteria
- [ ] Specific, testable requirement
- [ ] Another requirement
- [ ] User can verify this works
## Context
Additional background, links, or references.
## Technical Notes (optional)
Implementation hints or constraints.
Writing Acceptance Criteria
Good criteria are:
- Specific: "User sees error message" not "Handle errors"
- Testable: Can verify pass/fail
- User-focused: What the user experiences
- Independent: Each stands alone
Examples:
- [ ] Login form validates email format before submission
- [ ] Invalid credentials show "Invalid email or password" message
- [ ] Successful login redirects to dashboard
- [ ] Session persists across browser refresh
Issue Types
Bug Report
## Summary
Description of the bug.
## Steps to Reproduce
1. Go to...
2. Click...
3. Observe...
## Expected Behavior
What should happen.
## Actual Behavior
What happens instead.
## Environment
- Browser/OS/Version
Feature Request
## Summary
What feature and why it's valuable.
## Acceptance Criteria
- [ ] ...
## User Story (optional)
As a [role], I want [capability] so that [benefit].
Technical Task
## Summary
What technical work needs to be done.
## Scope
- Include: ...
- Exclude: ...
## Acceptance Criteria
- [ ] ...
Labels
Use labels to categorize:
bug,feature,enhancement,refactorpriority/high,priority/low- Component labels specific to project
Dependencies
Reference related issues:
- "Depends on #N" - Must complete first
- "Blocks #N" - This blocks another
- "Related to #N" - Informational link