メニュー
Use when executed research materials, results, observations, analyses, or draft claims need to become a Research Architect evidence bank, claim register, evidence-display plan, and bounded interpretation trail.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when reviewing, revising, or deciding whether to complete a Research Architect draft, especially when its reference adaptation, design, evidence, citations, claim boundaries, copying risk, or missing upstream artifacts need an auditable diagnosis.
Use when a user needs distinct, feasible Research Architect research-question options from a raw topic, available materials, constraints, and—when available—transferable logic from a target reference paper.
Use when a Research Architect project or existing draft needs claim-level literature support for background, positioning, methods, interpretation, limitations, or revision, rather than broad generic literature searching.
Use when a Research Architect candidate research spine and approved exemplar adaptation need to become a feasible, field-appropriate study design, analysis plan, validation strategy, and user action plan.
Use when a Research Architect project has an evidence-ready spine, evidence and claim trail, citation support, and adapted reference logic that need to become a field-appropriate first draft or an audited revision.
Use when starting or resuming a Research Architect project—including an existing draft that needs review—and you need to capture target reference papers, project materials, constraints, verification status, and the next deliverable.
| name | research-architect-evidence |
| description | Use when executed research materials, results, observations, analyses, or draft claims need to become a Research Architect evidence bank, claim register, evidence-display plan, and bounded interpretation trail. |
Organize executed material into claims that remain inside their evidence and inference boundaries.
Read when available:
paper_output/confirmed_research_spine.md
paper_output/study_design_brief.md
paper_output/analysis_plan.md
paper_output/evaluation_plan.md
paper_output/study_component_registry.md
paper_output/exemplar_adaptation_plan.md # when target references exist
user-supplied results, sources, analyses, observations, or draft claims
If no verifiable evidence or argumentative material exists, create paper_output/execution_plan.md using ../research-architect/templates/execution_plan.md, identify the next executable actions, and stop before drafting. Do not let a renamed task list substitute for evidence readiness.
Read ../research-architect/references/claim-evidence-framework.md. Use the following CSV files only as column contracts; write Markdown artifacts in paper_output/:
../research-architect/templates/evidence_bank.csv
../research-architect/templates/claim_register.csv
../research-architect/templates/evidence_display_map.csv
Create:
paper_output/evidence_bank.md
paper_output/claim_register.md
paper_output/evidence_display_map.md
paper_output/claim_strength_calibration.md
paper_output/result_interpretation_notes.md
For guided depth, produce the evidence bank, claim register, and only the display/interpretation information needed to make a next decision. standard and deep add the complete display and calibration trail.
Every central claim must resolve to evidence IDs, citation IDs, or an explicit limitation; record exact locators, contradictory/null/negative material, and verification status. An evidence display must name its argument function and allowed claim.
Create evidence_bank.md.metadata.json and claim_register.md.metadata.json
with the contracts in ../research-architect/schemas/v1/. Use stable Evidence
IDs and Claim IDs so run validation can resolve their links.
Before prose drafting, present the evidence/claim trail, limitations, contradictions, and unresolved gaps. On a standard/deep run, use python3 ../research-architect/scripts/first_paper_artifact_check.py paper_output --mode plan and treat any failed prerequisite as a blocker or intake debt. Obtain explicit user approval that the available evidence is ready for the intended draft scope, then record it with python3 ../research-architect/scripts/run_state.py gate paper_output evidence_readiness <status>. Do not add another approval gate here. If evidence is absent, the run remains at execution_plan.md and cannot pass this gate.
Accept supplied results, tables, interview material, documents, or a draft with claims even when upstream design artifacts are missing. Mark the missing design context as an intake debt or provisional limitation, do not invent it, and route structural gaps to design or intake. Do not convert preliminary material into stronger claims merely to complete a table.