Sevo Pipeline

SEVO — Agent 研发流水线。Spec-Execute-Verify-Operate: the agentic software delivery lifecycle for AI agent software production. Covers 8 stages from specification...

What to consider before installing: - This package is a full OpenClaw plugin (not just a tiny instruction). It expects to be installed into the host workspace and will read/write files there (pipeline state, events, possibly project artifacts). Review where it will be placed (typical path: ~/.openclaw/extensions/sevo-pipeline and ~/.openclaw/workspace). - The plugin injects text into the main session (before_prompt_build) to request that the host spawn subagents; it deliberately uses prompt injection (documented ADR). That is a design choice: it avoids directly calling spawn APIs but relies on the main session/model to obey the injected instructions. If you run in a sensitive environment, this increases risk — a model could be coerced or misled by injected content. Consider running in a sandboxed host first. - The bridge dynamically imports compiled JS from the workspace/dist path and constructs/instantiates engine classes at runtime. That means code present under the workspace can be executed with plugin privileges. Make sure the workspace and any dist artifacts are trusted and immutable (or verify builds) before enabling. - Metadata underreports the footprint (no required env vars/config paths declared), but the code reads env vars and resolves config paths. Expect to configure OPENCLAW_WORKSPACE_ROOT / OPENCLAW_SEVO_* or confirm default locations. Confirm there are no unexpected env variables or secrets in those paths. - Recommended actions: (1) review the included source (bridge.js, index.js, label-protocol.js, task-mapper.js, and the hooks) to ensure behavior matches policy; (2) install and test in an isolated OpenClaw sandbox environment first; (3) ensure no secrets are present in the target workspace; (4) consider pinning/locking the dist compiled artifacts or running sevo build steps yourself and auditing the resulting JS; (5) if you don't want automatic prompt-driven spawning, disable or override the before_prompt_build hook or run in Single-Agent Mode with manual approval. Confidence note: The assessment is based on code and SKILL.md provided. If you can provide the OpenClaw host policy, exact installation path, and any intended env var overrides, I can raise or lower concern levels — e.g., if you plan to install into a disposable test host the risk is lower.

Type: OpenClaw Skill Name: sevo-pipeline Version: 0.4.1 The SEVO pipeline is a highly sophisticated and well-architected framework designed to manage the full software delivery lifecycle for AI agents. It consists of a core TypeScript engine, an OpenClaw plugin for automated stage advancement, and a Next.js-based management dashboard. While the bundle performs high-privilege operations—such as modifying the host's 'openclaw.json' to enable prompt injection hooks (init.sh) and programmatically appending role-specific constraints to other agents' 'SOUL.md' files (role-templates.js)—these actions are transparently implemented and essential for the framework's stated purpose of coordinating multi-agent workflows. The code follows security best practices, such as using timing-safe comparisons for authentication and implementing 'fail-open' wrappers for hooks to ensure host stability. No evidence of malicious intent, data exfiltration, or unauthorized remote execution was detected.