Pi Prompting

Use this skill when pi:pi-rescue needs to ask Pi for help on a non-trivial coding or investigation task.

Pi runs whatever model the user has configured. By default this plugin targets DeepSeek V4 (Pro for review, Flash for everyday tasks). The guidance below assumes the prompt may run on either a non-reasoning model (Flash) or a reasoning model (Pro). Bias toward concrete, numbered checklists rather than abstract instructions — both model classes follow those reliably.

Core rules:

• Prefer one clear task per Pi run. Split unrelated asks into separate runs.
• Tell Pi what done looks like. Do not assume it will infer the desired end state.
• State explicit grounding rules whenever an unsupported guess would degrade quality.
• Use stable XML-style tag blocks so the prompt has obvious internal structure.
• Keep prose short. Prefer numbered checklists over paragraphs for procedural work.

Default prompt recipe:

• <task>: the concrete job and the relevant repository or failure context. Include file paths.
• <output_contract> (or <structured_output_contract> for JSON): exact shape, ordering, and brevity requirements.
• <grounding_rules>: required for review, research, or anything that could drift into unsupported claims.
• <action_safety>: required for write-capable tasks — name the directories and file kinds Pi may touch.