mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-06 16:31:12 +08:00
fd847070d5
- Enhanced multi-perspective discussion capabilities in discuss-subagent for architecture optimization, integrating CLI tools for structured analysis and recommendations. - Updated explore-subagent to utilize CLI tools directly for architecture-critical structure exploration, improving efficiency. - Streamlined discuss-subagent in team-coordinate to leverage CLI for multi-perspective critiques, enhancing artifact evaluation. - Modified explore-subagent in team-coordinate to adopt CLI tools for codebase exploration, ensuring consistency across roles. - Expanded team-issue skill to include additional tools for issue resolution, refining role-specific execution and restrictions. - Improved explorer role specifications to utilize CLI for exploration tasks, enhancing context gathering for architecture-critical structures. - Adjusted implementer role specifications to route execution through CLI tools, optimizing backend selection for task execution. - Enhanced integrator role specifications to utilize CLI for queue formation, improving issue resolution efficiency. - Updated planner role specifications to leverage CLI for solution generation, ensuring structured implementation planning. - Refined analyst role specifications to utilize CLI for codebase exploration, enhancing context generation for research. - Adjusted executor role specifications to utilize CLI tools for task execution, improving backend selection and error handling. - Enhanced writer role specifications to generate documents using CLI tools, streamlining document generation processes. - Updated team-planex skill to reflect changes in execution methods, focusing on CLI tools for task execution. - Refined team-testing role specifications to utilize CLI for test generation and failure resolution, improving testing workflows. - Enhanced ultra-analyze role specifications to leverage CLI tools for discussion and exploration tasks, improving analysis depth and clarity.
90 lines
3.4 KiB
Markdown
90 lines
3.4 KiB
Markdown
---
|
|
prefix: BUILD
|
|
inner_loop: false
|
|
message_types:
|
|
success: impl_complete
|
|
failed: impl_failed
|
|
error: error
|
|
---
|
|
|
|
# Issue Implementer
|
|
|
|
Load solution plan, route to execution backend (Agent/Codex/Gemini), run tests, and commit. Execution method determined by coordinator during task creation. Supports parallel instances for batch mode.
|
|
|
|
## Modes
|
|
|
|
| Backend | Condition | Method |
|
|
|---------|-----------|--------|
|
|
| codex | task_count > 3 or explicit | `ccw cli --tool codex --mode write --id issue-<issueId>` |
|
|
| gemini | task_count <= 3 or explicit | `ccw cli --tool gemini --mode write --id issue-<issueId>` |
|
|
| qwen | explicit | `ccw cli --tool qwen --mode write --id issue-<issueId>` |
|
|
|
|
## Phase 2: Load Solution & Resolve Executor
|
|
|
|
| Input | Source | Required |
|
|
|-------|--------|----------|
|
|
| Issue ID | Task description (GH-\d+ or ISS-\d{8}-\d{6}) | Yes |
|
|
| Bound solution | `ccw issue solutions <id> --json` | Yes |
|
|
| Explorer context | `<session>/explorations/context-<issueId>.json` | No |
|
|
| Execution method | Task description (`execution_method: Codex|Gemini|Qwen|Auto`) | Yes |
|
|
| Code review | Task description (`code_review: Skip|Gemini Review|Codex Review`) | No |
|
|
|
|
1. Extract issue ID from task description
|
|
2. If no issue ID -> report error, STOP
|
|
3. Load bound solution: `Bash("ccw issue solutions <issueId> --json")`
|
|
4. If no bound solution -> report error, STOP
|
|
5. Load explorer context (if available)
|
|
6. Resolve execution method (Auto: task_count <= 3 -> gemini, else codex)
|
|
7. Update issue status: `Bash("ccw issue update <issueId> --status in-progress")`
|
|
|
|
## Phase 3: Implementation (Multi-Backend Routing)
|
|
|
|
**Execution prompt template** (all backends):
|
|
|
|
```
|
|
## Issue
|
|
ID: <issueId>
|
|
Title: <solution.bound.title>
|
|
|
|
## Solution Plan
|
|
<solution.bound JSON>
|
|
|
|
## Codebase Context (from explorer)
|
|
Relevant files: <explorerContext.relevant_files>
|
|
Existing patterns: <explorerContext.existing_patterns>
|
|
Dependencies: <explorerContext.dependencies>
|
|
|
|
## Implementation Requirements
|
|
1. Follow the solution plan tasks in order
|
|
2. Write clean, minimal code following existing patterns
|
|
3. Run tests after each significant change
|
|
4. Ensure all existing tests still pass
|
|
5. Do NOT over-engineer
|
|
|
|
## Quality Checklist
|
|
- All solution tasks implemented
|
|
- No TypeScript/linting errors
|
|
- Existing tests pass
|
|
- New tests added where appropriate
|
|
```
|
|
|
|
Route by executor:
|
|
- **codex**: `Bash("ccw cli -p \"<prompt>\" --tool codex --mode write --id issue-<issueId>", { run_in_background: false })`
|
|
- **gemini**: `Bash("ccw cli -p \"<prompt>\" --tool gemini --mode write --id issue-<issueId>", { run_in_background: false })`
|
|
- **qwen**: `Bash("ccw cli -p \"<prompt>\" --tool qwen --mode write --id issue-<issueId>", { run_in_background: false })`
|
|
|
|
On CLI failure, resume: `ccw cli -p "Continue" --resume issue-<issueId> --tool <tool> --mode write`
|
|
|
|
## Phase 4: Verify & Commit
|
|
|
|
| Check | Method | Pass Criteria |
|
|
|-------|--------|---------------|
|
|
| Tests pass | Detect and run test command | No new failures |
|
|
| Code review | Optional, per task config | Review output logged |
|
|
|
|
- Tests pass -> optional code review -> `ccw issue update <issueId> --status resolved` -> report `impl_complete`
|
|
- Tests fail -> report `impl_failed` with truncated test output
|
|
|
|
Update `<session>/wisdom/.msg/meta.json` under `implementer` namespace:
|
|
- Read existing -> merge `{ "implementer": { issue_id, executor, test_status, review_status } }` -> write back
|