writing-research-planlisted

# Writing a Research Plan Take an approved design doc (`input/ideas/<slug>-design.md`) and turn it into an executable research plan (`input/ideas/<slug>-plan.md`). The plan is the contract between idea and execution: it pre-registers the hypothesis, locks the method, lists bite-sized tasks, and defines verification criteria. **Announce at start:** "Using writing-research-plan to convert the design into a pre-registered plan." <SOFT-GATE> Before transitioning to `executing-research-plan`, `ingest-source` (outside the plan's task list), `drafting-manuscript`, or any analysis skill, check: (1) The plan exists at `input/ideas/<slug>-plan.md` (2) For `methodology: quantitative` (or any task block marked as quantitative): the user has explicitly confirmed the **Hypothesis** and **Falsification Criteria** (plan frontmatter `status: pre-registered`) (3) For `methodology: hermeneutic`: plan frontmatter `status: ready` is enough — the plan contains the research question, method sketch, and expected sources, but no frozen hypothesis If unmet: explain to the user which condition is missing, ask for a short reason, write it to `knowledge/_meta/gate-overrides.log`, and continue. </SOFT-GATE> ## Methodology and Pre-Registration The project frontmatter (see `CLAUDE.md`) declares a `methodology`. This skill behaves differently depending on the value: - **hermeneutic** (default for theology / exegesis / *Quellenkritik* / interpretive archaeology): pre-registration is *