critty-ai-cowork

Cowork with Another AI

Experimental: interfaces and supported launch configurations may change.

Read critty-ai-review and follow its requester workflow, request identity, snapshot, posting, and completion contracts. This skill changes only how the requester acts between AI review rounds. Keep its reviewer role unchanged.

A request such as /critty-ai-cowork with Astra selects a collaborator for the current task and authorizes in-scope fixes and follow-up between agents. Follow the shared skill's with argument handling. Establish the target outcome and acceptance checks before dispatch, using existing task context. If the request only asks for an opinion, use critty-ai-review instead. Preserve the user's selected collaborator and the caller's execution permissions.

Replace the per-round checkpoint

After collecting and verifying each AI result:

1. Assess the findings against the requirements and evidence. Exchange focused questions or counterexamples with the reviewer when needed; agreement alone is not evidence of correctness.
2. Make authorized fixes and run the affected checks as the requester. The other AI reads, posts findings, replies to its own threads, and resolves its own verified findings through the restricted Critty interface; it does not edit files or execute checks.
3. Capture the revised target and request review of the affected scope, explicitly carrying forward unresolved findings and permitting the reviewer to resolve its own findings after verification. Reuse valid results for unchanged content. Keep each assignment tied to its own version and completion report.

For a one-shot reviewer that has exited, continue an exchange by posting the requester's question or evidence as a reply, then launching a new assignment with a new request ID and references to that thread and the prior result. A live transport may continue on its existing handle. An exited process cannot receive another question merely by waiting on it.