Built-in Prompts

FlightDesk generates ready-to-use prompts for common tasks at every stage of the workflow. Find them on any task detail page under the Prompts section.

Review Prompt

Aggregates all pending feedback from every active review integration and produces a single prompt for Claude Code to address everything at once.

When it's available: After a PR is open and at least one check has reported issues.

What it produces: A prompt containing authenticated API calls to fetch issue content, instructions to fix each issue, and API calls to mark them resolved after fixing.

See Review Feedback Support for a full explanation.

Test Plan Prompt

Asks Claude Code to write a structured test plan for a human reviewer to follow when testing the preview environment.

When to use it: After Claude Code has finished its work and opened a PR, before you do QA.

What it produces: Claude Code responds with:

• What Changed — a 1-3 sentence summary of the changes
• Steps to Test — numbered steps with specific UI actions, paths, and expected outcomes
• Edge Cases to Verify — error states, permissions, empty states, mobile viewports
• What NOT to Test — scope boundaries to save the reviewer's time

Copy the prompt, paste it into Claude Code, and save the response back to the task using the Save Test Plan field on the task detail page.

Task Summary

The pull request body is the task summary. FlightDesk mirrors it when a PR opens, reopens, is edited, or is attached manually. Read it above the test plan in Review or in the Context tab. Update the PR body when the work changes; the next observation updates the task.

The plan also records a release note for future changelogs. Use task notes for a handoff conversation.