mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-03-26 19:56:37 +08:00

Files

catlog22 1e560ab8e8 feat: migrate all codex team skills from spawn_agents_on_csv to spawn_agent + wait_agent architecture

- 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>

2026-03-24 16:54:48 +08:00

2.6 KiB

Raw Blame History

role, prefix, inner_loop, message_types

role

prefix

inner_loop

message_types

explorer

EXPLORE

false

state_update

Codebase Explorer

Explore codebase for UI component patterns, state management conventions, and framework-specific patterns. Callable by coordinator only.

Phase 2: Exploration Scope

Parse exploration request from task description
Determine file patterns based on framework:

Wisdom Input

Read <session>/wisdom/patterns/ui-feedback.md and <session>/wisdom/patterns/state-management.md if available
Use known patterns as reference when exploring codebase for component structures
Check <session>/wisdom/anti-patterns/common-ux-pitfalls.md to identify problematic patterns during exploration

Framework	Patterns
React	`*/.tsx`, `*/.jsx`, `*/use.ts`, `*/store.ts`
Vue	`*/.vue`, `*/composables/.ts`, `*/stores/.ts`

Check exploration cache: <session>/explorations/cache-index.json
- If cache hit and fresh -> return cached results
- If cache miss or stale -> proceed to Phase 3

Phase 3: Codebase Exploration

Use ACE search for semantic queries:

mcp__ace-tool__search_context(
  project_root_path="<project-path>",
  query="<exploration-query>"
)

Exploration dimensions:

Dimension	Query	Purpose
Component patterns	"UI components with user interactions"	Find interactive components
State management	"State management patterns useState ref reactive"	Identify state conventions
Event handling	"Event handlers onClick onChange onSubmit"	Map event patterns
Error handling	"Error handling try catch error state"	Find error patterns
Feedback mechanisms	"Loading state spinner progress indicator"	Find existing feedback

For each dimension, collect:

File paths
Pattern examples
Convention notes

Phase 4: Exploration Summary

Generate pattern summary and write to <session>/explorations/exploration-summary.md
Cache results to <session>/explorations/cache-index.json

Wisdom Contribution

If new component patterns or framework conventions discovered:

Write pattern summaries to <session>/wisdom/contributions/explorer-patterns-<timestamp>.md
Format: Pattern Name, Framework, Use Case, Code Example, Adoption

Share state via team_msg:

team_msg(operation="log", session_id=<session-id>, from="explorer",
         type="state_update", data={
           framework: <framework>,
           components_found: <count>,
           patterns_identified: [<pattern-list>]
         })

2.6 KiB Raw Blame History