mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-10 17:11:04 +08:00
62d8aa3623
- 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.
1.9 KiB
1.9 KiB
TASK ASSIGNMENT
MANDATORY FIRST STEPS
- Read role definition: {role_spec_path} (MUST read first)
- Read shared discoveries: {session_folder}/discoveries.ndjson (if exists, skip if not)
- Read project context: .workflow/project-tech.json (if exists)
Your Task
Task ID: {id} Title: {title} Description: {description} Role: {role}
Previous Tasks' Findings (Context)
{prev_context}
Execution Protocol
- Read role definition: Load {role_spec_path} for Phase 2-4 domain instructions (MANDATORY)
- Read discoveries: Load {session_folder}/discoveries.ndjson for shared exploration findings
- Use context: Apply previous tasks' findings from prev_context above
- Execute: Follow the role-specific instructions from your role definition file
- Share discoveries: Append exploration findings to shared board:
echo '{"ts":"<ISO8601>","worker":"{id}","type":"<type>","data":{...}}' >> {session_folder}/discoveries.ndjson - Report result: Return JSON via report_agent_job_result
Role Definition Structure
Your role definition file contains:
- Phase 2: Context & scope resolution
- Phase 3: Execution steps
- Phase 4: Output generation
Follow the phases in order as defined in your role file.
Discovery Types to Share
implementation: {file, function, approach, notes} — Implementation approach takentest_result: {test_name, status, duration} — Test execution resultreview_comment: {file, line, severity, comment} — Code review commentpattern: {pattern, files[], occurrences} — Code pattern identified
Output (report_agent_job_result)
Return JSON: { "id": "{id}", "status": "completed" | "failed", "findings": "Key discoveries and implementation notes (max 500 chars)", "error": "" }
Findings format: Concise summary of what was accomplished, key decisions made, and any important notes for downstream tasks.