aops-collaborative-work

Orchestrates AOPS-backed agent work sessions with PM, memory, chat, and review workflows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/eeemzs/aops --skill aops-collaborative-work-eeemzs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aops-collaborative-work
Source: https://github.com/eeemzs/aops/tree/main/assets/skills/aops-collaborative-work
Command: npx skills add https://github.com/eeemzs/aops --skill aops-collaborative-work-eeemzs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents working on AOPS-backed projects lose context between sessions and lack a consistent discipline for tracking tasks, reviews, and decisions. This Skill provides a token-efficient startup playbook that keeps project management, memory checkpoints, and optional multi-agent coordination in one repeatable workflow. ## Core Features & Use Cases - Solo-first session playbook: Registers every task in PM before coding, uses the memory brief/checkpoint/summary loop, and validates work honestly with per-slice evidence. - Async review across sessions: Leaves PM review requests open so a future session can discover, review, and record findings as issues without a live reviewer. - Optional chat-room and multi-agent modes: Adds a hosted ChatV3 room for task intake and wake signals, standalone discuss rituals for design decisions, and a verify-first consensus-to-build recipe. - Use Case: An agent resumes a project by running the startup block, finds an open review request from a prior session, reviews the slice, records findings as PM issues, and checkpoints progress to memory. ## Quick Start Ask your agent to use aops-collaborative-work for your project slug to start a solo AOPS session with PM and memory discipline.

Frequently Asked Questions about aops-collaborative-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start an AOPS work session with an AI agent?▼

Run the token-efficient startup block: check sync status, view the dashboard, and call aops-cli start with your task in JSON mode. The result includes a memory brief and session guidance so you avoid bulk-loading guides.

How do I request a code review across agent sessions?▼

Create a PM review request with a review scope such as files or sprint at the end of your slice. A future session discovers it via the open review-request list, appends a result outcome, and records material findings as PM issues.

When should I use chat-room mode instead of solo mode?▼

Use chat-room mode only when the operator requests room-based task intake or a live peer. It adds a hosted ChatV3 room for coordination and wake signals on top of the same solo PM and memory discipline.

Does aops-collaborative-work require multiple agents to work?▼

No, solo mode is the default and needs only one agent with PM, memory, and doc discipline. Multi-agent coordination, chat rooms, and discuss rituals are optional layers activated only by explicit operator opt-in.

Why should decisions use standalone discuss instead of chat messages?▼

Chat rooms are coordination flow, not a decision ledger. Material design forks require a standalone discuss topic with independent stances, final stances, and a conclude step, with the consensus surfaced through PM feedback or bindings.