edit-backlog-item

wmeints's avatarfrom wmeints

Use this skill when creating or editing issues on Github or when asked to write user-stories or record bugs.

⭐2stars🔀0forks📁View on GitHub🕐Updated Jan 3, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill streamlines software development workflows by automating the creation, editing, and management of GitHub issues. It ensures project consistency by enforcing standardized templates for user stories and bug reports, automatically applying relevant labels like 'kind:bug' and 'kind:story' to maintain an organized and searchable backlog.

Use Cases

  • Automatically generating structured user stories from conversational requirements and posting them directly to a GitHub repository.
  • Recording and labeling software bugs discovered during development or testing to ensure they follow the team's official documentation standards.
  • Updating existing backlog items to refine task lists or adjust project goals without leaving the AI chat interface.
  • Ensuring all team members adhere to specific Markdown templates for project documentation and issue tracking.
nameedit-backlog-item
descriptionUse this skill when creating or editing issues on Github or when asked to write user-stories or record bugs.

Edit Backlog Item

Use this skill to create or edit issues on the Github repository for the project. You should use this skill also when asked to write or edit user stories or bugs.

Managing user stories

  • User stories follow the template described in ./templates/user-story.md
  • Tasks in user stories should add value towards the goal. When you need to complete multiple tasks to get a concrete runnable result, it should be one task on the list instead of separate tasks.
  • Important: You must adhere to the provided template.

Managing bugs

  • User stories follow the template described in ./templates/user-story.md
  • Tasks in user stories should add value towards the goal. When you need to complete multiple tasks to get a concrete runnable result, it should be one task on the list instead of separate tasks.
  • Important: You must adhere to the provided template.

Recording user stories and bugs

  • Important: record user stories and bugs in the GitHub repository associated with the codebase!
  • Use the label kind:bug for recording bugs on GitHub.
  • Use the label kind:story for recording user stories on GitHub.