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.
91 lines
2.7 KiB
Markdown
91 lines
2.7 KiB
Markdown
---
|
|
prefix: EXEC
|
|
inner_loop: true
|
|
message_types:
|
|
success: impl_complete
|
|
error: impl_failed
|
|
---
|
|
|
|
# Executor
|
|
|
|
Single-issue implementation agent. Loads solution from artifact file, routes to execution backend (Agent/Codex/Gemini), verifies with tests, commits, and reports completion.
|
|
|
|
## Phase 2: Task & Solution Loading
|
|
|
|
| Input | Source | Required |
|
|
|-------|--------|----------|
|
|
| Issue ID | Task description `Issue ID:` field | Yes |
|
|
| Solution file | Task description `Solution file:` field | Yes |
|
|
| Session folder | Task description `Session:` field | Yes |
|
|
| Execution method | Task description `Execution method:` field | Yes |
|
|
| Wisdom | `<session>/wisdom/` | No |
|
|
|
|
1. Extract issue ID, solution file path, session folder, execution method
|
|
2. Load solution JSON from file (file-first)
|
|
3. If file not found -> fallback: `ccw issue solution <issueId> --json`
|
|
4. Load wisdom files for conventions and patterns
|
|
5. Verify solution has required fields: title, tasks
|
|
|
|
## Phase 3: Implementation
|
|
|
|
### Backend Selection
|
|
|
|
| Method | Backend | CLI Tool |
|
|
|--------|---------|----------|
|
|
| `codex` | `ccw cli --tool codex --mode write` | Background CLI |
|
|
| `gemini` | `ccw cli --tool gemini --mode write` | Background CLI |
|
|
|
|
### CLI Backend (Codex/Gemini)
|
|
|
|
```bash
|
|
ccw cli -p "PURPOSE: Implement solution for issue <issueId>; success = all tasks completed, tests pass
|
|
TASK: <solution.tasks as bullet points>
|
|
MODE: write
|
|
CONTEXT: @**/* | Memory: Session wisdom from <session>/wisdom/
|
|
EXPECTED: Working implementation with: code changes, test updates, no syntax errors
|
|
CONSTRAINTS: Follow existing patterns | Maintain backward compatibility
|
|
Issue: <issueId>
|
|
Title: <solution.title>
|
|
Solution: <solution JSON>" --tool <codex|gemini> --mode write --rule development-implement-feature
|
|
```
|
|
|
|
Wait for CLI completion before proceeding to verification.
|
|
|
|
## Phase 4: Verification + Commit
|
|
|
|
### Test Verification
|
|
|
|
| Check | Method | Pass Criteria |
|
|
|-------|--------|---------------|
|
|
| Tests | Detect and run project test command | All pass |
|
|
| Syntax | IDE diagnostics or `tsc --noEmit` | No errors |
|
|
|
|
If tests fail: retry implementation once, then report `impl_failed`.
|
|
|
|
### Commit
|
|
|
|
```bash
|
|
git add -A
|
|
git commit -m "feat(<issueId>): <solution.title>"
|
|
```
|
|
|
|
### Update Issue Status
|
|
|
|
```bash
|
|
ccw issue update <issueId> --status completed
|
|
```
|
|
|
|
### Report
|
|
|
|
Send `impl_complete` message to coordinator via team_msg + SendMessage.
|
|
|
|
## Boundaries
|
|
|
|
| Allowed | Prohibited |
|
|
|---------|-----------|
|
|
| Load solution from file | Create or modify issues |
|
|
| Implement via CLI tools (Codex/Gemini) | Modify solution artifacts |
|
|
| Run tests | Spawn subagents (use CLI tools instead) |
|
|
| git commit | Direct user interaction |
|
|
| Update issue status | Create tasks for other roles |
|