research

Comparing solution options involves evaluating 2 to 4 viable approaches against project constraints, verifying current library APIs through official docs, and ranking them by fit, testability, and reversibility. This produces a grounded recommendation memo for implementation planning.

Tradeoff analysis for spec preparation evaluates candidate approaches by fit, testability, reversibility, and project constraint alignment. It surfaces viable paths and verifies current library APIs through context7 to ensure recommendations reflect actual behavior.

Write a research memo for solution exploration by comparing 2 to 4 candidate approaches, verifying current library APIs through context7, and ranking options by fit and reversibility. Save the ranked recommendation to docs/research/<slug>.md to inform implementation.

Yes, solution exploration requires current API verification through context7 or official documentation. This doc-grounded check ensures your tradeoff analysis and ranked recommendations rely on verified, current library behavior rather than outdated memory.

The best way to evaluate candidate approaches for library selection is to compare 2 to 4 viable paths, verify current APIs through official docs, and rank them explicitly by fit, testability, and reversibility. This yields a constraint-aligned recommendation memo.

You should not use tradeoff analysis for implementation planning when only one viable solution path exists or the task lacks multiple plausible approaches. The process specifically compares discrete options and writes a ranked recommendation when multiple paths are present.