TheDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/paramveer-cyber/Deployaar/llms.txt
Use this file to discover all available pages before exploring further.
featureRequest router manages the complete lifecycle of a feature request — from the moment a plain-English idea is submitted, through the AI clarification conversation, PRD generation, agent coding, review, and final shipment. Every procedure in this router requires authentication and enforces organization membership before any data is read or mutated.
featureRequest.createFeatureRequest — mutation
Creates a new feature request inside a project. The caller must be an authenticated member of the organization that owns the project, the project must have a linked GitHub repository, and the organization must not have exceeded its plan’s feature request limit.
Billing limits are enforced at creation time. If the organization has reached
its plan’s
maxFeatureRequests ceiling the procedure throws a 403 Forbidden
error with an upgrade prompt.Input
The UUID of the project under which the feature request will be created.
A short human-readable title for the feature. Minimum 5 characters, maximum 200 characters.
The full plain-English description of the feature being requested. Minimum 10 characters.
Response
featureRequest.getFeatureRequests — query
Returns all feature requests belonging to a specific project. Results are ordered by creation date descending.
Input
The UUID of the project whose feature requests should be listed.
Response
featureRequest.getFeatureRequestById — query
Fetches a single feature request by its ID, provided the caller is a member of the owning organization.
Input
The UUID of the feature request to retrieve.
Response
featureRequest.updateFeatureRequestStatus — mutation
Directly sets the status of a feature request. Use the specialized lifecycle procedures (approveRelease, rejectRelease, markShipped) where possible — they enforce guard conditions. This procedure is for administrative overrides.
Status values
| Value | Description |
|---|---|
clarifying | Awaiting user answers in the clarification chat |
prd_pending | Clarification complete, PRD not yet generated |
planning | PRD approved, engineering tasks being generated |
in_development | Coding agent is running or has run |
in_review | PR exists, awaiting AI code review pass |
fix_needed | Review failed or release rejected — needs another coding cycle |
approved | Release approved by an owner or admin |
shipped | PR merged into the default branch |
rejected | Permanently closed without shipping |
Input
The UUID of the feature request to update.
One of:
clarifying | prd_pending | planning | in_development | in_review | fix_needed | approved | shipped | rejectedResponse
featureRequest.getClarificationMessages — query
Retrieves the full AI ↔ user clarification conversation for a feature request. Messages are returned in chronological order.
Input
The UUID of the feature request whose clarification thread should be fetched.
Response
featureRequest.submitReplyAndGetNextQuestion — mutation
Saves the user’s reply in the clarification chat and immediately calls the AI to generate the next follow-up question. Returns both the saved user message and the AI’s next question (or null when the AI determines clarification is complete).
Input
The UUID of the feature request being clarified.
The user’s reply to the current AI question. Minimum 1 character, maximum 4 000 characters.
Response
featureRequest.completeClarification — mutation
Marks the clarification phase as finished and transitions the feature request to prd_pending, signalling that it is ready for PRD generation. Call this when the user chooses to end the conversation early or after the AI returns nextAiQuestion: null.
Input
The UUID of the feature request to advance past clarification.
Response
featureRequest.approveRelease — mutation
Approves a feature request for release. The feature request must currently be in in_review status and the caller must be an owner or admin of the organization.
Input
The UUID of the feature request to approve.
Response
featureRequest.rejectRelease — mutation
Rejects a release and moves the feature request back to fix_needed, triggering another coding cycle. The feature request must be in_review or approved. Caller must be an owner or admin.
Input
The UUID of the feature request to reject.
Response
featureRequest.markShipped — mutation
Merges the associated GitHub pull request (squash merge) and transitions the feature request to shipped. Requires approved status, a linked repository, and at least one AI review that passed. Caller must be an owner or admin.
Input
The UUID of the feature request to ship.
Response
featureRequest.deleteFeatureRequest — mutation
Permanently deletes a feature request and its associated data. The caller must be a member of the owning organization.
Input
The UUID of the feature request to delete.
Response
featureRequest.getDashboardFeed — query
Returns the dashboard feed for the authenticated user, segmented into three buckets. No input required.
Feature requests currently waiting on the user:
clarifying, prd_pending, in_review, fix_needed.Feature requests actively being processed by the system:
planning, in_development.The 10 most recently shipped feature requests.