flowmade-one/architecture
3
0
Fork 0
Code Issues 15 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Create /arch-refine-issue command #59

New Issue
Closed
opened 2026-01-09 22:59:37 +00:00 by HugoNijhuis · 0 comments
HugoNijhuis commented 2026-01-09 22:59:37 +00:00
Owner
Copy Link

Summary

Create a command that refines an issue in the context of the project's architecture. The command first analyzes the existing codebase to understand patterns and structure, then refines the issue with architectural perspective.

Acceptance Criteria

  • Command file created at commands/arch-refine-issue.md
  • Command takes issue number as argument
  • Spawns software-architect agent for contextual analysis
  • Analyzes existing project architecture before refining
  • Suggests implementation approach that fits existing patterns
  • Identifies architectural dependencies
  • Flags concerns (breaking changes, tech debt, pattern violations)
  • Proposes refined description and acceptance criteria
  • Adds technical notes about how the issue fits the architecture

Context

User runs /arch-refine-issue 42 to get architectural input on an issue before implementation.

Dependencies

  • Depends on #56 (software-architecture skill)
  • Depends on #57 (software-architect agent)

Technical Notes

The command must understand the existing codebase context - not refine in isolation. This means:

  1. Read project structure and key packages
  2. Understand current patterns and conventions
  3. Identify modules that will be affected
  4. Then refine the issue with that context
## Summary Create a command that refines an issue in the context of the project's architecture. The command first analyzes the existing codebase to understand patterns and structure, then refines the issue with architectural perspective. ## Acceptance Criteria - [ ] Command file created at `commands/arch-refine-issue.md` - [ ] Command takes issue number as argument - [ ] Spawns software-architect agent for contextual analysis - [ ] Analyzes existing project architecture before refining - [ ] Suggests implementation approach that fits existing patterns - [ ] Identifies architectural dependencies - [ ] Flags concerns (breaking changes, tech debt, pattern violations) - [ ] Proposes refined description and acceptance criteria - [ ] Adds technical notes about how the issue fits the architecture ## Context User runs `/arch-refine-issue 42` to get architectural input on an issue before implementation. ## Dependencies - Depends on #56 (software-architecture skill) - Depends on #57 (software-architect agent) ## Technical Notes The command must understand the existing codebase context - not refine in isolation. This means: 1. Read project structure and key packages 2. Understand current patterns and conventions 3. Identify modules that will be affected 4. Then refine the issue with that context
HugoNijhuis added a new dependency 2026-01-09 23:00:01 +00:00
#56 Create software-architecture skill
HugoNijhuis added a new dependency 2026-01-09 23:00:01 +00:00
#57 Create software-architect agent
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
HugoNijhuis fluxcd-bot renovate-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Depends on
#56 Create software-architecture skill
flowmade-one/architecture
#57 Create software-architect agent
flowmade-one/architecture
Reference: flowmade-one/architecture#59
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?