Files
architecture/skills/issue-writing/SKILL.md
Hugo Nijhuis 092538b097 Add new commands, skills, and agents; remove token loading script
- Add groom, plan-issues, and roadmap commands
- Add skills for backlog-grooming, forgejo, issue-writing, roadmap-planning
- Add agents directory structure
- Remove load-forgejo-token.sh and SessionStart hook (using fj auth instead)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-30 23:52:27 +01:00

2.0 KiB

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, refactor
  • priority/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