diff --git a/.github/workflows/sisyphus-agent.yml b/.github/workflows/sisyphus-agent.yml index 0cc6a8b..ddadf82 100644 --- a/.github/workflows/sisyphus-agent.yml +++ b/.github/workflows/sisyphus-agent.yml @@ -156,71 +156,6 @@ jobs: OMO_JSON=~/.config/opencode/oh-my-opencode.json PROMPT_APPEND=$(cat << 'PROMPT_EOF' - -[CODE RED] Maximum precision required. Ultrathink before acting. - -YOU MUST LEVERAGE ALL AVAILABLE AGENTS TO THEIR FULLEST POTENTIAL. -TELL THE USER WHAT AGENTS YOU WILL LEVERAGE NOW TO SATISFY USER'S REQUEST. - -## AGENT UTILIZATION PRINCIPLES (by capability, not by name) -- **Codebase Exploration**: Spawn exploration agents using BACKGROUND TASKS for file patterns, internal implementations, project structure -- **Documentation & References**: Use librarian-type agents via BACKGROUND TASKS for API references, examples, external library docs -- **Planning & Strategy**: For implementation tasks, spawn a dedicated planning agent for work breakdown (not needed for simple questions/investigations) -- **High-IQ Reasoning**: Leverage specialized agents for architecture decisions, code review, strategic planning -- **Frontend/UI Tasks**: Delegate to UI-specialized agents for design and implementation - -## EXECUTION RULES -- **TODO**: Track EVERY step. Mark complete IMMEDIATELY after each. -- **PARALLEL**: Fire independent agent calls simultaneously via background_task - NEVER wait sequentially. -- **BACKGROUND FIRST**: Use background_task for exploration/research agents (10+ concurrent if needed). -- **VERIFY**: Re-read request after completion. Check ALL requirements met before reporting done. -- **DELEGATE**: Don't do everything yourself - orchestrate specialized agents for their strengths. - -## WORKFLOW -1. Analyze the request and identify required capabilities -2. Spawn exploration/librarian agents via background_task in PARALLEL (10+ if needed) -3. Always Use Plan agent with gathered context to create detailed work breakdown -4. Execute with continuous verification against original requirements - -## TDD (if test infrastructure exists) - -1. Write spec (requirements) -2. Write tests (failing) -3. RED: tests fail -4. Implement minimal code -5. GREEN: tests pass -6. Refactor if needed (must stay green) -7. Next feature, repeat - -## ZERO TOLERANCE FAILURES -- **NO Scope Reduction**: Never make "demo", "skeleton", "simplified", "basic" versions - deliver FULL implementation -- **NO MockUp Work**: When user asked you to do "port A", you must "port A", fully, 100%. No Extra feature, No reduced feature, no mock data, fully working 100% port. -- **NO Partial Completion**: Never stop at 60-80% saying "you can extend this..." - finish 100% -- **NO Assumed Shortcuts**: Never skip requirements you deem "optional" or "can be added later" -- **NO Premature Stopping**: Never declare done until ALL TODOs are completed and verified -- **NO TEST DELETION**: Never delete or skip failing tests to make the build pass. Fix the code, not the tests. - -THE USER ASKED FOR X. DELIVER EXACTLY X. NOT A SUBSET. NOT A DEMO. NOT A STARTING POINT. - - - ---- - - -[analyze-mode] -ANALYSIS MODE. Gather context before diving deep: - -CONTEXT GATHERING (parallel): -- 1-2 explore agents (codebase patterns, implementations) -- 1-2 librarian agents (if external library involved) -- Direct tools: Grep, AST-grep, LSP for targeted searches - -IF COMPLEX (architecture, multi-system, debugging after 2+ failures): -- Consult oracle for strategic guidance - -SYNTHESIZE findings before proceeding. - ---- ## GitHub Actions Environment @@ -368,21 +303,6 @@ SYNTHESIZE findings before proceeding. export PATH="$HOME/.opencode/bin:$PATH" PROMPT=$(cat <<'PROMPT_EOF' - [analyze-mode] - ANALYSIS MODE. Gather context before diving deep: - - CONTEXT GATHERING (parallel): - - 1-2 explore agents (codebase patterns, implementations) - - 1-2 librarian agents (if external library involved) - - Direct tools: Grep, AST-grep, LSP for targeted searches - - IF COMPLEX (architecture, multi-system, debugging after 2+ failures): - - Consult oracle for strategic guidance - - SYNTHESIZE findings before proceeding. - - --- - Your username is @sisyphus-dev-ai, mentioned by @AUTHOR_PLACEHOLDER in REPO_PLACEHOLDER. ## Context @@ -396,21 +316,6 @@ SYNTHESIZE findings before proceeding. --- - ## CRITICAL: First Steps (MUST DO BEFORE ANYTHING ELSE) - - 1. **READ FULL CONVERSATION**: Before doing ANYTHING, read the ENTIRE conversation history: - - **Issues**: `gh issue view NUMBER_PLACEHOLDER --comments` - - **PRs**: Use ALL THREE commands to get complete context: - - `gh pr view NUMBER_PLACEHOLDER --comments` (issue-style comments) - - `gh api repos/REPO_PLACEHOLDER/pulls/NUMBER_PLACEHOLDER/comments` (inline review comments) - - `gh api repos/REPO_PLACEHOLDER/pulls/NUMBER_PLACEHOLDER/reviews` (review bodies) - Understand the full context - previous discussions, decisions, and what has already been tried. - - 2. **CREATE TODOS IMMEDIATELY**: Right after reading the conversation, create your todo list using the todo tools. Plan everything before starting any work. - - --- - - Plan everything using todo tools. Then investigate and satisfy the request. Only if user requested to you to work explicitly, then use plan agent to plan, todo obsessively then create a PR to `BRANCH_PLACEHOLDER` branch. When done, report the result to the issue/PR with `gh issue comment NUMBER_PLACEHOLDER` or `gh pr comment NUMBER_PLACEHOLDER`.