Guide teams to validate uncertain assumptions with scoped research plans.
npx skills add https://github.com/xiongxianfei/rigorloop --skill research-xiongxianfei
Please help me install this Agent Skill. Skill: research Source: https://github.com/xiongxianfei/rigorloop/tree/main/.codex/skills/research Command: npx skills add https://github.com/xiongxianfei/rigorloop --skill research-xiongxianfei
## What problem does it solve? Formalizes uncertainty by guiding structured assumption research before proposals, specs, architectures, or implementations. It ensures decisions are backed by scoped, sourced evidence rather than ad hoc exploration.
## Core Features & Use Cases
### Quick Start Draft a compact research plan for the upcoming feature, including the decision to inform, key questions, acceptable sources, and the artifact path.
High-intent search queries and answers about installing and using this skill.
Validate technical assumptions by defining the decision, key questions, and acceptable sources upfront, then gathering evidence from official documentation to generate a documented decision-support artifact. This structured research approach ensures your architecture decisions are backed by credible evidence rather than ad hoc exploration.
Assumption research is a structured process of validating uncertain technical behavior, domain facts, platform limits, or compliance constraints before proposals or implementations. You need it when engineering decisions depend on uncertain variables that could introduce risk if left unverified.
Structure a research plan by drafting the specific decision to inform, listing key questions, defining acceptable sources like official docs and standards, and specifying the artifact output path. This scoping ensures focused evidence gathering and generates a reusable decision-support document with conclusions.
Yes, structured research is designed for validating regulatory requirements and compliance constraints before committing to a solution. By defining acceptable primary sources and standards upfront, teams can gather credible evidence and document compliance findings in a structured decision-support artifact.
The best way to document evidence is generating a research artifact with an evidence table and conclusions at a specified path like docs/research/YYYY-MM-DD-slug.md. This formalizes uncertainty by capturing scoped, sourced evidence rather than relying on informal exploration.
Formal assumption research prevents costly architectural mistakes by ensuring decisions are backed by scoped, sourced evidence. Unlike ad hoc exploration, it forces teams to define acceptable sources, document findings in a structured artifact, and systematically address risk management before proposals.
fredericpoitevinAsk clarifying questions to define research goals and scope before starting.
estevanhernandez-stack-edTranslate PRDs into architecture blueprints with data flows and file structures.
udecodeGenerate technical stack documentation by analyzing codebase, configuration files, and dependencies.
plurigridProvide in-memory algebraic databases using ACSets for schema-driven relational modeling.
