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>

commands/groom.md

@@ -0,0 +1,31 @@
+---
+description: Groom and improve issues. Without argument, reviews all open issues. With argument, grooms specific issue.
+argument-hint: [issue-number]
+---
+
+# Groom Issues
+
+Use the backlog-grooming and issue-writing skills.
+
+## If issue number provided ($1):
+
+1. **Fetch the issue**: `fj issue view $1`
+2. **Evaluate** against grooming checklist
+3. **Suggest improvements** for:
+   - Title clarity
+   - Description completeness
+   - Acceptance criteria quality
+   - Scope definition
+4. **Ask user** if they want to apply changes
+5. **Update issue** if approved: `fj issue edit $1 --body "..."`
+
+## If no argument (groom all):
+
+1. **List open issues**: `fj issue search -s open`
+2. **Review each** against grooming checklist
+3. **Categorize**:
+   - Ready: Well-defined, can start work
+   - Needs work: Missing info or unclear
+   - Stale: No longer relevant
+4. **Present summary** table
+5. **Offer to improve** issues that need work

commands/plan-issues.md

@@ -0,0 +1,34 @@
+---
+description: Plan and create issues for a feature or improvement. Breaks down work into well-structured issues.
+argument-hint: <feature-description>
+---
+
+# Plan Feature: $1
+
+Use the roadmap-planning, issue-writing, and forgejo skills.
+
+1. **Understand the feature**: Analyze what "$1" involves
+2. **Explore the codebase** if needed to understand context
+3. **Break down** into discrete, actionable issues:
+   - Each issue should be independently completable
+   - Clear dependencies between issues
+   - Appropriate scope (not too big, not too small)
+
+4. **Present the plan**:
+   ```
+   ## Proposed Issues for: $1
+
+   1. [Title] - Brief description
+      Dependencies: none
+
+   2. [Title] - Brief description
+      Dependencies: #1
+
+   3. [Title] - Brief description
+      Dependencies: #1, #2
+   ```
+
+5. **Ask for approval** before creating issues
+6. **Create issues** in order using `fj issue create`
+7. **Update dependencies** with actual issue numbers after creation
+8. **Present summary** with links to created issues

commands/roadmap.md

@@ -0,0 +1,31 @@
+---
+description: View current issues as a roadmap. Shows open issues organized by status and dependencies.
+---
+
+# Roadmap View
+
+Use the forgejo skill.
+
+1. **Fetch all open issues**: `fj issue search -s open`
+2. **Analyze dependencies** from issue descriptions
+3. **Categorize issues**:
+   - Blocked: Waiting on other issues
+   - Ready: No blockers, can start
+   - In Progress: Has assignee or WIP label
+4. **Present roadmap** as organized list:
+
+```
+## Ready to Start
+- #5: Add user authentication
+- #8: Create dashboard layout
+
+## In Progress
+- #3: Setup database schema
+
+## Blocked
+- #7: User profile page (blocked by #5)
+- #9: Admin dashboard (blocked by #3, #8)
+```
+
+5. **Highlight** any issues that seem stale or unclear
+6. **Suggest** next actions based on the roadmap state