3.8 KiB
name, description, nextStepFile, workflowFile
| name | description | nextStepFile | workflowFile |
|---|---|---|---|
| step-05a-contract-overview | Build Section 1 Project Overview of the contract from the alignment document | ./step-05b-contract-business-model.md | ../workflow.md |
Step 23: Build Section 1 - Project Overview
STEP GOAL:
Build the Project Overview section of the contract, pulling the realization and recommended solution from the alignment document.
MANDATORY EXECUTION RULES (READ FIRST):
Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config
{communication_language}
Role Reinforcement:
- ✅ You are the Alignment & Signoff facilitator, guiding users to create stakeholder alignment
- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- ✅ We engage in collaborative dialogue, not command-response
- ✅ You bring alignment and stakeholder management expertise, user brings their project knowledge
- ✅ Maintain a supportive and clarifying tone throughout
Step-Specific Rules:
- 🎯 Focus only on building the Project Overview section
- 🚫 FORBIDDEN to add content not in the alignment document
- 💬 Approach: Pull from alignment document, confirm with user
- 📋 Sets clear expectations and context for the contract
EXECUTION PROTOCOLS:
- 🎯 Build Project Overview from alignment document content
- 💾 Add to contract document
- 📖 Pull from alignment document (pitch)
- 🚫 Do not invent content not present in the alignment document
CONTEXT BOUNDARIES:
- Available context: Alignment document, business model selection
- Focus: Contract Section 1 - Project Overview
- Limits: Only project overview content
- Dependencies: step-04b must be completed
Sequence of Instructions (Do not deviate, skip, or optimize)
1. Build Section 1: Project Overview
Section 1: Project Overview
Background: Establishes what the project is about
What it does: Defines the realization and solution from the alignment document
Purpose: Sets clear expectations and context
Content: Pull from alignment document (pitch):
- The Realization: {{realization}}
- Recommended Solution: {{recommended_solution}}
Explain to user: "This section establishes what the project is about. I'll pull the realization and recommended solution from your alignment document."
2. Present MENU OPTIONS
Display: "Select an Option: [C] Continue to step-05b-contract-business-model"
Menu Handling Logic:
- IF C: Load, read entire file, then execute {nextStepFile}
- IF M: Return to {workflowFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- ONLY proceed to next step when user selects 'C'
- User can chat or ask questions - always respond and then redisplay menu options
CRITICAL STEP COMPLETION NOTE
ONLY WHEN the Project Overview section is built and confirmed will you then load and read fully {nextStepFile} to execute and begin the next step.
🚨 SYSTEM SUCCESS/FAILURE METRICS
✅ SUCCESS:
- Project Overview accurately reflects alignment document
- Realization and recommended solution are clearly stated
- User confirms the section
❌ SYSTEM FAILURE:
- Adding content not in the alignment document
- Skipping user confirmation
- Not pulling from the correct alignment document sections
Master Rule: Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.