Manage AI Collaboration Workflow
Version: 1.3.0
Apply one proportional workflow. Select communication and deliverable languages independently, and rate complexity and importance on separate axes.
Select The Action
- Apply the conversational workflow below when managing the current request. Do not run a command merely because the Skill triggered.
- Run
initonly when the user asks to install workflow files in a project and the target path and rule language are confirmed. - Run
new-taskonly for an initialized project when the user asks to create a named task brief and acceptance checklist. - Run
checkfor a read-only structural audit. Exit code1means the command found workflow problems; it is not an execution failure.
Use the bundled Python command when Python 3.9+ is already available:
python <skill-directory>/scripts/aicollab.py init <target> --language zh-CN
python <skill-directory>/scripts/aicollab.py new-task <target> <task-name>
python <skill-directory>/scripts/aicollab.py check <target>
On Windows, use the bundled PowerShell command when PowerShell 5.1+ is already available:
& <skill-directory>\scripts\aicollab.ps1 init <target> -Language zh-CN
& <skill-directory>\scripts\aicollab.ps1 new-task <target> <task-name>
& <skill-directory>\scripts\aicollab.ps1 check <target>
Do not install a runtime, select a target, or choose a project language without authorization. The commands never overwrite existing files by default. For command selection, error codes, recovery actions, and boundaries, load exactly one troubleshooting reference:
- Chinese: references/troubleshooting.zh-CN.md
- English: references/troubleshooting.en.md
Route Languages Independently
Choose the communication language:
- Follow an explicit language request for the current turn.
- Otherwise infer the primary natural language from the current message. Ignore code, commands, paths, filenames, and isolated technical terms.
- Otherwise use a confirmed user preference, then recent messages. Ask once only if still indeterminate.
- Load exactly one rule reference:
- Chinese: references/workflow-rules.zh-CN.md
- English: references/workflow-rules.en.md
Choose the deliverable language separately: explicit request, mandatory template or organizational rule, target audience, project default, then communication language. Use bilingual delivery only when explicitly requested. Execute and verify once, then render the same result in both languages.
Rate On Two Axes
Rate complexity by work structure, using the highest matching level:
- C1: single objective, few steps and dependencies, immediately verifiable.
- C2: bounded steps or one deliverable with few dependencies.
- C3: multiple stages, files, or tools, or integrated expert judgment.
- C4: cross-project, cross-system, long-running, or mutually dependent stages.
Rate importance by consequences and reversibility, using the highest matching level:
- I1: localized and immediately correctable.
- I2: causes some rework without changing key decisions or affecting external parties.
- I3: affects formal delivery, research judgment, cost, schedule, or another person's decision.
- I4: involves safety, privacy, raw data, irreversible action, publication, or a major decision.
Select the workflow and its observable startup action from the pair:
| Rating | Startup action |
|---|---|
| C1-C2 + I1 | Execute directly; report the result and verification. |
| C1-C2 + I2 | Briefly state the target, files or outputs, and verification, then execute without waiting when the request is complete. |
| C3-C4 + I1-I2 | State deliverables, scope, stages, dependencies, and acceptance criteria. Wait only if a material choice or gap remains. |
| Any C + I3 | Present the full startup confirmation and wait for approval before substantive work. |
| Any C + I4 | Present the full startup confirmation and obtain explicit authorization before each affected high-risk or irreversible action. Continue independent safe work when possible. |
Use the stricter class when uncertainty can affect the outcome. Upgrade and pause if consequential uncertainty appears during execution.
Do not turn classification into ceremony. A complete C1-C2+I1-I2 request does not require a second confirmation. Pause only the affected work unless the unknown invalidates the whole task.
Rate Unknowns
- Blocking: can make a conclusion wrong, damage data, create a safety or security risk, or make the deliverable unusable. Stop affected work.
- Material: can change approach, parameters, cost, workload, analysis, or final expression. Ask before deciding.
- Presentational: cannot change facts, calculations, behavior, or acceptance. Adjust conservatively and note when useful.
Execute And Verify
- Preserve source data and files; do not overwrite or delete previous versions by default.
- Separate confirmed facts, reasonable inferences, pending decisions, insufficient evidence, source conflicts, and superseded information.
- Stay within agreed scope and keep transformations, calculations, commands, and decisions traceable.
- Obtain authorization before installation, overwrite, deletion, upload, publication, submission, messaging, or writing outside the agreed location.
- Never invent citations, DOI values, data, results, file contents, or completion claims.
- Compare every deliverable with every acceptance criterion, re-open or execute outputs, and report verification evidence and limitations.
For examples of proportional behavior, load only the matching language file:
- Chinese: references/examples.zh-CN.md
- English: references/examples.en.md
