research-requirements

To turn a feature idea into clear requirements documentation, you provide a plain-text brief or GitHub issue URL. The tool ingests the full input, extracts functional constraints, and outputs a structured research document with documented findings.

Requirements research is the early discovery process of collecting technology options, constraints, and success criteria before implementation planning. It decomposes inputs into research domains and investigates best practices to document findings and recommendations.

To analyze technology trade-offs from a GitHub issue, provide the URL for full ingestion before parallel research agents investigate options and best practices. The tool synthesizes results into a fixed-schema flow document with documented findings and recommendations.

Yes, you can use plain-text descriptions to generate a research report for new features. The tool ingests the text brief, runs parallel investigation agents, and writes a complete research report under the flow directory before stopping for user confirmation.

The best way to document constraints and architecture options before planning is to run parallel research agents that synthesize technology preferences and historical context. This generates a fixed-schema research document and stops for user confirmation before proceeding.

No, you do not need a GitHub issue URL to perform requirements research. You can provide a plain-text description of what you want to build, and the tool will ingest the full input to identify functional requirements and research domains.