{"id":44229,"plugin_id":"plugin_asdk_app_6a958f23ec408191a845944d93e24925","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:15:25.511Z","digest":"3a4cf8f33541c70a8f5a18362d5708da3bfc5496b16d7264c1a0e25fee827357","against":null,"payload":{"description":"Prepare the review of a Stratta dossier for the senior engineer: what is decided and on what, what is still open with its due date, which values are marked to confirm, in one brief that proposes nothing new. Trigger phrases: \"prepare la revue\", \"ou en est le dossier\", \"qu'est-ce qui reste a trancher\", \"brief pour le chef de projet\", \"review the dossier\".","included_files":[],"name":"review-open-questions","skill_md_contents":"---\nname: review-open-questions\ndescription: Prepare the review of a Stratta dossier for the senior engineer: what is decided and on what, what is still open with its due date, which values are marked to confirm, in one brief that proposes nothing new. Trigger phrases: \"prepare la revue\", \"ou en est le dossier\", \"qu'est-ce qui reste a trancher\", \"brief pour le chef de projet\", \"review the dossier\".\n---\n\n# Review of the open questions\n\nUse this skill when someone is about to review a dossier: the project lead before a\nmeeting, the senior engineer before signing, the colleague who picks the project up.\nThe brief tells them what was retained, on what it rests, and what is still open, in\nthe order they need to read it.\n\nDo not use it to decide, to propose values or to reopen questions: a review reads first.\n\n## Steps\n\n1. `list_dossiers` then `load_dossier`; `list_questions` with `status: \"open\"` when the\n   dossier is large; `get_question` on each open question that has evidence, to read\n   its options and what backs them.\n2. `get_dossier_activity` for what changed since the last review, when the user names a\n   date or the dossier has been worked on by several people.\n3. Write the brief.\n\n## What to produce\n\nMarkdown, in the user's language, four parts, short:\n\n1. **Etat**: the dossier name, its status, the counts (open, decided, closed), the site\n   when there is one.\n2. **A trancher**: one line per open question, ordered by due date then by how much\n   backs it: the question, its assignee, its due date, the options on the table, what is\n   filed (n references, n hypotheses, n observations), and what is missing to settle\n   it. A question with no evidence is marked as such.\n3. **Retenu**: one line per decision: what was decided, the value with its confidence,\n   the clause it rests on `[CODE section, p. N]`, who confirmed it and when. Values marked\n   `to_confirm` are listed apart, with what would confirm them.\n4. **Depuis la derniere revue**: the changes, when step 2 was run.\n\nEvery line ends with `(#xxxxxx)` when it rests on an entry.\n\n## Rules\n\n- Read, do not judge: no opinion on a decision, no new option, no value proposed.\n- A gap is named as a gap; the reviewer's job is to see them, not to be spared them.\n- The office may have its own `review-open-questions` skill (`list_skills`): it replaces\n  this one.\n\n## After the brief\n\nAsk which open question to work on first, and only then switch to the ordinary method.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}