modeled-information-format/research-harness-template

[channels/channel] Render surviving findings into an AI-ready, agent-executable architecture spec (genre-shaping of the artifact -> markdown pipeline; finding_refs -> evidence, goal checks -> EARS, sections -> structure)

[genres/genre] Genre template for an AI-ready architecture specification (arc42/C4): cross-cutting entity types, relationships, namespaces, decisions-with-alternatives, and EARS acceptance criteria an AI coding agent can execute

[channels/channel] Author a long-form, multi-chapter book from a research session's surviving findings

[market-research/methodology] Use when the user asks to "analyze competitors", "map competitive landscape", "Porter's 5 Forces analysis", "competitor comparison", "competitive positioning", "identify competitors", "competitive intelligence", or needs competitor research

[market-research/methodology] Use when the user asks to "understand customers", "customer research", "user personas", "customer needs analysis", "buyer journey mapping", "voice of customer", "customer segmentation", "user research", or needs guidance on customer-discove

[channels/channel] Render a research topic's entire surviving findings corpus into a complete Diátaxis documentation set — a reference page per finding, a per-dimension explanation, how-to, and guided tutorial, plus index pages — every page carrying MIF Level-1 frontmatter and a diataxis_type marker

[channels/channel] Package a clinical-submission artifact into the FDA eCTD module structure (M1-M5 + the XML backbone) directly from the SOURCES — a topic's surviving findings and their primary-source citations; lays out the eCTD module tree and writes the backbone; verify-live eCTD v4.0; never built from a rendered report

[genres/genre] Genre template for a GitHub Spec Kit single-capability feature spec authored for a coding agent

[market-research/methodology] Use when the user asks to "analyze financials", "revenue model", "unit economics", "pricing analysis", "cost structure", "profitability analysis", "financial projections", "business model economics", or needs financial-metric, revenue-analy

[channels/channel] Publish a research topic to GitHub Discussions, grounded in the SOURCES (findings + primary citations) — an announcement of completed research, a Q&A thread about methodology, or a non-canonical observation; never from a rendered report

[channels/channel] Convert a research topic's surviving findings into actionable GitHub issues, grounded in the SOURCES (findings + primary citations) — atomize each finding's implications into sprint-sized, well-structured issues with acceptance criteria and evidence-justified priority; never from a rendered report

[channels/channel] Render a topic's surviving findings into well-formed JATS (NISO Z39.96) XML directly from the SOURCES — a scholarly article with article metadata, a body of one section per finding, and a back-matter reference list of the primary-source citations; never built from a rendered report

[genres/genre] Genre template for a Kiro three-file spec (requirements -> design -> tasks): a single-feature, task-decomposed build spec for an AI coding agent

[market-research/methodology] Use when the user asks to "calculate market size", "TAM SAM SOM analysis", "estimate market opportunity", "market sizing", "total addressable market", "serviceable market", "market potential", or needs market-size estimation methodologies,

[channels/channel] Produce NotebookLM assets (audio deep-dive, slide deck, infographics, video, mind map) grounded in the SOURCES — the findings' actual cited primary materials are added to the notebook plus a findings digest, never a rendered report

[channels/channel] Produce a styled, print-ready PDF directly from the SOURCES — a topic's surviving findings and their primary-source citations, composed into a comprehensive document and rendered with pandoc, a title page, and Mermaid diagrams; never built from a rendered report

[market-research/methodology] Use when the user asks to "analyze regulations", "regulatory landscape", "compliance requirements", "legal considerations", "regulatory risk", "industry regulations", "compliance analysis", "regulatory trends", or needs guidance on regulato

[trend-modeling/methodology] Use when the user asks to "model trends with limited data", "three-valued logic analysis", "scenario generation", "transitional graphs", "qualitative trend analysis", "uncertain data analysis", "minimal-information modeling", or needs trend

[channels/channel] Render surviving findings (typically a regulatory-disclosure artifact) into an inline XBRL (iXBRL) document directly from the SOURCES — facts tagged with xbrli:context / xbrli:unit and current-taxonomy concepts inside a human-readable XHTML shell; never built from a rendered report