.claude/skills/glm5-parallel/SKILL.md
Model-agnostic parallel execution with Agent Teams coordination
npx skillsauth add alfredolopez80/multi-agent-ralph-loop glm5-parallelInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Model-agnostic parallel execution with Agent Teams coordination for comprehensive task execution.
Note: Despite the name, this skill is model-agnostic as of v2.88.0. It works with any model configured in Agent Teams.
/glm5-parallel <task> [--roles coder,reviewer,tester]
/glm5-parallel "Implement OAuth2 authentication" --roles coder,reviewer,tester
This spawns 3 teammates:
# Generate task ID
TASK_ID="parallel-$(date +%s)"
# Parse roles
ROLES="coder,reviewer,tester"
# Spawn in parallel
for ROLE in $(echo $ROLES | tr ',' ' '); do
.claude/scripts/glm5-teammate.sh "$ROLE" "<task>" "${TASK_ID}-${ROLE}" &
done
# Wait for all
wait
# Aggregate results
for ROLE in $(echo $ROLES | tr ',' ' '); do
echo "=== $ROLE ==="
cat .ralph/teammates/${TASK_ID}-${ROLE}/status.json | jq '.output_summary'
done
If no --roles specified:
coder - Implementationreviewer - Code reviewtester - Test generationCreates parallel status files:
.ralph/teammates/{task_id}-coder/status.json.ralph/teammates/{task_id}-reviewer/status.json.ralph/teammates/{task_id}-tester/status.jsonAggregated in .ralph/team-status.json
Optimal Scenario: Pure Agent Teams (Native)
This skill uses Pure Agent Teams with native coordination - no custom subagent specialization needed.
TeamCreate
→ Task(prompt, subagent_type) for each parallel workstream
→ Native agents execute in parallel
→ Aggregate results
→ Complete
// Create team for coordination
TeamCreate(team_name="parallel-{timestamp}", description="Parallel execution for: {task}")
// Spawn native agents in parallel
const workstreams = [
{ task: "Implement feature X", files: ["src/a.ts"] },
{ task: "Implement feature Y", files: ["src/b.ts"] },
{ task: "Write tests", files: ["tests/*.test.ts"] }
];
workstreams.forEach(work => {
Task(
subagent_type="coder", // Native agent type
team_name="parallel-{timestamp}",
input=work
);
});
Esta skill genera reportes automáticos completos para trazabilidad:
Cuando esta skill completa, se genera automáticamente:
docs/actions/glm5-parallel/{timestamp}.md.claude/metadata/actions/glm5-parallel/{timestamp}.jsonCada reporte incluye:
# Listar todos los reportes de esta skill
ls -lt docs/actions/glm5-parallel/
# Ver el reporte más reciente
cat $(ls -t docs/actions/glm5-parallel/*.md | head -1)
# Buscar reportes fallidos
grep -l "Status: FAILED" docs/actions/glm5-parallel/*.md
source .claude/lib/action-report-lib.sh
start_action_report "glm5-parallel" "Task description"
# ... ejecución ...
complete_action_report "success" "Summary" "Recommendations"
development
Living knowledge base management. Actions: search (query vault), save (store learning), index (update indices), compile (raw->wiki->rules graduation), init (create vault structure). Follows Karpathy pipeline: ingest->compile->query. Use when: (1) searching accumulated knowledge, (2) saving learnings, (3) compiling raw notes into wiki, (4) initializing a new vault. Triggers: /vault, 'vault search', 'knowledge base', 'save learning'.
testing
Produce a verifiable technical specification before coding. 6 mandatory sections: Interfaces, Behaviors, Invariants (from Aristotle Phase 2), File Plan, Test Plan, Exit Criteria (executable bash commands + expected results). Use when: (1) before implementing features with complexity > 4, (2) as Step 1.5 in orchestrator workflow, (3) when requirements need formalization. Triggers: /spec, 'create spec', 'write specification', 'technical spec'.
testing
Pre-launch shipping checklist orchestrating /gates, /security, /browser-test, /perf. Ensures nothing ships without passing all quality checks. Use when: (1) before deploying, (2) before merging to main, (3) before release. Triggers: /ship, 'ship it', 'ready to deploy', 'pre-launch check'.
development
Performance optimization skill. Core Web Vitals via Lighthouse, bundle size analysis, metrics tracking over time. Use when: (1) optimizing frontend performance, (2) analyzing bundle size, (3) tracking metrics regression. Triggers: /perf, 'performance audit', 'core web vitals', 'bundle size'.