document-safety-committee-decisions
SolidRecords or reviews a safety or escalation committee decision so it can be understood a year later or by an inspector. It requires the decision to name exactly one action and flags wording that permits more than one, verifies quorum against the charter rather than inferring it from attendance, keeps decision date and data cut-off as separate fields, and traces every fact in the stated basis back to the pack the committee actually saw so knowledge drawn from outside the record is flagged rather than lost. It also preserves dissent and names who verifies each condition. Use it immediately after a meeting, before filing, or to reconstruct a past decision. Example: "Please assembling the pack, for the escalation design, for agency meeting minutes." Do not use for assembling the pack, for the escalation design, for agency meeting minutes, or to make or endorse the decision.
Install
Quality Score: 84/100
Skill Content
Details
- Author
- malekokour
- Repository
- malekokour/clinpharm-pmx-skills
- Created
- 1 weeks ago
- Last Updated
- 6 days ago
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
record-decision
Use when recording an architecture or structural decision. Captures the context, the decision, and the consequences as a short, append-only record so the why survives.
decision-record
Use when writing a new decision record (an ADR, or whatever the project calls its decisions artefact) or fleshing out one that is still planned. Covers classifying the change — new versus amendment versus superseding — the required structure and house style, the branch → Proposed → review-with-open-questions → Accepted → merge cycle, and the index and status updates. Not for implementation work.
decision-capture
Use when recording, updating, accepting, or superseding a durable project decision that constrains future work, including a maintainer's promotion of an already-recorded policy-level verification observation. Covers tracked Markdown decision records under .agenticloop/decisions/, maintainer ownership, proposed vs accepted state, source-linked discoverability, supersession, and decision.recorded events.