← ClaudeAtlas

arcade-collablisted

Structured guidance for agents to read, classify, and act on user feedback (annotations and direct file edits) from the Arcade.
rp1-run/rp1 · ★ 38 · AI & Automation · score 77
Install: claude install-skill rp1-run/rp1
# Arcade Collaboration Process user feedback from the Arcade: annotations and direct file edits. Follow the loop below exactly, then return control to the calling gate. ## 1. Read Feedback Fetch all open feedback for the current run: ```bash rp1 agent-tools feedback read --run-id {RUN_ID} --status open ``` Parse the JSON response. It contains: - `annotations[]`: Open annotations with id, docId, artifactPath, content, anchor, status, author, replies, createdAt. - `edits[]`: Pending file edits with docId, artifactPath, patch (unified diff). - `summary`: Counts of totalAnnotations, totalEdits, and byArtifactType breakdown. **If both `totalAnnotations` and `totalEdits` are zero**: No pending feedback. Return to the calling gate immediately. Do not produce any output about the feedback check. ## 2. Classify Feedback Classify each feedback item by the artifact it targets: | Artifact Pattern | Classification | Routing | |------------------|---------------|---------| | `requirements.md` | Requirements feedback | Spawn `feature-editor` agent | | `design.md`, `design-decisions.md` | Design feedback | Spawn `feature-editor` agent | | Code files (`.ts`, `.tsx`, `.js`, `.jsx`, `.py`, `.rs`, etc.) | Code feedback | Apply fix directly | | Other files or unanchored annotations | General feedback | Incorporate into context, acknowledge | For **annotations**: classify based on `artifactPath`. If `artifactPath` is null (unanchored), classify as General. For **edits**: classify based