--- name: multi-ai-research-synthesis description: "RS track: write a research prompt, save it to a single consistent folder, present it inline in chat for the person to copy, submit to multiple AI platforms (with friendly guardrails on making sure each submission is a genuine deep-research run, not just a normal answer), polish the results into one authoritative filed master document. Use when a person asks to install or apply \"Multi-AI Research Synthesis System\" (FTR-28) in a project, or when working in a project that has it installed." --- # Multi-AI Research Synthesis System (FTR-28, version 2.0) > Generated from library record FTR-28 version 2.0, publish 20261102a. Review status: unreviewed. The complete specification is in references/spec.md and is the authority; this file is the operating procedure drawn from it. ## What this does RS track: write a research prompt, save it to a single consistent folder, present it inline in chat for the person to copy, submit to multiple AI platforms (with friendly guardrails on making sure each submission is a genuine deep-research run, not just a normal answer), polish the results into one authoritative filed master document ## When to use this skill - A person asks to install, apply or update "Multi-AI Research Synthesis System" (FTR-28) in a project. - A project's agent instructions list multi-ai-research-synthesis as installed and the task touches what it covers. - Requires first: FTR-13 (skill document-tracker-system). - Works better with, if installed: FTR-04 (skill agent-role-and-project-identity), FTR-07 (skill folder-structure), FTR-14 (skill active-flags-tracker), FTR-15 (skill project-cache), FTR-29 (skill legal-case-research-synthesis), FTR-30 (skill cascading-research-pipeline). - Required by: FTR-30 (skill cascading-research-pipeline), FTR-32 (skill cowork-orchestrated-research), FTR-35 (skill prompt-vetting-checklist), FTR-29 (skill legal-case-research-synthesis). ## Install procedure Steps run in order. Assess comes first, every question in the Ask step is answered by the person before anything is written, and every write merges additively into the existing project files (read the file first, update an existing section in place, never overwrite). ### Assess first - Confirm the Document Tracker System (FTR-13) is installed — this feature's Research Register depends on it directly. - Check whether `trackers\data\research_register.md` already exists; if so, read and carry it forward rather than starting fresh. - Check whether `research\research_prompts\` already exists; if so, treat it as the established location rather than creating a second one. - Check whether FTR-29 (Legal Case Research Synthesis) is also installed or being installed in the same session — if so, both the `RS` and `LR` tracks exist in this project, and any new research need should be assessed for which track it belongs to (see FTR-29's own track-assessment guidance). Remember the two tracks use different storage rules — `RS` here, `LR` per FTR-29's own file. - Check `#drop\` for any already-waiting platform outputs tied to an open Research Register item. ### Ask, only if needed - If no project code is established yet: this feature needs one for the `RS[NN]` ID format — confirm it's set (should already exist from Agent Role & Project Identity, FTR-04). - When a new research need comes up: "Is this something that needs a full multi-platform research prompt, or is it answerable from what we already know?" (see the criteria below before opening a new RS item). - "Which platforms do you have access to for this one?" if it's not obviously the standard trio. - For a triangulation-preferred item specifically: whether deep research mode is active for the Claude leg, per the guidance above — asked plainly, not assumed either way. **When to open a new RS item** — the need meets at least one of: - The answer will directly drive a real decision, not just background understanding - The question is complex enough that a single-session answer carries meaningful risk of being wrong - The topic is one where AI platforms are known to vary, guess, or hallucinate **When NOT to open one:** - Already answered in an existing RS (or LR) master — check the Research Register first - A quick factual lookup with no real ambiguity - A drafting task — this system is for research, not document production ### Write The full Write payload is in references/write-payload.md. It is applied exactly as written, with the merge rule above. ### Confirm Confirm: the Research Register is set up at `trackers\data\research_register.md`, `research\research_prompts\` is the established location for prompts and masters, the RS track is ready for its first ID, and the standard platform list is recorded. Want to install another, or is that everything for now? ## Other sections in the specification - Why this exists - The RS track - The Research Register (this feature's tracker) - Standard platforms - Making sure each submission is a real deep-research run - The research prompt - Present the prompt to the person, every time - Submit to all platforms in parallel - Polish the results into the MASTER document - Filing and closing the loop These are in references/spec.md. ## Files in this skill - references/spec.md: the complete specification, unabridged. - references/write-payload.md: the Write step on its own.