メニュー
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.
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 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 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.
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-citation |
| description | 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. |
Build claim-level citation support separately from exemplar learning. An exemplar teaches transferable structure; a citation supports a specific statement.
Read when available:
paper_output/project_config.json
paper_output/concept_dossier.md
paper_output/gap_map.md
paper_output/confirmed_research_spine.md
paper_output/claim_register.md
paper_output/reference_materials/source_index.md
an existing draft or user-supplied list of claims/sources
Read ../research-architect/references/citation-support-bank.md. Use ../research-architect/templates/citation_support_bank.csv as the column contract and write paper_output/citation_support_bank.md as a Markdown table.
Create paper_output/citation_support_bank.md. Link each source to the exact supported claim IDs or claim sentence, stable identifier, source locator, support boundary, verification status, and notes. Default to 30 candidates only when that is useful; prioritize verified relevance over count.
Create paper_output/citation_support_bank.md.metadata.json using
../research-architect/schemas/v1/citation_support_bank.schema.json; its
Supported Claim IDs must resolve to the claim register.
Use verified, partial, needs_user_file, or reject status. Never invent a bibliography entry or claim support. A source that cannot be accessed remains needs_user_file, not assumed supportive.
Accept an existing draft, a section, a claim list, or a small set of sources without the full workflow trail. Extract candidate claims from the supplied text, mark the bank provisional when the spine/claim register is absent, and identify the missing upstream artifact as an intake debt. This branch can support revision, but it does not substitute for evidence readiness before new prose drafting.
For guided depth, cover only the draft's highest-risk or highest-value claims. standard and deep add broader section coverage, source locators, and support-boundary review.