Human Gate Details
Gate points and Erik_Todo format, extracted from Research Sections 4–5.
Gate Points
Gates are before a phase proceeds — the human approves to unlock the next step.
| Gate Point | Mechanism |
|---|---|
| Before Vision approval | Skill presents draft, iterates until approved |
| Before each Research decision | Skill presents decisions, iterates until all approved |
| Before Spec approval (after Spec Audit) | Skill presents draft + audit result, iterates until approved |
| Before Plan approval (after Plan Audit) | Skill presents plans + audit result, iterates until approved |
| Before each Evaluation proceeds | Evaluate skill presents findings, user decides fix/update/reject/defer |
| Before Verify proceeds | Verify skill presents findings, user decides |
Enhanced Erik_Todo Format
Each item includes:
- Project name
- What needs attention
- Document link for review
- Current document status
Blocked State Convention
When an agent hits a blocker, the Phase file is set to {Phase}_Blocked (e.g., Implement_1_Blocked). Project Runner detects _Blocked suffix and appends to Erik_Todo for escalation.
Files Containing Lifecycle String
Forge/Skills/Project_Flow/SKILL.mdForge/Configs/Agents/Project_Snippet.mdForge/Configs/Agents/Forge_Chat_Prompt.md