Refine prompt to adjust requirement planning

[amitpuri]

Provide a mechanism in the IDE to refine requirement planning before implementation, focus on structuring and evaluating feature descriptions to refine prompt in requirement planning phase in IDE. The extension may internally determine how to implement the functionality to refine prompt rewrite.

• Technical Design

Decompose the described feature into atomic tasks that can be implemented and validated independently. For each task, indicate relevant APIs, libraries, or services that could satisfy the requirement.

• Clarification & Scoping

Rewrite requirements in Goal, Inputs, Outputs, Constraints, and Acceptance Criteria

• Validation & Testability

Rewrite requirements in Gherkin (Given/When/Then) format

• Risk & Dependency Analysis

optionally allow or disallow the external dependencies - from a list.

finally, check whether is SMART: Specific, Measurable, Achievable, Relevant, Time-bound. or not - if possible, point out ambiguity

[amitpuri]

Here's an example of "Implementation Plan" in Antigravity

[nikhilsi]

Thanks for the detailed writeup, Amit. This is a thoughtful proposal — the structured decomposition (Goal/Inputs/Outputs/Constraints, Gherkin, SMART checks) is a well-defined problem.

I'm curious how you see this fitting into Recurate specifically. Right now Recurate focuses on the response side — curating what the AI says back to you via annotation gestures (highlight, strikethrough, dig deeper, verify). What you're describing feels more like an input side tool — refining the prompt before it's sent.

A few questions to understand your thinking:

1. Do you see this as a pre-step before the AI conversation starts, or something that happens during the conversation (e.g., after annotating a response, the refined requirements feed into the next turn)?
2. Would this work as a standalone feature, or do you see it connected to the annotation workflow somehow?
3. Are you working on anything like this yourself? Would love to explore if there's a collaboration angle.

Appreciate you engaging with the project — your Antigravity bug report was spot on too (fix incoming in v0.2.1).