Workflow Archival Skill

Purpose

Archive completed workflows and update the context/ wiki with learnings. This skill runs at the final step of any workflow or when explicitly requested by the user.

Trigger

• Workflow reaches final step (automatic)
• User explicitly says "archive this workflow"

Process Overview

┌─────────────────────────────────────────────────────────────────┐
│                    WORKFLOW ARCHIVAL                             │
└─────────────────────────────────────────────────────────────────┘
                              │
    ┌─────────────────────────┼─────────────────────────┐
    ▼                         ▼                         ▼
┌─────────────┐       ┌─────────────┐       ┌─────────────┐
│ 1. Archive  │       │ 2. Update   │       │ 3. Sync to  │
│   Workflow  │       │   Context   │       │    Jira     │
│             │       │    Wiki     │       │             │
│ Move folder │       │ Extract     │       │ Batch sync  │
│ to archive/ │       │ learnings   │       │ final state │
└─────────────┘       └─────────────┘       └─────────────┘

---

Step 1: Archive Workflow Folder

Action: Move workflow folder from active/ to archive/

Naming: {date}-{workflow-type}-{identifier}/

Example:

workflow/active/development-EPIC-45/
    ↓
workflow/archive/2026-01-09-development-EPIC-45/

Preserved:

• workflow.md - Final state of workflow manifest
• state.json - Complete gate history and metrics
• stories/*.md - All story iteration history
• decisions.md - All decisions made

---

Step 2: Update Context Wiki

The context/ folder serves as the project wiki. After archiving, update it with learnings from the completed workflow.

2.1 Copy Stories to Context (Development Workflows)

workflow/archive/{date}-development-{id}/stories/*.md
    ↓ (copy)
context/stories/*.md

Note: Stories in context/stories/ serve as historical reference for future agents.

2.2 Update Solution Summary

If the workflow introduced significant changes, update context/solution-summary.md:

• New architectural patterns
• New modules or features
• Changed constraints or conventions

2.3 Update Project Summaries

If specific modules were affected, update relevant context/project/*.md:

• New files or directories
• Changed integration points
• New patterns discovered

2.4 Extract Learnings

From workflow/archive/{name}/state.json, extract:

• Patterns: Reusable approaches that worked
• Pitfalls: Issues to avoid in future workflows
• Metrics: Time spent, iterations needed, gates passed/failed

Add significant learnings to appropriate context files.

---

Step 3: Batch Sync to Jira

Sync all pending items from state.json to Jira:

3.1 Sync Pending Items

"pending_sync": {
  "decisions": [...],    → Add to Jira comments / Confluence decision log
  "blockers": [...],     → Update blocker status in Jira
  "learnings": [...],    → Add to Confluence documentation
  "comments": [...]      → Add to Jira ticket comments
}

3.2 Update Story Status

For each story in the workflow:

• Transition to final status (Done, Closed)
• Add completion summary as comment

3.3 Log Sync

Update sync_history in archived state.json:

{
  "timestamp": "2026-01-09T18:00:00Z",
  "trigger": "workflow_archival",
  "items_synced": ["story_status", "decisions", "comments", "learnings"]
}

---

Agent Responsibility

Orchestrator runs this skill:

1. Detects workflow completion (final step reached)
2. Executes archival process
3. Notifies stakeholder of completion

---

Archival Checklist

• Workflow folder moved to archive/ with date prefix
• Stories copied to context/stories/ (for dev workflows)
• context/solution-summary.md updated (if needed)
• context/project/*.md updated (if needed)
• Pending Jira sync items processed
• Story statuses updated in Jira
• Completion notification sent to stakeholder

---

Example: Development Workflow Archival

Before Archival

workflow/active/development-EPIC-45/
├── workflow.md           # Status: Step 9 (Closure)
├── state.json            # All gates passed
├── stories/
│   ├── PROJECT-123.md    # Done, 2 iterations
│   ├── PROJECT-124.md    # Done, 1 iteration
│   └── PROJECT-125.md    # Done, 3 iterations
└── decisions.md          # 3 decisions logged

Archival Actions

1. Move folder:

   → workflow/archive/2026-01-09-development-EPIC-45/
   

2. Copy stories to context:

   → context/stories/PROJECT-123.md
   → context/stories/PROJECT-124.md
   → context/stories/PROJECT-125.md
   

3. Update solution summary:

   ## Current Focus
   - Completed: EPIC-45 (User Dashboard Enhancements)
   - Active: [next epic or "None"]
   

4. Sync to Jira:

   • PROJECT-123: Transition to "Done", add summary comment
   • PROJECT-124: Transition to "Done", add summary comment
   • PROJECT-125: Transition to "Done", add summary comment
   • EPIC-45: Transition to "Done" if all stories complete

5. Notify stakeholder:

   ✅ Workflow Complete: EPIC-45 - User Dashboard Enhancements
   
   Stories Completed: 3
   Total Iterations: 6
   Time in Workflow: 4h 30m
   
   All stories deployed and verified.
   

---

After Archival

workflow/
├── active/                                    # Empty
└── archive/
    └── 2026-01-09-development-EPIC-45/       # Preserved for history

context/
├── solution-summary.md                        # Updated
├── project/
│   └── ...
└── stories/
    ├── PROJECT-123.md                         # Copied from workflow
    ├── PROJECT-124.md
    └── PROJECT-125.md

---

Integration Points

• Reads: workflow/active/{name}/ (all files)
• Writes: workflow/archive/, context/
• Syncs: Jira (via Atlassian MCP tools)
• Notifies: Stakeholder (via Orchestrator)

---

When NOT to Archive

• Workflow is blocked and waiting for resolution
• User explicitly pauses the workflow
• Workflow failed and needs investigation (mark as failed, don't archive)

For failed workflows, keep in active/ with status "Failed" until resolved or user requests archival.