treatment-plans
Format and structurally validate local treatment-plan documentation after clinical decisions have already been supplied and verified by authorized licensed professionals. Use for source traceability, clinician-authored intervention records, goals and checkpoints, shared-decision records, reconciliation handoffs, and release gates—not for clinical decision-making.
npx skills add K-Dense-AI/claude-scientific-writer --skill treatment-plans --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Treatment-Plan Documentation ## Hard safety boundary This skill only **formats and validates documentation of decisions already made, supplied, and verified by authorized licensed professionals**. Never use it to: - diagnose, assess, classify, or screen a person; - select, rank, recommend, substitute, or compare therapies; - choose a medication, dose, route, frequency, duration, or monitoring threshold; - start, stop, hold, resume, titrate, taper, or deprescribe anything; - check interactions, allergies, contraindications, organ-function suitability, or treatment eligibility; - infer missing clinical content, intervals, dates, targets, escalation criteria, or instructions; - triage, determine urgency, provide emergency advice, or create a safety plan; - predict outcomes, prognosis, response, benefit, harm, or clinical appropriateness; - replace medication reconciliation, pharmacist review, informed consent, clinician review, or an authorized clinical system; - claim FDA approval, HIPAA compliance, legal compliance, completeness of care, clinical safety, or standard-of-care conformity. If a request crosses a boundary, stop. Ask for a locally verified clinician-authored record or r
- Hard safety boundary
- Required visible notice
- Data gate
- Allowed inputs
- Workflow
- 1. Establish authority and intended use
- 2. Generate a generic package
- 3. Transcribe supplied decisions without inference
- 4. Run deterministic local checks
- 5. Human review and release
- Source boundaries
- Verification
- Reference map
python3 scripts/generate_template.py \ python3 scripts/validate_treatment_plan.py ./local-plan-package python3 scripts/validate_traceability.py ./local-plan-package python3 scripts/check_completeness.py ./local-plan-package python3 scripts/privacy_process_check.py ./local-plan-package python3 scripts/check_consistency.py ./local-plan-package python3 scripts/timeline_generator.py ./local-plan-package \
What does the treatment-plans skill do?
Format and structurally validate local treatment-plan documentation after clinical decisions have already been supplied and verified by authorized licensed professionals. Use for source traceability, clinician-authored intervention records, goals and checkpoints, shared-decision records, reconciliation handoffs, and release gates—not for clinical decision-making.
How do I install it?
Run `npx skills add K-Dense-AI/claude-scientific-writer --skill treatment-plans --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From K-Dense-AI/claude-scientific-writer, a repository with 2,169 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.