005-write-research

Creates IMRAD-structured research documents following XDRS research standards and scope rules.

1|1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/flaviostutz/xdrs-core --skill 005-write-research-flaviostutz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 005-write-research
Source: https://github.com/flaviostutz/xdrs-core/tree/main/examples/typed-scope/.xdrs/_core/adrs/principles/skills/005-write-research
Command: npx skills add https://github.com/flaviostutz/xdrs-core --skill 005-write-research-flaviostutz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams need research documents that back architectural, business, and engineering decisions with reproducible evidence, but ad-hoc notes lack structure, traceability, and consistent placement. This Skill guides the creation of standardized XDRS research documents that read as standalone technical papers. ## Core Features & Use Cases - Structured IMRAD authoring: Produces research documents with Abstract, Introduction, Methods, Results, Discussion, Conclusion, and References sections, each checked against explicit section goals and word-count ratios. - Scope, type, and numbering governance: Selects the correct XDRS scope, decision type (ADR/BDR/EDR), subject, and sequential research number while avoiding duplication with existing Policies and research. - Interactive clarification workflow: Asks focused questions at each phase when direction, evidence, or next steps are unclear instead of guessing. - Use Case: When asked to compare package distribution options for a decision, the Skill scans existing research, gathers evidence, writes a comparison study with pros and cons, updates indexes, and runs lint verification. ## Quick Start Ask the assistant to create a research document comparing options for a decision topic, and answer the clarifying questions about scope, evidence, and intended next steps.

Frequently Asked Questions about 005-write-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a research document that backs an architecture decision?▼

Use this Skill to create an XDRS research document with IMRAD sections: Abstract, Introduction, Methods, Results, Discussion, Conclusion, and References. It selects the scope, type, subject, and number, then guides evidence collection and synthesis interactively.

What is the difference between a research document and a Policy in XDRS?▼

A research document explores the problem space, evidence, and option trade-offs, while a Policy captures the final decision and rules. If the user actually wants a final decision, the Skill directs them to write a Policy instead.

How are research documents numbered and placed in XDRS?▼

The Skill scans .xdrs/[scope]/[type]/[subject]/researches/ for the highest existing number and increments by one, never reusing deleted numbers. Placement follows the type (adrs, bdrs, edrs) and subject rules defined in the XDRS standards policy.

Can the research document include diagrams and images?▼

Yes, following the XDRS asset policy: prefer Markdown tables and lists first, then ASCII art, then Mermaid diagrams, then draw.io editable SVGs. Local files are stored in the sibling .assets folder and linked with relative paths.

What are the limitations of the XDRS research format?▼

Documents must stay under 5000 words with section word limits and an Introduction:Methods:Results:Discussion ratio near 3:5:6:4, unless the introduction justifies a detailed study. Research must not become the final decision or focus on repository process.