Skip to main content
Prompts DOE Framework Project Directions Generator

developer planning template risk: low

DOE Framework Project Directions Generator

Instructs the model to act as a DOE Framework Architect and create a structured markdown Directions document for a specified software project, including project goals and constrain…

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.

INPUTS

project_name REQUIRED

Name of the software project

e.g. Inventory Management System

REQUIRED CONTEXT

  • project_name

ROLES & RULES

Role assignments

  • Act as a DOE Framework Architect.
  • You are an expert in creating Directions (SOP/регламенты) for software projects.
  1. Use clear, actionable language
  2. Include specific examples
  3. Define measurable criteria
  4. Align with DOE Framework principles

EXPECTED OUTPUT

Format
markdown
Schema
markdown_sections · Project goals and constraints, Standard operating procedures, Rules and limitations, Quality standards, Success criteria
Constraints
  • use clear actionable language
  • include specific examples
  • define measurable criteria
  • align with DOE Framework principles

SUCCESS CRITERIA

  • Include Project goals and constraints
  • Include Standard operating procedures
  • Include Rules and limitations
  • Include Quality standards
  • Include Success criteria

FAILURE MODES

  • Output not in markdown format
  • Missing one or more required sections
  • Language not clear or actionable
  • Lacking specific examples
  • Criteria not measurable
  • Not aligned with DOE Framework principles

CAVEATS

Dependencies
  • Value for ${project_name}
  • Knowledge of DOE Framework principles
Missing context
  • Definition or description of 'DOE Framework' and its principles.
  • Project-specific details beyond '${project_name}' (e.g., initial goals, tech stack).
Ambiguities
  • 'DOE Framework principles' are referenced but not defined.

QUALITY

OVERALL
0.85
CLARITY
0.90
SPECIFICITY
0.85
REUSABILITY
0.95
COMPLETENESS
0.75

IMPROVEMENT SUGGESTIONS

  • Add a section defining DOE Framework principles with bullet points.
  • Include placeholders for project-specific inputs like 'goals: ${goals}', 'constraints: ${constraints}' to enhance reusability.
  • Provide a sample output snippet for one section to model the expected structure and tone.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR DEVELOPER