UNPKG

hey-claudio

Version:

šŸ¤– HeyClaudio: AI-powered development assistant with R.A.D.A.R. analysis + C.I.D.E.R. atomic issues for Claude IDE

232 lines (167 loc) • 6.07 kB
--- allowed-tools: Bash(echo:*), Bash(cut:*), Bash(find:*), Bash(grep:*), Bash(head:*), Bash(git:*), Bash(npm:*), Bash(date:*), Bash(mkdir:*), Bash(cat:*), Bash(sed:*), Read, Write, Edit description: Work on specific issue following C.I.D.E.R. methodology --- # šŸ”§ C.I.D.E.R. Issue Execution **Work on specific issue following C.I.D.E.R. methodology** **Usage**: `/project:cider:work ISSUE_NUMBER SCOPE` **Arguments**: `$ARGUMENTS` --- ## What This Command Does Executes development work on a **specific atomic issue** using structured C.I.D.E.R. methodology: - **C**ontextualizar: Load issue context and current state - **I**terar: Plan work approach and break into steps - **D**ocumentar: Record decisions and progress - **E**jecutar: Implement with testing and validation - **R**eflexionar: Update status and plan next steps --- ## šŸ“‹ Parsing Work Arguments !echo "šŸ”§ C.I.D.E.R. Issue Execution" !echo "Arguments: $ARGUMENTS" !ISSUE_NUMBER=$(echo "$ARGUMENTS" | cut -d' ' -f1) !SCOPE=${2:-"full"} !echo "šŸŽÆ **Issue**: #$ISSUE_NUMBER" !echo "šŸ“– **Scope**: $SCOPE" --- ## šŸ” CONTEXTUALIZAR (Load Issue Context) ### Load Issue Details !ISSUE_FILE=$(find .claude/epics/ -name "issue-$ISSUE_NUMBER-*.md" | head -1) !if [ -f "$ISSUE_FILE" ]; then echo "āœ… Found issue file: $ISSUE_FILE" echo "šŸ“‹ **Issue Details**:" else echo "āŒ Issue #$ISSUE_NUMBER not found" echo "šŸ’” Available issues:" find .claude/epics/ -name "issue-*.md" | head -5 exit 1 fi ### Issue Content @$ISSUE_FILE ### Current Project State @.claude/current/project-state.md ### Active Epic Status @.claude/current/active-epic.md --- ## šŸŽÆ ITERAR (Plan Work Approach) Based on the issue details above, let me plan the work approach: ### Issue Analysis - **Complexity**: [Simple/Medium/Complex based on issue content] - **Estimated Time**: [From issue file] - **Dependencies**: [Any blocking requirements] - **Files Affected**: [From issue specification] ### Work Plan !echo "šŸ“‹ **Work Plan for Issue #$ISSUE_NUMBER**:" !if [ "$SCOPE" = "quick" ]; then echo "⚔ **QUICK MODE**: Focus on core functionality only" echo "1. Minimal viable implementation" echo "2. Basic testing" echo "3. Essential documentation" elif [ "$SCOPE" = "full" ]; then echo "šŸŽÆ **FULL MODE**: Complete implementation" echo "1. Complete feature implementation" echo "2. Comprehensive testing" echo "3. Full documentation" echo "4. Code review preparation" else echo "šŸ”§ **CUSTOM SCOPE**: $SCOPE" echo "Work tailored to specified scope" fi ### Environment Validation !echo "šŸ” **Environment Check**:" !git status --porcelain || echo "āš ļø Git not available" !if [ -f "package.json" ]; then echo "šŸ“¦ Node.js project detected" npm --version || echo "āš ļø npm not available" fi --- ## šŸ“ DOCUMENTAR (Session Tracking) ### Create Session File !SESSION_FILE=".claude/sessions/$(date +%Y-%m)/$(date +%Y%m%d_%H%M)_issue-$ISSUE_NUMBER.md" !mkdir -p "$(dirname "$SESSION_FILE")" !cat > "$SESSION_FILE" << EOF # Session: Issue #$ISSUE_NUMBER - $(date +%Y-%m-%d) ## Session Info - **Issue**: #$ISSUE_NUMBER - **Scope**: $SCOPE - **Started**: $(date +%H:%M:%S) - **Status**: šŸ”„ IN_PROGRESS ## Issue Summary [From $ISSUE_FILE] ## Work Plan [Approach planned above] ## Progress Log - $(date +%H:%M) - Session started - [ ] Phase 1: Setup and validation - [ ] Phase 2: Core implementation - [ ] Phase 3: Testing and validation - [ ] Phase 4: Documentation and cleanup ## Files Modified [To be updated during work] ## Important Decisions [Document key decisions made during implementation] ## Challenges & Solutions [Record any obstacles and how they were solved] ## Next Steps [To be updated at session end] EOF !echo "šŸ“ Session file created: $SESSION_FILE" --- ## šŸš€ EJECUTAR (Implementation Phase) ### Pre-Implementation Checklist !echo "āœ… **Pre-Implementation Checklist**:" !echo "- [x] Issue loaded and understood" !echo "- [x] Work plan created" !echo "- [x] Session tracking started" !echo "- [ ] Environment validated" !echo "- [ ] Dependencies checked" ### Implementation Focus Based on the issue requirements, I'll now focus on: 1. **Understanding Requirements**: What exactly needs to be built? 2. **Current State Analysis**: What exists already? 3. **Implementation Strategy**: What's the best approach? 4. **Testing Strategy**: How will we validate success? Let me start the implementation: ### Phase 1: Setup & Analysis [Implementation steps will be guided by the specific issue requirements] ### Phase 2: Core Development [Focus on the main deliverables specified in the issue] ### Phase 3: Testing & Validation [Ensure acceptance criteria are met] --- ## šŸ”„ REFLEXIONAR (Progress Update) ### Update Issue Status !sed -i 's/Status.*TODO/Status: šŸ”„ IN_PROGRESS/' "$ISSUE_FILE" 2>/dev/null || echo "Could not update issue status" ### Update Active Epic !cat > .claude/current/active-epic.md << EOF # Active Epic: [Epic Name] ## Current Status šŸ”„ **ACTIVE** - Working on Issue #$ISSUE_NUMBER ## Current Issue - **Issue #$ISSUE_NUMBER**: Currently in development - **Started**: $(date +%Y-%m-%d %H:%M) - **Scope**: $SCOPE - **Session**: $SESSION_FILE ## Progress - [x] Issue analysis completed - [x] Work plan created - [ ] Implementation in progress - [ ] Testing phase - [ ] Completion and review ## Next Steps Continue implementation following C.I.D.E.R. methodology EOF --- ## šŸŽÆ Work Session Active! ### Current Focus **Issue #$ISSUE_NUMBER** is now the active development focus. ### Available Actions - Continue implementation following the issue requirements - Update progress in session file: `$SESSION_FILE` - Test and validate work against acceptance criteria - Use `/project:cider:status` to check overall progress ### Session Management - **Session File**: `$SESSION_FILE` - **Issue File**: `$ISSUE_FILE` - **Current Status**: šŸ”„ IN_PROGRESS --- **šŸ”§ Ready to implement! Follow the issue requirements and update progress as you work.**