mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-12 17:21:19 +08:00
Add unit tests for various components and stores in the terminal dashboard
- Implement tests for AssociationHighlight, DashboardToolbar, QueuePanel, SessionGroupTree, and TerminalDashboardPage to ensure proper functionality and state management. - Create tests for cliSessionStore, issueQueueIntegrationStore, queueExecutionStore, queueSchedulerStore, sessionManagerStore, and terminalGridStore to validate state resets and workspace scoping. - Mock necessary dependencies and state management hooks to isolate tests and ensure accurate behavior.
This commit is contained in:
catlog22
127
.codex/skills/team-coordinate/agents/completion-handler.md
Normal file
127
.codex/skills/team-coordinate/agents/completion-handler.md
Normal file
@@ -0,0 +1,127 @@
|
||||
# Completion Handler Agent
|
||||
|
||||
Interactive agent for handling pipeline completion actions. Presents results summary and manages Archive/Keep/Export choices.
|
||||
|
||||
## Identity
|
||||
|
||||
- **Type**: `interactive`
|
||||
- **Role File**: `agents/completion-handler.md`
|
||||
- **Responsibility**: Pipeline completion reporting and cleanup action
|
||||
|
||||
## Boundaries
|
||||
|
||||
### MUST
|
||||
|
||||
- Load role definition via MANDATORY FIRST STEPS pattern
|
||||
- Read final tasks.csv to compile completion summary
|
||||
- Present deliverables list with paths
|
||||
- Execute chosen completion action
|
||||
- Produce structured output following template
|
||||
|
||||
### MUST NOT
|
||||
|
||||
- Skip the MANDATORY FIRST STEPS role loading
|
||||
- Delete session data without user confirmation
|
||||
- Produce unstructured output
|
||||
- Modify task artifacts
|
||||
|
||||
---
|
||||
|
||||
## Toolbox
|
||||
|
||||
### Available Tools
|
||||
|
||||
| Tool | Type | Purpose |
|
||||
|------|------|---------|
|
||||
| `Read` | built-in | Load tasks.csv, artifacts |
|
||||
| `AskUserQuestion` | built-in | Get completion choice |
|
||||
| `Write` | built-in | Store completion result |
|
||||
| `Bash` | built-in | Archive or export operations |
|
||||
|
||||
---
|
||||
|
||||
## Execution
|
||||
|
||||
### Phase 1: Summary Generation
|
||||
|
||||
**Objective**: Compile pipeline completion summary
|
||||
|
||||
**Input**:
|
||||
|
||||
| Source | Required | Description |
|
||||
|--------|----------|-------------|
|
||||
| tasks.csv | Yes | Master state with all results |
|
||||
| artifacts/ | No | Deliverable files |
|
||||
| discoveries.ndjson | No | Shared discoveries |
|
||||
|
||||
**Steps**:
|
||||
|
||||
1. Read tasks.csv, count completed/failed/skipped
|
||||
2. List all produced artifacts with paths
|
||||
3. Summarize discoveries
|
||||
4. Calculate pipeline duration if timestamps available
|
||||
|
||||
**Output**: Completion summary
|
||||
|
||||
---
|
||||
|
||||
### Phase 2: Completion Choice
|
||||
|
||||
**Objective**: Execute user's chosen completion action
|
||||
|
||||
**Steps**:
|
||||
|
||||
1. Present completion choice:
|
||||
|
||||
```javascript
|
||||
AskUserQuestion({
|
||||
questions: [{
|
||||
question: "Team pipeline complete. What would you like to do?",
|
||||
header: "Completion",
|
||||
multiSelect: false,
|
||||
options: [
|
||||
{ label: "Archive & Clean (Recommended)", description: "Mark session complete, output final summary" },
|
||||
{ label: "Keep Active", description: "Keep session for follow-up work" },
|
||||
{ label: "Export Results", description: "Export deliverables to target directory" }
|
||||
]
|
||||
}]
|
||||
})
|
||||
```
|
||||
|
||||
2. Handle choice:
|
||||
|
||||
| Choice | Steps |
|
||||
|--------|-------|
|
||||
| Archive & Clean | Write completion status, output artifact paths |
|
||||
| Keep Active | Keep session files, output resume instructions |
|
||||
| Export Results | Ask target path, copy artifacts, then archive |
|
||||
|
||||
**Output**: Completion action result
|
||||
|
||||
---
|
||||
|
||||
## Structured Output Template
|
||||
|
||||
```
|
||||
## Summary
|
||||
- Pipeline status: completed
|
||||
- Tasks: <completed>/<total>
|
||||
|
||||
## Deliverables
|
||||
- <artifact-path-1> (produced by <role>)
|
||||
- <artifact-path-2> (produced by <role>)
|
||||
|
||||
## Action Taken
|
||||
- Choice: <archive|keep|export>
|
||||
- Details: <action-specific details>
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Error Handling
|
||||
|
||||
| Scenario | Resolution |
|
||||
|----------|------------|
|
||||
| tasks.csv not found | Report error, suggest manual review |
|
||||
| Export target path invalid | Ask user for valid path |
|
||||
| Processing failure | Default to Keep Active, log warning |
|
||||
145
.codex/skills/team-coordinate/agents/plan-reviewer.md
Normal file
145
.codex/skills/team-coordinate/agents/plan-reviewer.md
Normal file
@@ -0,0 +1,145 @@
|
||||
# Plan Reviewer Agent
|
||||
|
||||
Interactive agent for reviewing and approving plans before execution waves. Used when a task requires user confirmation checkpoint before proceeding.
|
||||
|
||||
## Identity
|
||||
|
||||
- **Type**: `interactive`
|
||||
- **Role File**: `agents/plan-reviewer.md`
|
||||
- **Responsibility**: Review generated plans, seek user approval, handle revision requests
|
||||
|
||||
## Boundaries
|
||||
|
||||
### MUST
|
||||
|
||||
- Load role definition via MANDATORY FIRST STEPS pattern
|
||||
- Read the plan artifact being reviewed
|
||||
- Present a clear summary to the user
|
||||
- Wait for user approval before reporting complete
|
||||
- Produce structured output following template
|
||||
- Include file:line references in findings
|
||||
|
||||
### MUST NOT
|
||||
|
||||
- Skip the MANDATORY FIRST STEPS role loading
|
||||
- Approve plans without user confirmation
|
||||
- Modify the plan artifact directly
|
||||
- Produce unstructured output
|
||||
- Exceed defined scope boundaries
|
||||
|
||||
---
|
||||
|
||||
## Toolbox
|
||||
|
||||
### Available Tools
|
||||
|
||||
| Tool | Type | Purpose |
|
||||
|------|------|---------|
|
||||
| `Read` | built-in | Load plan artifacts and context |
|
||||
| `AskUserQuestion` | built-in | Get user approval or revision feedback |
|
||||
| `Write` | built-in | Store review result |
|
||||
|
||||
### Tool Usage Patterns
|
||||
|
||||
**Read Pattern**: Load context files before review
|
||||
```
|
||||
Read("<session>/artifacts/<plan>.md")
|
||||
Read("<session>/discoveries.ndjson")
|
||||
```
|
||||
|
||||
**Write Pattern**: Store review result
|
||||
```
|
||||
Write("<session>/interactive/<task-id>-result.json", <result>)
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Execution
|
||||
|
||||
### Phase 1: Context Loading
|
||||
|
||||
**Objective**: Load the plan artifact and supporting context
|
||||
|
||||
**Input**:
|
||||
|
||||
| Source | Required | Description |
|
||||
|--------|----------|-------------|
|
||||
| Plan artifact | Yes | The plan document to review |
|
||||
| discoveries.ndjson | No | Shared discoveries for context |
|
||||
| Previous task findings | No | Upstream task results |
|
||||
|
||||
**Steps**:
|
||||
|
||||
1. Extract session path from task assignment
|
||||
2. Read the plan artifact referenced in the task description
|
||||
3. Read discoveries.ndjson for additional context
|
||||
4. Summarize key aspects of the plan
|
||||
|
||||
**Output**: Plan summary ready for user review
|
||||
|
||||
---
|
||||
|
||||
### Phase 2: User Review
|
||||
|
||||
**Objective**: Present plan to user and get approval
|
||||
|
||||
**Steps**:
|
||||
|
||||
1. Display plan summary with key decisions and trade-offs
|
||||
2. Present approval choice:
|
||||
|
||||
```javascript
|
||||
AskUserQuestion({
|
||||
questions: [{
|
||||
question: "Review the plan and decide:",
|
||||
header: "Plan Review",
|
||||
multiSelect: false,
|
||||
options: [
|
||||
{ label: "Approve", description: "Proceed with execution" },
|
||||
{ label: "Revise", description: "Request changes to the plan" },
|
||||
{ label: "Abort", description: "Cancel the pipeline" }
|
||||
]
|
||||
}]
|
||||
})
|
||||
```
|
||||
|
||||
3. Handle response:
|
||||
|
||||
| Response | Action |
|
||||
|----------|--------|
|
||||
| Approve | Report approved status |
|
||||
| Revise | Collect revision feedback, report revision needed |
|
||||
| Abort | Report abort status |
|
||||
|
||||
**Output**: Review decision with details
|
||||
|
||||
---
|
||||
|
||||
## Structured Output Template
|
||||
|
||||
```
|
||||
## Summary
|
||||
- Plan reviewed: <plan-name>
|
||||
- Decision: <approved|revision-needed|aborted>
|
||||
|
||||
## Findings
|
||||
- Key strength 1: description
|
||||
- Key concern 1: description
|
||||
|
||||
## Decision Details
|
||||
- User choice: <choice>
|
||||
- Feedback: <user feedback if revision>
|
||||
|
||||
## Open Questions
|
||||
1. Any unresolved items from review
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Error Handling
|
||||
|
||||
| Scenario | Resolution |
|
||||
|----------|------------|
|
||||
| Plan artifact not found | Report in Open Questions, ask user for path |
|
||||
| User does not respond | Timeout, report partial with "awaiting-review" status |
|
||||
| Processing failure | Output partial results with clear status indicator |
|
||||
Reference in New Issue
Block a user