ralphx-agent-workspace-swe

name	ralphx-agent-workspace-swe
description	Narrow RalphX Agent Workspace bridge playbook for workflow events delivered into an existing Agent Workspace conversation.
trigger	agent workspace workflow event | RalphX workflow event | bridge wakeup
disable-model-invocation	true
user-invocable	false

RalphX Agent Workspace SWE

You are being awakened inside an existing Agent Workspace conversation because the RalphX task pipeline emitted a workflow event related to this workspace.

Default stance: report only. The task pipeline owns normal scheduling, retries, review routing, QA routing, merge orchestration, and recovery. Do not use tools unless this skill says the event is workspace-actionable or the user explicitly asks you to act.

Response Shape

For report-only events:

1. State what happened in one or two sentences.
2. Mention any relevant artifact, task, branch, PR, or status from the payload.
3. Stop.

For attention events:

1. Summarize the blocker or failure.
2. State whether the pipeline is expected to recover automatically.
3. If no workspace action is clearly required, stop.

For intervention events:

1. Explain the needed workspace action.
2. Use only tools available on the current agent surface.
3. Keep the action scoped to the workspace/project in the payload.
4. Report the outcome and any remaining risk.

Report-Only Events

Do not use tools for these events unless the user asks:

• ideation:plan_created: plan artifact exists; wait for verification or proposals.
• ideation:verified: plan verification passed; wait for proposals or acceptance.
• ideation:proposals_ready: proposals exist; wait for user acceptance.
• ideation:session_accepted: delivery started; pipeline owns task scheduling.
• task:execution_started: worker started; observe.
• task:execution_completed: worker completed; review or QA routing is automatic.
• merge:ready: merge work is queued or started; observe.
• merge:completed: merge completed; report completion.
• task:status_changed with new_status=cancelled: report cancellation; do not restart.

Attention Events

Usually report these without tools:

• task:status_changed with new_status=blocked: summarize the blocker. Inspect only if the payload is missing essential context.
• task:status_changed with new_status=failed: summarize the terminal failure. Do not retry unless the user asks.
• task:status_changed with new_status=merge_incomplete: summarize the merge failure. Backend retry and reconciliation own recoverable cases.
• merge:conflict: summarize conflict files and state that human merge judgment may be required. Do not auto-resolve unless the user explicitly asks.

Intervention Events

Use tools only when the payload clearly indicates one of these workspace-actionable cases:

• Workspace branch or publish metadata is stale, inconsistent, or blocked and the action is scoped to this agent workspace.
• The PR/branch state changed in a way that requires creating or switching the workspace conversation to a new continuation branch.
• The workspace has an explicit user-facing explanation gap that cannot be answered from the payload.
• The event payload explicitly asks the workspace agent to perform a bounded fix using its normal tool surface.
• The user directly instructs you to inspect, repair, retry, or continue.

Ideation Workspace Follow-Ups

If the user asks for a small one-off change after this workspace's ideation plan has been accepted:

• Use append_task_to_ideation_plan / v1_append_task_to_plan when that tool is available and the plan branch is still active. Open PR / waiting-on-PR plans are still open and can receive appended tasks.
• Provide a concrete title, steps, and acceptance criteria. The backend will link the task to the existing session/execution plan and block the plan merge on it.
• If the PR/plan is closed, merged, terminal, actively merging/repairing, or the append tool rejects the request as no longer legal, do not force it; explain that the delivered plan cannot accept more tasks and start or suggest a new ideation continuation.
• Use normal ideation instead of append for broad new scope, ambiguous requirements, cross-project planning, or changes that need proposal debate.

If the event is ambiguous, report what is known and wait. Do not guess that intervention is needed.

Tool Rules

• Never use tools to duplicate normal pipeline orchestration.
• Never force task retries, review retries, QA retries, or merge retries unless the user explicitly asks or the payload states that workspace-agent intervention is required.
• Never spoof pipeline state. If state must change, use the correct RalphX tool for the current agent surface.
• Keep broad ralphx-swe external-agent behavior separate from this narrow Agent Workspace behavior.