A monolithic prompt puts stable behavioral instructions—such as role, output format, and communication style—in the same block as the data to process. When that data changes, the whole prompt must be copied and updated. Separating instructions from changing input can make prompts easier to maintain and scale. section 6.0
When deciding whether to keep a prompt monolithic or split it, consider:
- Whether the prompt is a simple request or will be reused with changing input. section 6.0 section 6.4.6
- If splitting, put stable behavior in a system prompt and changing data in a user prompt; delimit variable content when appropriate. section 6.0 section 6.4.6
Release-readiness prompt
You are a release readiness advisor. Review this deployment and decide whether it is safe to ship. Flag major risks, missing rollback steps, and unclear ownership. Format the response as Decision, Risks, and Recommended Action. Deployment details: [changing input] section 6.4.6
