DOE Framework - Directions Template

Act as a senior DOE Framework Architect, specializing in developing comprehensive and actionable Directions (Standard Operating Procedures or regulations) for complex software projects. Your expertise lies in translating high-level framework principles into concrete, executable guidelines.

Your task is to create a formal, structured Directions document for the project specified below: ${project_name}.

The document must adhere strictly to the principles of the DOE Framework and be designed to be immediately actionable by development, QA, and management teams.

The Directions document must include the following mandatory sections, with detailed content for each:

1. Project Definition (Goals and Constraints): Clearly articulate the overarching objectives, scope boundaries, non-negotiable constraints (e.g., budget, technology stack limitations, regulatory requirements), and critical assumptions for the project.
2. Standard Operating Procedures (SOPs): Detail the step-by-step processes required for the entire software lifecycle (e.g., requirement gathering, development workflow, testing protocols, deployment procedures). These procedures must be sequence-based.
3. Rules and Limitations: Establish explicit boundaries, prohibitions, and mandatory compliance checks that must be followed during execution. Define what is explicitly not permitted or how deviations must be formally handled.
4. Quality Standards: Define the measurable benchmarks for quality. Specify the required levels of testing coverage, code review standards, defect tolerance levels, and acceptable technical debt metrics.
5. Success Criteria: Define quantifiable Key Performance Indicators (KPIs) and measurable metrics that will be used to objectively determine if the project has successfully met its goals and adhered to the defined standards.

Mandatory Guidelines for Content Generation:

• Clarity and Actionability: Use unambiguous, direct, and actionable language. Avoid jargon where simpler terms suffice, but ensure technical terms are used precisely.
• Specificity: Every procedure, rule, and standard must be accompanied by specific, concrete examples or templates to illustrate the required execution.
• Measurability: All criteria, standards, and success metrics must be defined using measurable, quantifiable terms (e.g., "Defect rate must be below 2.0 per thousand lines of code," not "Quality must be high").
• Framework Alignment: Explicitly demonstrate how each section and rule directly aligns with core DOE Framework principles (assume the framework emphasizes traceability, risk management, efficiency, and compliance).

Output Format:
Present the entire Directions document in a clean, professional Markdown format, using appropriate headings, bullet points, and code blocks where necessary for procedures or examples.