Back to catalogue

Research Proposal Flow

Researcher Official v1.1.29

Gap analysis, hypothesis generation, methodology design, and proposal drafting

by skrptiq

academic methodology proposal
workflow Updated 12 July 2026 7 nodes

Sign in to import this skrpt into your workspace.

Sign in
What's included 7 nodes
1 workflow 2 skills 2 prompts 1 source 1 document
workflow (1)

Research Proposal Flow

Gap analysis, hypothesis generation, methodology design, and proposal drafting

skills (2)

Hypothesis Generator

Generates testable hypotheses from the research gaps and existing findings.

Proposal Drafting

Drafts a complete research proposal from the gaps, hypotheses, and methodology.

prompts (2)

Hypothesis Generator

Generates testable hypotheses from research gaps and existing findings

Research Proposal Writer

Drafts a complete research proposal from hypotheses and methodology

source (1)

Research Ethics Framework

Core principles and requirements for ethical research conduct

document (1)

Ethics Checklist

Pre-submission checklist for research ethics applications

Requirements 1 service, 1 permission, 1 data type
Services
  • LLM Service
Permissions
  • network:doi.org
Data Handling
  • pii
Security Passed
All checks passed v1.1.29 · scanner v3.3.0

Detected

  • Services: llm-service
  • Permissions:
  • Data Handling:
Version history 17 releases
v1.1.29 latest 12 July 2026

GH#818 Phase 1 (Tier 1) — fix intent-vs-output: the pipeline promised a drafted proposal but ran gap-analysis + methodology-assessment → polish (it polished the ANALYSIS). The `hypothesis-generator` and `research-proposal-writer` prompts were shipped but never wired in. Wire both on dedicated local skills (`hypothesis-generation` → "Hypothesis Generator", `proposal-drafting` → "Proposal Drafting"): gap-analysis → hypothesis → methodology → **research-proposal-writer(draft)** → polish. Re-point the proposal-writer's gap refs to `{{steps.Research Gap Identification.output}}` (resolvable title). Polish binds `source` `from_step "Proposal Drafting"`; coherent-lock all deps to current published (repin `polish-language` → 1.0.5, `check-brief-compliance` → 1.0.3 with its new `source` binding). contents skills 0→2.

v1.1.28 2 July 2026

GH#745 — declare per-step `output: {name, type}` on every execution step (research_gaps/text, compliance_verdict/decision, input_gaps/decision, methodology_assessment/text, polished_proposal/text). Lights up the #744 rich flow-map with named, typed outputs. **Also corrects the input-gap-check step to its intended `validation` type** — its `step_type` was mis-indented (outside the parallel item) and dropped at parse time, so the step previously ran untyped; it is now a validation gate. Content + structural fix (GH#748); no bindings changes.

v1.1.27 7 June 2026

GH#645 Row 3b — migrate to K-037 dep-referenced schema. Strip 13 inline shared-content files and declare 13 hub-shared deps (UUID id + slug name + version + checksum from `gen-dep-checksums.mjs`). Closes pre-Step-3 inline-vendoring for this bundle.

v1.1.23 19 May 2026

Signature fix — RELEASE_NOTES.md now included in integrity checksum.

v1.1.22 19 May 2026

Initial catalogue release with full structural and content-quality validation. All scanner checks pass.

v1.1.21 18 May 2026

Release notes unavailable for this version.

v1.1.20 14 May 2026

Release notes unavailable for this version.

v1.1.19 13 May 2026

Release notes unavailable for this version.

v1.1.18 11 May 2026

Release notes unavailable for this version.

v1.1.17 27 April 2026

Release notes unavailable for this version.

v1.1.16 25 April 2026

Release notes unavailable for this version.

v1.1.15 18 April 2026

Release notes unavailable for this version.

v1.1.14 16 April 2026

Release notes unavailable for this version.

v1.1.13 16 April 2026

Release notes unavailable for this version.

v1.1.12 14 April 2026

Release notes unavailable for this version.

v1.1.11 13 April 2026

Release notes unavailable for this version.

v1.0.0 29 March 2026

Release notes unavailable for this version.

More from Researcher

View all →

Send feedback

Sign in to send feedback — it lets us follow up and keeps the tracker free of spam.