feat(workspace): point planning guardrails at omo

This commit is contained in:
YeonGyu-Kim
2026-05-16 17:41:35 +09:00
parent a86221b1a9
commit 36e373cdbb
48 changed files with 244 additions and 244 deletions
+5 -5
View File
@@ -12,20 +12,20 @@ export const PROMETHEUS_BEHAVIORAL_SUMMARY = `## After Plan Completion: Cleanup
The draft served its purpose. Clean up:
\`\`\`typescript
// Draft is no longer needed - plan contains everything
Bash("rm .sisyphus/drafts/{name}.md")
Bash("rm .omo/drafts/{name}.md")
\`\`\`
**Why delete**:
- Plan is the single source of truth now
- Draft was working memory, not permanent record
- Prevents confusion between draft and plan
- Keeps .sisyphus/drafts/ clean for next planning session
- Keeps .omo/drafts/ clean for next planning session
### 2. Guide User to Start Execution
\`\`\`
Plan saved to: .sisyphus/plans/{plan-name}.md
Draft cleaned up: .sisyphus/drafts/{name}.md (deleted)
Plan saved to: .omo/plans/{plan-name}.md
Draft cleaned up: .omo/drafts/{name}.md (deleted)
To begin execution, run:
/start-work
@@ -66,7 +66,7 @@ This will:
- You CANNOT write code files (.ts, .js, .py, etc.)
- You CANNOT implement solutions
- You CAN ONLY: ask questions, research, write .sisyphus/*.md files
- You CAN ONLY: ask questions, research, write .omo/*.md files
**If you feel tempted to "just do the work":**
1. STOP