DOE Framework - Directions Template
Act as a DOE Framework Architect. You are an expert in creating Directions (SOP/регламенты) for software projects. Your task is to create a…
Prompt
Act as a DOE Framework Architect. You are an expert in creating Directions (SOP/регламенты) for software projects.
Your task is to create a structured Directions document for: ${project_name}
The document should include:
- Project goals and constraints
- Standard operating procedures
- Rules and limitations
- Quality standards
- Success criteria
Rules:
- Use clear, actionable language
- Include specific examples
- Define measurable criteria
- Align with DOE Framework principles
Output the document in markdown format.How to use this prompt
- 1
Copy the prompt above and paste it into ChatGPT, Claude, or Gemini — or open it in the visual Studio to edit each part on a canvas and run it with your own key.
- 2
Replace any bracketed placeholders with your specifics. The more concrete your context and constraints, the sharper the result — see the 5-part prompt structure.
- 3
Run it, then refine. Ask the model to critique and improve its own answer with self-critique prompting.
Techniques in this prompt
Assigns the model an expert persona so it adopts the right vocabulary, depth, and standards for the task.
Learn this techniqueRecommended models
Build on this prompt
Open it in the visual Studio to wire it into a full workflow with your own API key — or learn the craft behind prompts like this.
More in Software Engineering
Production Incident Root Cause Analysis
Drives a disciplined RCA from symptoms to root cause and prevention, separating contributing factors from the true trigger.
Security-Focused Code Review For Pull Requests
Reviews a diff specifically for security vulnerabilities, mapping findings to severity, exploit path, and concrete fixes.
Legacy Code Refactoring Strategist
Plans a safe, incremental refactor of tangled legacy code with characterization tests and reversible seams.
API Contract Designer With OpenAPI Output
Designs a consistent, versioned REST resource and emits a ready-to-use OpenAPI 3.1 fragment plus error model.