Prompt Engineering

Treat prompts as small behavioral specs. Improve them by naming the job, testing the behavior, changing one important thing at a time, and preserving the prompt's operating context.

Activity And Authority

• For review, return findings and evidence without rewriting files or changing a deployed prompt. A proposed revision may accompany findings when requested.
• For drafting or implementation, change the requested prompt artifact within existing authority. Separate local evaluation from deployments, live tool actions, sensitive-data use, and metered runs that need additional authority.
• Use the smallest useful output. A short rewrite need not produce a formal experiment report; a consequential behavior change needs explicit cases and honest evidence.

Core Workflow