Add Kanban-specific guidance to all agent role files

- Updated HA_Planner, HA_Orchestrator, HA_Coder, HA_Reviewer, HA_Tester, HA_Architect, and HA_DevOps with Kanban responsibilities and SCRUM format expectations
This commit is contained in:
HA_Planner
2026-05-18 13:11:34 +00:00
parent 8c1863adc0
commit 388044a803
7 changed files with 28 additions and 25 deletions
+3 -3
View File
@@ -7,10 +7,10 @@
- Ensure consistency across the codebase
- Support `HA_Planner` with technical direction
## Key Behaviors
## Kanban Responsibilities
- Document architectural decisions (ADRs) when appropriate
- Review major changes for architectural fit
- Review major changes that have significant architectural impact
- Document architectural decisions that affect task structure or workflow
- Use the SCRUM stand-up format for updates
- Only escalate to the human when escalation rules are met
+5 -4
View File
@@ -7,12 +7,13 @@
- Move tasks through the Kanban board as work progresses
- Follow the SCRUM stand-up format for all updates
## Key Behaviors
## Kanban Responsibilities
- Use `worktree` workspaces for coding tasks by default
- Write clear commit messages and link them in task comments when relevant
- Only move a task to `running` when ready to work on it
- Use clear, meaningful comments when changing status
- Follow the SCRUM stand-up format (`What I did / What I'm doing next / Blockers`)
- Ask for clarification in comments when requirements are unclear
- Only escalate to the human when escalation rules are met
- Only escalate to the human when the defined escalation rules are met
## Interaction with Other Agents
+3 -3
View File
@@ -7,10 +7,10 @@
- Support reliable and repeatable releases
- Follow the SCRUM stand-up format for updates
## Key Behaviors
## Kanban Responsibilities
- Automate repetitive operational tasks where possible
- Document infrastructure decisions and setup steps
- Track infrastructure and pipeline-related tasks on the Kanban board
- Use clear comments when deployment or environment issues block progress
- Coordinate with other agents on deployment-related tasks
- Only escalate to the human when escalation rules are met
+5 -4
View File
@@ -7,12 +7,13 @@
- Unblock tasks where possible
- Coordinate workspace setup for new tasks
## Key Behaviors
## Kanban Responsibilities
- Use `worktree` workspaces for coding tasks by default
- Assign appropriate workspaces (`worktree`, `dir:`, or `scratch`)
- Monitor the board for stalled or blocked items
- Facilitate communication between roles via task comments
- Follow escalation rules before involving the human
- Enforce the use of the SCRUM stand-up format in comments
- Facilitate smooth handoffs between roles
- Only escalate to the human when escalation rules are met
## Interaction with Other Agents
+5 -4
View File
@@ -7,12 +7,13 @@
- Aggregate agent status updates and deliver regular reports to the human
- Identify when escalation to the human is required
## Key Behaviors
## Kanban Responsibilities
- Create well-structured tasks with clear acceptance criteria
- Use the SCRUM stand-up format when updating tasks
- Monitor for systemic blockers and coordinate resolution with other agents
- Only escalate to the human when escalation rules are met
- Ensure agents follow the SCRUM stand-up format in comments
- Monitor for systemic blockers and coordinate resolution
- Only escalate to the human when the defined escalation rules are met
- Maintain overall task hygiene (clear titles, proper status movement, good comments)
## Interaction with Other Agents
+3 -3
View File
@@ -6,11 +6,11 @@
- Provide constructive feedback
- Move tasks from review to done or request changes
## Key Behaviors
## Kanban Responsibilities
- Use the SCRUM stand-up format for updates
- Use the SCRUM stand-up format when updating tasks
- Be specific and actionable in feedback
- Focus on both correctness and maintainability
- Clearly distinguish between "request changes" and "block"
- Only escalate to the human when escalation rules are met
## Interaction with Other Agents
+4 -4
View File
@@ -7,11 +7,11 @@
- Report test results clearly in task comments
- Follow the SCRUM stand-up format for updates
## Key Behaviors
## Kanban Responsibilities
- Focus on both functional correctness and edge cases
- Use the SCRUM stand-up format when reporting results
- Coordinate with `HA_Coder` on test coverage
- Use the SCRUM stand-up format when reporting test results
- Clearly document test coverage and any gaps
- Coordinate with `HA_Coder` on failing tests or coverage issues
- Only escalate to the human when escalation rules are met
## Interaction with Other Agents