Coordinate the requested outcome

Read the shared workflow contract before substantive work. This skill is part of the locally installed Clarila suite. Its source is in ~/Developer/skills; resolve sibling skills relative to this directory.

Procedure

1. Resolve the requested issue and existing workflow before allocating anything. Read current repository instructions, GitHub state and the original Discord conversation as source evidence. Resolve a separate workflow thread in the configured Clarila server for progress updates; a source report in HeyAmara or another server is not the publishing destination. Preserve active writers and existing holds.
2. For local issue setup, implementation, resume, sync, list or requested cleanup, read the local issue workflow. Its deterministic helpers preserve issue/worktree identity and existing safety checks. Use clarila-branch and clarila-session for workspace/session responsibility.
3. Enter the complete pinned poteto-mode protocol, select its actual upstream playbook and retain the exact source steps in the existing task tracking/handoff. Keep this chat as outer coordinator and one accountable engineering owner through the bounded outcome. Execute triggered how, why, architect, arena, interrogate and other source procedures; Clarila role names bind responsibility and do not replace them with summaries. A clear issue needs the owner's inline plan and work, not a compulsory Research or standalone Plan worker. Add Test when strategy or test writing needs focused work; keep independent Verify and Review in separate actual contexts. For a UI change, include Capture: visible data/interaction changes count even if layout/styles are unchanged. Require before/after screenshots, a short real recording for an interactive flow and authorized uploaded evidence in the Clarila thread. Add Product, Plan, Design, Build, Security, Perf or Release only when acceptance requires them.
4. State a concise plan, perform authorized work, inspect complete upstream handoffs and reconcile actual results before selecting a dependent stage. A named role is not proof of an independent assessment. For workflows with Discord synchronization, record skill activity when the coordinator or a specialist actually begins, and clear it when that role stops.
5. For resume, recover the existing workspace, candidate, session, evidence and unknown effects. Continue the same work rather than creating another writer. Register the current session only after native identity is known.
6. When Discord synchronization is authorized, use Clarila Discord to publish each contributing specialist's own finding from its matching bot account in the same verified issue thread. Ask each specialist for a short, public-facing finding alongside its private evidence. Publish after each meaningful result or blocker, and record the actual author and receipt. Keep the issue summary with Clarila. Codex owns execution and delegation for this mode. Prepared publication uses the Go helper and needs no separate inference run.
7. Retain useful facts through clarila-obsidian. Finish with the requested outcome, checks, remaining limits and a concrete next action. Never start or resume other issues yourself; automatic starts come only from the control service in Auto mode.
8. When the Clarila control service started this turn, honor its admitted scope and stopping point. Leave the PR in draft and return the actual source-bound implementation evidence. The service owns independently observed Verify/Review assessments and any authorized readiness transition. Never mark the PR ready, manufacture assessment receipts, widen the admitted effects, or merge from the implementation context. Auto-ship merging remains the service's job after its verified gates and objection window.

Select the next stage

Keep the selected upstream source/hash and exact task steps in the existing handoff. Each active stage names its prerequisite evidence, responsible role, current source, completion signal and next action. Record source-permitted conditions, supported host mappings, named owner bindings and unavailable requirements distinctly; no generic skip reason completes mandatory work. Read the actual report and relevant artifact before accepting a result. A changed candidate marks affected checks stale and sends them back to their owning role. Optional fidelity inspection is a consistency diagnostic, never an independent verdict or service gate.

Select the route from the requested outcome. An investigation ends with the source-grounded answer; a bug needs its original failure and repaired result; a feature needs observable acceptance; a refactor preserves the affected contracts; performance work needs comparable measurements. Let one responsible engineer carry a complete bounded change. Add a separate Product, Plan, Design or Research stage only for a specific unresolved decision. Discover the repository's existing verifier and feature map through project verification; reuse an applicable control surface instead of recreating its launch and interaction scripts.

When a stage is blocked, record the missing input and the condition that permits continuation. Continue independent authorized preparation. Preserve an unknown writer or external operation with its original identity. Resume by rechecking that condition and the current candidate, then take the next eligible stage.

Synchronization and handoff

Resolve the same issue/workspace/session association before substantive work, including direct invocation. Read and update the private handoff described in the shared contract using available native file tools. Record the actual stage, source, findings, evidence, outcome and next action. If no native session identity is available, retain an unbound record. The installed background jobs mirror GitHub issues and publish presence. Start work by invoking the skill in Codex.

Deliverable

Return an issue-bound plan or completed scoped workflow, source coordinates, stage outcomes, evidence and next action.

Load only the relevant specialist from the catalog. Resolve additional technical methods through verified external expertise, with the pstack Codex adaptation controlling host-specific assumptions. Missing tools change the available evidence, never its meaning.