openclaw-agent45-workflow

Orchestrate end-to-end OpenClaw workflows for RISC-V software ecosystem optimization tasks.

3|1|Updated Jun 14, 2025
One-click install
npx skills add https://github.com/zcxGGmu/linux-riscv-docs --skill openclaw-agent45-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-agent45-workflow
Source: https://github.com/zcxGGmu/linux-riscv-docs/tree/main/agent/yuansheng-claw/plugin-skills/codex/openclaw-agent45-workflow
Command: npx skills add https://github.com/zcxGGmu/linux-riscv-docs --skill openclaw-agent45-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

OpenClaw Agent4/Agent5 Workflow orchestrates end-to-end planning, implementation, and follow-up for RISC-V software ecosystem optimization tasks, coordinating Agent4 and Agent5 processes to deliver structured patches, validation, and community feedback loops.

Core Features & Use Cases

  • End-to-end workflow orchestration for RISC-V optimization tasks across knowledge ingestion, spec digestion, task decomposition, and acceptance checkpoints.
  • Coordination of Agent4 (planning, implementation, self-test) and Agent5 (CI triage, patch iteration, submission) to close feedback loops.
  • Trigger patterns and practical use cases: when a user asks to take ownership of a task, plan a rollout, or manage patch submission and review workflows.

Quick Start

Describe your RISC-V optimization task and request end-to-end ownership to trigger an Agent4/Agent5 workflow takeover.

Frequently Asked Questions about openclaw-agent45-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate RISC-V software optimization tasks end-to-end?

Automate RISC-V software optimization tasks end-to-end by triggering a workflow that handles planning, implementation, self-testing, and patch resubmission. This enforces a stage-based plan with inputs, constraints, and evidence to deliver structured patches and community-facing artifacts.

What is the best way to manage CI failure triage and patch resubmission for RISC-V?

Manage CI failure triage and patch resubmission for RISC-V by coordinating Agent5 patterns within the workflow. It handles CI triage, patch iteration, and submission to close feedback loops and generate validated patch updates.

How does RISC-V workflow orchestration handle task decomposition and acceptance checkpoints?

RISC-V workflow orchestration handles task decomposition and acceptance checkpoints through a stage-based plan that coordinates knowledge ingestion and spec digestion. It enforces inputs, constraints, and evidence to generate test plans and community-facing artifacts.

Can I use this workflow to plan a rollout and take ownership of RISC-V ecosystem tasks?

You can use this workflow to plan a rollout and take ownership of RISC-V ecosystem tasks. Requesting end-to-end ownership triggers an Agent4 and Agent5 workflow takeover to manage planning, implementation, and community feedback loops.

Do I need specific dependencies to coordinate Agent4 and Agent5 workflows?

No specific dependencies are required to coordinate Agent4 and Agent5 workflows. The workflow operates standalone using references to orchestrate RISC-V optimization tasks, generating patch updates, test plans, and community-facing artifacts without external libraries.

Why does my RISC-V patch submission workflow lack structured validation and feedback loops?

RISC-V patch submission workflows lack structured validation when they do not enforce stage-based plans with acceptance checkpoints. Orchestrating Agent4 and Agent5 processes closes feedback loops by generating test plans, evidence, and community-facing artifacts.