mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-25 19:48:33 +08:00
- Delete 21 old team skill directories using CSV-wave pipeline pattern (~100+ files) - Delete old team-lifecycle (v3) and team-planex-v2 - Create generic team-worker.toml and team-supervisor.toml (replacing tlv4-specific TOMLs) - Convert 19 team skills from Claude Code format (Agent/SendMessage/TaskCreate) to Codex format (spawn_agent/wait_agent/tasks.json/request_user_input) - Update team-lifecycle-v4 to use generic agent types (team_worker/team_supervisor) - Convert all coordinator role files: dispatch.md, monitor.md, role.md - Convert all worker role files: remove run_in_background, fix Bash syntax - Convert all specs/pipelines.md references - Final state: 20 team skills, 217 .md files, zero Claude Code API residuals Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2.6 KiB
2.6 KiB
role, prefix, inner_loop, message_types
| role | prefix | inner_loop | message_types | ||||||
|---|---|---|---|---|---|---|---|---|---|
| developer | DEV | true |
|
Developer
Code implementer. Implements code according to design, incremental delivery. Acts as Generator in Generator-Critic loop (paired with reviewer).
Phase 2: Context Loading
| Input | Source | Required |
|---|---|---|
| Task description | From task subject/description | Yes |
| Session path | Extracted from task description | Yes |
| .msg/meta.json | /.msg/meta.json | Yes |
| Design document | /design/design-001.md | For non-fix tasks |
| Task breakdown | /design/task-breakdown.json | For non-fix tasks |
| Review feedback | /review/*.md | For fix tasks |
| Wisdom files | /wisdom/ | No |
- Extract session path from task description
- Read .msg/meta.json for shared context
- Detect task type:
| Task Type | Detection | Loading |
|---|---|---|
| Fix task | Subject contains "fix" | Read latest review file for feedback |
| Normal task | No "fix" in subject | Read design document + task breakdown |
- Load previous implementation_context from .msg/meta.json
- Read wisdom files for conventions and known issues
Phase 3: Code Implementation
Implementation strategy selection:
| Task Count | Complexity | Strategy |
|---|---|---|
| <= 2 tasks | Low | Direct: inline Edit/Write |
| 3-5 tasks | Medium | Single agent: one code-developer for all |
| > 5 tasks | High | Batch agent: group by module, one agent per batch |
Fix Task Mode (GC Loop):
- Focus on review feedback items only
- Fix critical issues first, then high, then medium
- Do NOT change code that was not flagged
- Maintain existing code style and patterns
Normal Task Mode:
- Read target files, apply changes using Edit or Write
- Follow execution order from task breakdown
- Validate syntax after each major change
Phase 4: Self-Validation
| Check | Method | Pass Criteria |
|---|---|---|
| Syntax | tsc --noEmit or equivalent | No errors |
| File existence | Verify all planned files exist | All files present |
| Import resolution | Check no broken imports | All imports resolve |
- Run syntax check:
tsc --noEmit/python -m py_compile/ equivalent - Auto-fix if validation fails (max 2 attempts)
- Write dev log to
<session>/code/dev-log.md:- Changed files count, syntax status, fix task flag, file list
- Update implementation_context in .msg/meta.json:
- task, changed_files, is_fix, syntax_clean
- Write discoveries to wisdom/learnings.md