wa:spec-research

Technical feasibility research for a feature spec involves gathering prior art, industry patterns, and stack compatibility constraints. You can generate a structured research report by running a spec-research command with your feature topic to explore existing codebase context and inform acceptance criteria.

Spec-driven development research is the process of evaluating domain patterns, prior art, and codebase constraints before writing implementation specs. You need it during feature discovery to reduce design thrash and ensure acceptance criteria align with what is technically possible within your project.

Documenting acceptance criteria constraints through codebase exploration involves analyzing existing repository patterns and infrastructure to identify extension points. The research process outputs a structured RESEARCH.md file that maps feasibility constraints and likely modifications to guide your scope decisions.

Yes, you can adjust feasibility analysis rigor using mode calibration. Lite, Standard, and Strict modes match your development stage and risk tolerance, allowing lighter research for early discovery and deeper analysis when evaluating complex technical constraints.

The best way to structure prior art research for spec-driven development is to parallelize research by dimension, consulting heuristics when available, and writing a structured report to a dedicated docs directory. This approach covers domain patterns, comparable implementations, and stack compatibility simultaneously.

Yes, spec research works for evaluating architectural patterns like multi-tenant data isolation. By passing the topic as a parameter, the research process gathers industry patterns, comparable implementations, and feasibility constraints specific to that domain, outputting a structured report to guide your design decisions.