feat(workflow): implement retry tracking and escalation flow#12
Merged
feat(workflow): implement retry tracking and escalation flow#12
Conversation
Refined 8 core skills from "superpower" context to minimal Pichu architecture: - commander: 329 → 123 lines (63% reduction), added "never implement yourself" rule - verification: 58 → 35 lines (40% reduction), removed redundant "Iron Law" - brainstorming: 54 → 46 lines (15% reduction), added approval signals - using-skill: 47 → 42 lines (11% reduction), trimmed verbose description - background-tasks: added error handling (40 → 43 lines) - writing-plans: added plan review checklist (27 → 30 lines) - subagent-dev: added "why fresh" and "when not to use" (43 → 48 lines) - reviewer: maintained lean structure (44 lines) Created references/ folder structure for detailed documentation: - Plan templates, handoff scripts, task templates - Telegram format examples, verification patterns - Review checklists, confidence scoring, notification templates Reduced identity.md from 24 → 2 lines (92% reduction). Total estimated savings: ~3,000 tokens per message (65% reduction) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add comprehensive retry tracking and escalation workflow to prevent
infinite loops and ensure user awareness of persistent failures.
Changes:
- reviewer: Add 3-retry limit with escalation, update decision matrix
- background-tasks: Add escalation triggers and failure tracking
- brainstorming: Add explicit confirmation step before proceeding
- subagent-dev: Add post-verification step with retry handling
- task-state.sh: Add increment_retry, get_retry_count, reset_retry API
- references/workflow.md: Create comprehensive workflow documentation
- project-status.md: Clear active work status
Workflow flow:
User → Commander → Brainstorm → Confirm → Design → Plan → Background
→ Subagent → Review → Verify → Complete
↑ ↓ ↑ ↑
└─── 3 retries ←─┘ └── Escalate ←─┘
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements comprehensive retry tracking and escalation workflow to prevent infinite loops and ensure user awareness of persistent failures.
Changes
Workflow Skills
Infrastructure
increment_retry,get_retry_count,reset_retry)Workflow Flow
Test Plan
Token Efficiency
Main workflow skills: ~2,000-2,500 tokens per message (down from ~5,000 before optimization)
Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com