openspec-explore

You can clarify requirements and goals without coding by using structured prompts to discuss constraints, compare design options, and investigate codebases. This ensures non-code artifacts, traceability, and risk identification across uncertain problem spaces in Spark-workflow projects.

Comparing design tradeoffs during early-stage project discussion involves surfacing options and constraints without committing to implementation. You can capture requirements, compare approaches, and raise questions to align team understanding while limiting scope strictly to investigation.

To start an open-spec exploration for a Spark-workflow project, initiate a structured session to capture requirements, options, and risks. This limits scope strictly to discussion, comparison, and investigation without implementation across uncertain problem spaces.

Yes, you can investigate a codebase or docs to align team understanding and raise questions without committing to changes. This approach captures constraints and goals while ensuring non-code artifacts and traceability through structured prompts.

Yes, this approach supports capturing non-code artifacts for requirement traceability. It clarifies requirements and exploration goals through structured prompts, ensuring risks are identified and scope is limited strictly to discussion and investigation without implementation.