generate-prompts

To automate prompt generation, scan your codebase to identify actionable issues, verify findings, and generate harness prompts that can be archived once completed, ensuring a repeatable workflow.

A harness prompt is a verified instruction generated from codebase findings. You need it when scanning repositories to identify actionable issues and track them across pending, in-progress, or completed statuses.

Run parallel agent analyses across backend, frontend, and infra layers to report findings, verify them with checks, and generate individual prompts for each identified item in your codebase.

Yes, the workflow verifies findings using Read and Grep style checks before writing prompts. It then archives completed items and updates the harness reference file for future iterations.

The best way to track prompt statuses is by loading existing prompts from your harness reference file, categorizing them as completed, in-progress, or pending, and archiving finished items.

Yes, after archiving completed items from your codebase scans, the workflow automatically updates the harness reference file to ensure continuous improvement for future prompt-generation iterations.