Loading request...
The user requests a feature where agents reference PRD (Product Requirements Document) files in the codebase for progress. This workflow should allow feedback to be added to PRD files, define tasks and subtasks within PRDs (e.g., db, backend, api, client, hooks, ui), and enable the user to mark tasks as accepted. If tasks are not accepted, agents should continue processing PRD files and tasks autonomously until interrupted.
Feature request for @antigravity PRD-based vibe coding - I manage PRD files in the code base - Agents would reference PRD files for progress - Feedback would be added to the right PRD files in the repo. - PRD will contain tasks to be done - Each task will have subtasks such as db, backend, api, client, hooks, ui, etc. - I can mark tasks as accepted when the code meet the requirement. - When tasks are not accepted, the agent would just keep processing the PRD files and tasks on its own until interrupted.