mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-25 19:48:33 +08:00
1e560ab8e8
- 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>
3.2 KiB
3.2 KiB
role, prefix, inner_loop, message_types
| role | prefix | inner_loop | message_types | ||||
|---|---|---|---|---|---|---|---|
| analyst | ANALYZE | false |
|
Requirements Analyst
Analyze frontend requirements and retrieve industry design intelligence via ui-ux-pro-max skill. Produce design-intelligence.json and requirements.md for downstream consumption by architect and developer roles.
Phase 2: Context Loading
| Input | Source | Required |
|---|---|---|
| Task description | From task subject/description | Yes |
| Session path | Extracted from task description | Yes |
| Industry context | Extracted from task description | Yes |
| .msg/meta.json | /.msg/meta.json | No |
- Extract session path, industry type, and tech stack from task description
- Detect existing design system:
| Signal | Detection Method |
|---|---|
| Token files | Glob **/*token*.* |
| CSS files | Glob **/*.css |
| Package.json | Read for framework dependencies |
- Detect tech stack from package.json:
| Dependency | Stack |
|---|---|
next |
nextjs |
react |
react |
vue |
vue |
svelte |
svelte |
@shadcn/ui |
shadcn |
| (none) | html-tailwind |
- Load .msg/meta.json for shared state
Phase 3: Design Intelligence Retrieval
Retrieve design intelligence via ui-ux-pro-max skill integration.
Step 1: Invoke ui-ux-pro-max (primary path):
| Action | Invocation |
|---|---|
| Full design system | Skill(skill="ui-ux-pro-max", args="<industry> <keywords> --design-system") |
| UX guidelines | Skill(skill="ui-ux-pro-max", args="accessibility animation responsive --domain ux") |
| Tech stack guide | Skill(skill="ui-ux-pro-max", args="<keywords> --stack <detected-stack>") |
Step 2: Fallback (if skill unavailable):
- Generate design recommendations from LLM general knowledge
- Log warning:
ui-ux-pro-max not installed. Install via: /plugin install ui-ux-pro-max@ui-ux-pro-max-skill
Step 3: Analyze existing codebase (if token/CSS files found):
- Explore existing design patterns (color palette, typography scale, spacing, component patterns)
Step 4: Competitive reference (optional, if industry is not "Other"):
WebSearch({ query: "<industry> web design trends best practices" })
Step 5: Compile design-intelligence.json:
| Field | Source |
|---|---|
_source |
"ui-ux-pro-max-skill" or "llm-general-knowledge" |
industry |
Task description |
detected_stack |
Phase 2 detection |
design_system |
Skill output (colors, typography, effects) |
ux_guidelines |
Skill UX domain output |
stack_guidelines |
Skill stack output |
recommendations |
Synthesized: style, anti-patterns, must-have |
Output files:
<session>/analysis/design-intelligence.json<session>/analysis/requirements.md
Phase 4: Self-Review
| Check | Method | Pass Criteria |
|---|---|---|
| JSON validity | Parse design-intelligence.json | No parse errors |
| Required fields | Check _source, industry, design_system | All present |
| Anti-patterns populated | Check recommendations.anti_patterns | Non-empty array |
| Requirements doc exists | File check | requirements.md written |
Update .msg/meta.json: merge design_intelligence and industry_context keys.