25dd3ab2d2
Phase 10.1: Aggressive Workflow Modularization - 5 plan(s) in 3 wave(s) - Wave 1: Foundation (rename files, analyze boundaries, user approval) - Wave 2: 3 parallel extractions (batch-ui, status, confirmation) - Wave 3: Integration verification and UAT - Ready for execution Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
7.6 KiB
7.6 KiB
phase, plan, type, wave, depends_on, files_modified, autonomous, must_haves
| phase | plan | type | wave | depends_on | files_modified | autonomous | must_haves | ||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 10.1-aggressive-workflow-modularization | 05 | execute | 3 |
|
|
false |
|
Purpose: Ensure the modularized architecture is complete and all functionality works correctly. Output: Verified working system, documentation of final state, UAT sign-off.
<execution_context> @/home/luc/.claude/get-shit-done/workflows/execute-plan.md @/home/luc/.claude/get-shit-done/templates/summary.md </execution_context>
@.planning/PROJECT.md @.planning/ROADMAP.md @.planning/STATE.md @.planning/phases/10.1-aggressive-workflow-modularization/10.1-CONTEXT.md @.planning/phases/10.1-aggressive-workflow-modularization/10.1-02-SUMMARY.md @.planning/phases/10.1-aggressive-workflow-modularization/10.1-03-SUMMARY.md @.planning/phases/10.1-aggressive-workflow-modularization/10.1-04-SUMMARY.md @n8n-workflow.json @n8n-batch-ui.json @n8n-status.json @n8n-confirmation.json Task 1: Verify main workflow structure and node count n8n-workflow.json (read only) Analyze final main workflow state:-
Count total nodes (target: 50-80)
-
Verify main workflow contains only:
- Telegram Trigger (1 node)
- Authentication checks (2 nodes)
- Keyword routing (5-10 nodes)
- Execute Workflow calls to sub-workflows (6-8 nodes)
- Result handlers after sub-workflow calls (10-15 nodes)
- Error handling (2-3 nodes)
-
List all Execute Workflow nodes and their targets:
- Execute Text Update -> n8n-update.json
- Execute Callback Update -> n8n-update.json
- Execute Action -> n8n-actions.json
- Execute Text Logs -> n8n-logs.json
- Execute Batch UI -> n8n-batch-ui.json
- Execute Container Status -> n8n-status.json
- Execute Confirmation -> n8n-confirmation.json
-
Check for orphan nodes (nodes with no connections)
-
Verify all TODO_DEPLOY_*_WORKFLOW placeholders are documented
Output a summary:
- Final node count
- Node breakdown by category
- List of Execute Workflow nodes
- Any issues found
- Node count verified and documented
- No orphan nodes
- All sub-workflow calls identified Main workflow structure verified and documented.
Content:
# Sub-workflow Deployment Guide
## Overview
Phase 10.1 extracted main workflow from 192 nodes to ~XX nodes by creating domain sub-workflows.
## Sub-workflows
| File | Purpose | Deploy Order |
|------|---------|--------------|
| n8n-update.json | Container update operations | 1 (already deployed) |
| n8n-actions.json | Container start/stop/restart | 2 (already deployed) |
| n8n-logs.json | Container log retrieval | 3 (already deployed) |
| n8n-batch-ui.json | Batch selection UI | 4 |
| n8n-status.json | Container list/status | 5 |
| n8n-confirmation.json | Confirmation dialogs | 6 |
## Deployment Steps
### For each new sub-workflow (batch-ui, status, confirmation):
1. Import the JSON file into n8n
2. Note the workflow ID assigned by n8n
3. Search main workflow for the TODO placeholder:
- `TODO_DEPLOY_BATCH_UI_WORKFLOW`
- `TODO_DEPLOY_STATUS_WORKFLOW`
- `TODO_DEPLOY_CONFIRMATION_WORKFLOW`
4. Replace placeholder with actual workflow ID
5. Re-import main workflow
### Existing Sub-workflows (already deployed)
- Container Update: ID `7AvTzLtKXM2hZTio92_mC`
- Container Actions: ID `fYSZS5PkH0VSEaT5`
- Container Logs: ID `oE7aO2GhbksXDEIw`
## Rollback
Backup files created during extraction:
- `n8n-workflow.json.backup-batch` - Before batch extraction
- `n8n-workflow.json.backup-status` - Before status extraction
- `n8n-workflow.json.backup-confirm` - Before confirmation extraction
To rollback, copy the appropriate backup file to n8n-workflow.json and re-import.
## Architecture
\`\`\`
n8n-workflow.json (orchestrator)
├── Trigger + Auth + Routing
├── Execute Update -> n8n-update.json
├── Execute Actions -> n8n-actions.json
├── Execute Logs -> n8n-logs.json
├── Execute Batch UI -> n8n-batch-ui.json
│ ├── (calls n8n-update.json for batch updates)
│ └── (calls n8n-actions.json for batch actions)
├── Execute Status -> n8n-status.json
└── Execute Confirmation -> n8n-confirmation.json
└── (calls n8n-actions.json for confirmed actions)
\`\`\`
-
File structure check:
ls n8n-*.jsonshould show 7 files (workflow + 6 sub-workflows)- Main workflow has expected reduced node count
-
JSON validity:
- All JSON files parse correctly
- All sub-workflows have Execute Workflow Trigger
-
Deployment placeholders:
- Search n8n-workflow.json for "TODO_DEPLOY" - should find 3 new placeholders
- Existing workflow IDs still referenced correctly
-
After n8n deployment (when ready):
- Test
/listcommand - should show container list - Test
/stop <container>- should show confirmation - Test batch mode:
/stopthen select multiple containers - Test update flow
- Test logs command
- Test
Respond with:
- "approved" if structure looks correct
- "issues: [description]" if problems found Type "approved" or describe issues found
<success_criteria>
- Main workflow reduced to target size (50-80 nodes)
- 6 sub-workflows total (3 existing + 3 new)
- All TODO placeholders documented
- Deployment guide created
- User sign-off on structure </success_criteria>