spec-research

To convert a vague change request into a structured research brief, use constraint-driven discovery to translate user asks into precise goals, boundaries, dependencies, and risks. This process bounds the request and outputs proposal-ready constraints for planning.

Updating OpenSpec proposal context without altering product code involves applying a focused research brief to capture constraints and synthesis outputs. This enforces that research outputs strictly update the proposal context while documenting risks and questions.

Constraint synthesis for Codex change requests works by bounding the request with a focused discovery brief. It translates the initial request into explicit constraints, synthesis outputs, and a clear path to planning.

You can collaborate with Claude to gain alternative perspectives on a research proposal while preserving your ownership of the research brief. This optional collaboration helps refine constraints and questions without losing authorship control.

You need bounded discovery for a product change request when facing vague asks that require precise, constraint-driven briefs to feed planning. It captures risks, dependencies, and questions to ensure the proposal context is fully prepared.

Spec-research works with OpenSpec proposals to generate planning constraints by translating user requests into bounded research briefs. It updates the proposal context with goals, boundaries, and synthesis outputs without modifying product code.