Built-in Prompts
FlightDesk generates two prompts from a task's own context — a review prompt and a test plan prompt. Find them on the Prompts tab of any task, or print them from the terminal:
flightdesk prompt <task-id> # review (the default)
flightdesk prompt <task-id> --type test_plan
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 onto the task: the Context tab has a Test Plan field you can edit in place.
On an orchestrated project you rarely do this by hand — a plan submitted with flightdesk plan submit --test-plan <file> carries the test plan with it, and it appears in the same place. See Task Workflow.
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. While a pull request is linked the summary is read-only in FlightDesk — edit the PR body instead, and the next observation updates the task. A task with no pull request keeps a summary you can edit directly.
The plan also records a release note, which becomes the task's line in its release's changelog — see Initiatives and Releases. Use task comments for a handoff conversation.