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.
Session Summary Prompt
Asks Claude Code to write a permanent record of what was done in this session.
When to use it: At the end of a session, before archiving or handing off. Session context is lost when a session ends — the summary preserves the key decisions and changes.
What it produces: Claude Code responds with:
- Problem — the original requirement
- Approach — technical decisions and why they were made
- Changes Made — file-by-file summary of what was added, modified, or removed
- Known Limitations — anything deferred or cut
- Dependencies & Side Effects — new packages, migrations, environment variables
Save the response to the task using the Save Session Summary field. It's stored permanently on the task even after the session is archived.
Handoff Prompt
Asks Claude Code to document current state for someone who will continue the work later.
When to use it: When a task needs to be paused and resumed later, or passed to a different person or session.
What it produces: Claude Code responds with:
- Current State — what's done, what's in progress, what hasn't started
- Blocked On — anything that prevented completion
- Key Files — the most important files with a one-line description each
- Next Steps — ordered list of what to do first when resuming
- Gotchas — non-obvious things the next person needs to know
Save the response using the Save Handoff Notes field. The next session can read these notes to resume without losing context.