/data-management-plan, Funder-Compliant DMP Generator

Produce a Data Management Plan ready to paste into a funder portal. This skill writes the prose and structure; it does not submit anywhere. It is a composition skill, it folds the disclosure-avoidance / IRB rules from .claude/rules/confidential-data.md and the environment + replication-package plan from /capture-environment and /replication-package into a single funder-shaped document.

When to use

• Writing a grant proposal. Every NSF, NIH, ERC, and Horizon Europe proposal needs a DMP (NSF), DMS Plan (NIH 2023 policy), or Data Management Plan (ERC/Horizon). /grant-proposal follows this skill for that section, through an Agent that reads this SKILL.md (the skill is user-invoked only, so it is followed, not invoked).
• Before data collection on a funded project. The plan is a commitment you make at award time and report against at renewal.
• When restricted or human-subjects data is involved. The access/sharing and preservation sections change materially, see Phase 2.

When NOT to use

• For a clinical-trial data-sharing statement governed by ICMJE / ClinicalTrials.gov, use the trial sponsor's template.
• As a substitute for IRB protocol text, the DMP references IRB constraints; it is not the protocol itself.

Inputs

• $0 --funder nsf|nih|erc|horizon, target funder profile. If omitted, Phase 0 detects it from --input or asks once.
• --input <path>, a research spec (/interview-me output under quality_reports/specs/), a grant draft, or a passport-adjacent description. The skill extracts data types, sample, and identification strategy from it.
• --no-verify, skip the Phase 4 citation/standard post-flight (inherited from /preregister).

Workflow

Phase 0, Detect funder + data sensitivity

1. Resolve the funder (--funder, else infer from --input, else ask once). Load its section schema: