coding-research

Gather authoritative external evidence to resolve product, domain, library, or API uncertainties.

10|1|Updated Feb 22, 2026

Search Tags:#architecture #documentation #research #api #evidence #context7

Ready to run

npx skills add https://github.com/marcocello/dot-codex --skill coding-research

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: coding-research
Source: https://github.com/marcocello/dot-codex/tree/main/skills/coding-research
Command: npx skills add https://github.com/marcocello/dot-codex --skill coding-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces speculative planning by helping you gather authoritative external evidence before committing product, architecture, or feature decisions to docs and contracts.

Core Features & Use Cases

Evidence-first research: Start from a concrete uncertainty and resolve it with the minimum reliable evidence needed.
Authoritative sourcing: Prefer Context7, official documentation, standards, and vendor sources over summaries or blog posts.
Bounded decision support: Use the findings to inform planning documents such as APP.md, ARCHITECTURE.md, or FEATURE.md without creating a separate research track.

Quick Start

Ask the coding-research skill to verify the specific external assumption you need to settle and summarize the implication for your plan.

Frequently Asked Questions about coding-research

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

FAQPage Schema

How do I gather authoritative evidence for API and architecture assumptions before planning?▼

To gather authoritative evidence for API and architecture assumptions, use Context7-first sourcing to find official documentation, standards, and vendor sources. This resolves product, domain, or library uncertainties before finalizing planning documents and contracts.

What is the best way to verify external library uncertainties for app design?▼

The best way to verify external library uncertainties for app design is applying evidence-first research. It targets narrow questions affecting feature scope and implementation assumptions, mapping concise findings directly to planning documents like APP.md or ARCHITECTURE.md.

Does this research approach use official documentation over blog posts for feature scope decisions?▼

Yes, this research approach uses official documentation over blog posts for feature scope decisions. It enforces a preference for Context7, official documentation, standards, and vendor sources to prevent speculative planning and reliable evidence.

How do I map research findings to planning documents without creating a separate research track?▼

To map research findings to planning documents without a separate research track, use bounded decision support. It integrates concise external evidence directly into existing files like FEATURE.md, ensuring research informs architecture and product decisions seamlessly.

When do I need evidence-first research for implementation assumptions?▼

You need evidence-first research for implementation assumptions when you have a concrete uncertainty affecting app design, architecture, or feature scope. It gathers the minimum reliable evidence needed to resolve these specific domain or API questions before committing.