Hugo Nijhuis
f8d4640d4f
- Add Architecture Beliefs section to manifesto with outcome-focused beliefs: auditability, business language in code, independent evolution, explicit over implicit - Create software-architecture.md as human-readable documentation - Enhance software-architecture skill with beliefs→patterns mapping (DDD, Event Sourcing, event-driven communication) and auto-trigger description - Update work-issue command to reference skill and check project architecture - Update issue-worker agent with software-architecture skill - Add Architecture section template to vision-management skill The skill is now auto-triggered when implementing, reviewing, or planning architectural work. Project-level architecture choices go in vision.md. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
20 lines
1.0 KiB
Markdown
20 lines
1.0 KiB
Markdown
---
|
|
description: Work on a Gitea issue. Fetches issue details and sets up branch for implementation.
|
|
argument-hint: <issue-number>
|
|
---
|
|
|
|
# Work on Issue #$1
|
|
|
|
@~/.claude/skills/gitea/SKILL.md
|
|
@~/.claude/skills/software-architecture/SKILL.md
|
|
|
|
1. **View the issue** with `--comments` flag to understand requirements and context
|
|
2. **Create a branch**: `git checkout -b issue-$1-<short-kebab-title>`
|
|
3. **Plan**: Use TodoWrite to break down the work based on acceptance criteria
|
|
4. **Check architecture**: Review the project's vision.md Architecture section for project-specific patterns and divergences
|
|
5. **Implement** the changes following architectural patterns (DDD, event sourcing where appropriate)
|
|
6. **Commit** with message referencing the issue
|
|
7. **Push** the branch to origin
|
|
8. **Create PR** with title "[Issue #$1] <title>" and body "Closes #$1"
|
|
9. **Auto-review**: Inform the user that auto-review is starting, then spawn the `code-reviewer` agent in background (using `run_in_background: true`) with the PR number
|