project-collaboration-operating-system

Project Collaboration Operating System

Overview

Use this skill to govern a project's human-AI collaboration system. It makes collaboration context discoverable, authority clear, scope controlled, completion verifiable, and drift correctable.

This is not a product strategy skill, PRD generator, roadmap planner, market research workflow, or full lifecycle advisor.

Use templates/invocation.md only when the user needs a copyable invocation prompt.

Thinking Principle

Treat the user's proposal and your own first judgment as hypotheses, not conclusions.

Look for evidence that weakens the current judgment before strengthening it.

Revise the judgment when evidence changes; change the collaboration system only when evidence justifies a durable change.

Core Operating Model

Run this exact chain for every mode:

Select mode
-> Context
-> Authority
-> Scope
-> Diagnosis
-> Minimal Change
-> Verification
-> Correction

• Select mode: Route the request to Bootstrap, Audit, Improve, or Retrospective.
• Context: Inspect entrypoints, docs, code reality, local notes, known decisions, uncommitted work, and the user's latest instruction.
• Authority: Separate binding rules, explanatory docs, temporary notes, stale content, inferred ideas, and suggestions.
• Scope: Confirm the active stage and deferred capabilities.
• Diagnosis: Classify the need or failure before changing docs or process.
• Minimal Change: Prefer clarification, links, deduplication, status marking, or authority cleanup over new documents.
• Verification: Check that the intended future behavior is discoverable and evidence-backed.
• Correction: Preserve only durable learning in formal docs, decision records, local context policy, or workflow.

Route To A Mode

Route first, then run the core operating model:

Signal	Mode
No stable collaboration context, repository entrypoint, or agent boundary exists; input is mostly ideas, chats, screenshots, rough notes, or partial code	bootstrap
Existing project/docs need diagnosis or the user asks what the current collaboration system looks like	audit
A known collaboration gap, documentation problem, or workflow upgrade is requested	improve
A real miss, drift, repeated failure, skipped verification, fake completion, or correction event occurred	retrospective