report

Files (1)

• SKILL.md

SKILL.md (first lines)

Load and follow the [Mops skill](../mops/SKILL.md), executing its `/multica-team:report` flow — the procedure is in [`SECURITY.md`](../../operations/SECURITY.md) → *Reporting a defect in this skill*.

Something went wrong, or made the work harder than it needed to be. **You do not have to know whose defect it is** — that is the first thing this decides, and it decides it from the evidence rather than asking you to classify your own frustration.

**A defect in your product** is the urgent lane and belongs to `/multica-team:bug`: reproduced before it is fixed, straight to Build and Review. **Friction in your workspace** — a flow that fought you, a step that repeats — becomes a field note in `_ops/FIELD-NOTES.md`, one line, swept at the checkpoints PLAYBOOKS names — session end, `/multica-team:status`, before a release cut; a second occurrence earns an issue with both occasions named. **Friction in this skill or in Multica itself** is assembled from evidence — version, flow, symptom, the task record, the state of the files involved — de-identified, and **written whole to a file outside your repository — written first, with anything missing marked `unknown`, never held back waiting for a field**, with its path said out loud and the ways to send it named. Publishing is yours: the file is made here, you post it.

Use the invocation arguments and accompanying user message as the request.

From junjiezhou1122/multica-team, MIT.

More from junjiezhou1122/multica-team