Back to skills
Regulatory & Quality

Ra Qm Skills

Ra Qm Skills: Choose a regulatory or quality workflow. Review product type, market, lifecycle stage, responsible person, and immediate decision and produce a regulatory quality work plan.

---
name: ra-qm-team-ra-qm-skills
description: Use for ra qm skills when asked to choose a regulatory or quality workflow; produce a regulatory quality work plan.
license: MIT
metadata:
  author: Thrive
  category: ra-qm-team
---

# Ra Qm Skills

## When to use

Use this skill for ra qm skills when you need to choose a regulatory or quality workflow. The expected result is a regulatory quality work plan.

## Boundaries

Work within the requested task and its stated acceptance criteria. Drafting an artifact does not authorize publishing it, spending funds, changing a live system, or contacting another person. Identify any such action separately before taking it.

## Inputs

Inspect product type, market, lifecycle stage, responsible person, and immediate decision. Resolve missing information that would change the method; state lesser assumptions in the result.

## Method

1. **Diagnose.** Set product, jurisdiction, lifecycle stage, applicable framework, record owner, and evidence location.
2. **Decide.** Route the task to the relevant regulatory, risk, audit, or document process.
3. **Produce.** Build a regulatory quality work plan from the inspected material; keep assumptions distinguishable from observed facts.

## Decision rules

- Trace each requirement to the risk it controls and the documented proof that the control works. Mark missing or outdated evidence.
- When sources or constraints conflict, record the conflict and choose the path supported by the user's goal and the strongest available evidence. If neither path can be supported, identify the missing decision before changing the artifact.

## Domain rules

- Preserve traceability between requirement, risk, control, and validation evidence.
- Confirm jurisdiction and lifecycle stage before applying a regulated checklist.

## Verification

Verify the chosen framework and flag qualified review. Compare the result with the user's acceptance criteria and record any unverified boundary.

Produce a review matrix with requirement, source, owner, evidence, gap, and qualified-review decision.

## Evidence and stop conditions

- Verify current authoritative sources for rules, prices, clinical claims, or obligations that can change. Distinguish fact, interpretation, and assumption.
- Stop before an external action or regulated judgment without the required authorization or qualified reviewer.
- When evidence is materially missing or conflicting, state the uncertainty and the exact source or decision needed to proceed.

## Stop conditions

If a material input, required authorization, or a safe way to verify the result is absent, stop the affected action. Return the specific blocker and the smallest fact or decision needed to continue. Do not report an unrun check as passed.

## Output

Provide a regulatory quality work plan. Include the decisive evidence and actual verification result. Name any artifact location and unresolved issue that affects its use.

<!--
MIT License

Copyright (c) 2026 Thrive

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
-->