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>
1.0 KiB
1.0 KiB
description, argument-hint
| description | argument-hint |
|---|---|
| Work on a Gitea issue. Fetches issue details and sets up branch for implementation. | <issue-number> |
Work on Issue #$1
@/.claude/skills/gitea/SKILL.md
@/.claude/skills/software-architecture/SKILL.md
- View the issue with
--commentsflag to understand requirements and context - Create a branch:
git checkout -b issue-$1-<short-kebab-title> - Plan: Use TodoWrite to break down the work based on acceptance criteria
- Check architecture: Review the project's vision.md Architecture section for project-specific patterns and divergences
- Implement the changes following architectural patterns (DDD, event sourcing where appropriate)
- Commit with message referencing the issue
- Push the branch to origin
- Create PR with title "[Issue #$1]