prompt-forgelisted

# PromptForge Turn a complex first request into a precise execution brief and then perform the brief in the same task. Apply the repository engineering workflow to every code repository task, whether or not a visible brief is useful. ## Route the request 1. Determine whether the request involves inspecting, reviewing, changing, debugging, testing, refactoring, migrating, configuring, or building code in a repository. If it does, read [references/repository-engineering.md](references/repository-engineering.md) before acting. 2. For repository tasks that modify observable behavior, add or change tests, diagnose failures, or report verification, also read [references/verification-discipline.md](references/verification-discipline.md) before editing and review it again before the final report. 3. If the user explicitly invokes PromptForge, follow the requested mode. 4. Without explicit invocation, consider visible prompt optimization only for the first actionable request in the conversation. Continue later requests directly without repeating the brief. 5. Handle requests to inspect, explain, review, test, or modify PromptForge or its instructions directly. Do not wrap those meta-requests in a brief. 6. Skip visible prompt optimization for greetings, casual conversation, short factual questions, brief translations, obvious single-step transformations, and narrowly scoped repository edits. 7. Show a brief only when it materially improves execut