🛠️ Update various documentation, scripts, and configuration templates to enhance clarity, functionality, and maintainability across the project
This commit is contained in:
20
resources/prompts/review-audit-candidates.prompt.md
Normal file
20
resources/prompts/review-audit-candidates.prompt.md
Normal file
@@ -0,0 +1,20 @@
|
||||
---
|
||||
name: "review-audit-candidates"
|
||||
description: "Review an audit shortlist one candidate at a time and update the selection manifest with decisions and notes."
|
||||
agent: "agent"
|
||||
tools: [read, search, edit]
|
||||
argument-hint: "audit=<optional audit directory>"
|
||||
---
|
||||
|
||||
Review the audit shortlist one candidate at a time.
|
||||
|
||||
Requirements:
|
||||
|
||||
- Resolve the target audit directory from `audit=<path>` when provided, otherwise use the latest run under `.local/audits/`.
|
||||
- Read `selection-manifest.tsv` first, then open each pending candidate's `detail_file` before asking for a decision.
|
||||
- Summarize the candidate's purpose, expected benefit, audit context, and why it scored as it did before asking for a decision.
|
||||
- Mention transcript prompt-cost proxy fields when they are present, but label them as cost signals rather than exact token counts.
|
||||
- If the detail bundle has weak or missing evidence, say that explicitly and explain what the user would be deciding on anyway.
|
||||
- Use `vscode_askQuestions` to present decision choices as buttons and allow freeform text for `review_note`.
|
||||
- Update `selection-manifest.tsv` after each answer so review progress survives interruptions.
|
||||
- Stop only when every row has a non-empty `decision` or the user tells you to stop.
|
||||
Reference in New Issue
Block a user