Skip to content

mokhtarabadi/cognitive-lead-hq / skill-templates/kanban-lifecycle

kanban-lifecycle

Verified

Unified Kanban lifecycle — task generation, lint validation, META bundling, completion archiving, and flat-to-V6 migration in one meta skill.

FileKindSize
SKILL.mdskill md1.9 KB
templates/01-generate.mdmarkdown12.1 KB
templates/02-lint.mdmarkdown577 B
templates/03-bundle.mdmarkdown8.8 KB
templates/04-archive.mdmarkdown3.2 KB
templates/05-migrate.mdmarkdown1.9 KB

templates/04-archive.md

View on GitHub
## Part 4: Archive Tasks Skill (from `archive-tasks`)

# Archive Tasks Skill

## Purpose

Prevents the `tasks/completed/` directory from accumulating hundreds of task files by periodically compacting completed tasks into dense, single-file milestone summaries in `docs/history/`.

## Workflow

1. **Scan completed tasks** for the current milestone:

```bash
ls tasks/completed/*.md
```

2. **Read each file** and extract:
   - Task number and title
   - Type (bug/improvement/feature)
   - Source (from the `**Source:**` metadata line)
   - Execution Log & Reasoning (architectural reasoning)
   - Key files modified

3. **Generate a milestone summary** at `docs/history/milestone-X-summary.md` with the following structure:

   ```markdown
   # Milestone X Summary

   **Date:** YYYY-MM-DD
   **Tasks Compacted:** N

   ## Source Distribution

   | Source       | Count |
   | ------------ | ----- |
   | orchestrator | N     |
   | telegram     | N     |
   | manager      | N     |

   ## Architectural Changes

   [Dense summary of all architectural changes across the milestone]

   ## Files Modified

   | File         | Change      |
   | ------------ | ----------- |
   | path/to/file | description |

   ## Criteria Met

   | Task | Acceptance Criteria | Status |
   | ---- | ------------------- | ------ |
   | XX   | [Extracted criteria from the completed task's `## Acceptance Criteria` section] | ✅ Met |

   ## Individual Task Summaries

   ### Task XX: Title

   - **Type:** bug|improvement|feature
   - **Source:** [orchestrator|telegram|manager]
   - **Reasoning:** [condensed execution log]
   ```

4. **Create the `docs/history/` directory** if it does not exist:

```bash
mkdir -p docs/history
```

5. **Move completed files to archive**:

```bash
git mv tasks/completed/*.md tasks/archive/
```

*Note: For untracked task files, use the supported native file-management operation to move them. Stage the moved files only through `custom_context_stage_and_inject_diff`; never run `git add` directly.*

6. **Memory Validation:** After compacting tasks, audit the project memory bank for stale or superseded entries:
   a. Call `list_namespaces` to enumerate all memory namespaces.
   b. For each namespace, call `search_memory` using keywords from the archived tasks.
   c. Identify memories that reference archived/completed task files or superseded workflows.
   d. Detect duplicates: if two memories in the same namespace cover the same topic and one references a newer date or task, flag the older one as superseded.
   e. Output a `## Stale Memory Report` listing all flagged memories with their namespace, key, and reason for flagging.
   f. Wait for Manager approval before calling `delete_memory` on any flagged entry. NEVER auto-delete memories without explicit Manager confirmation.

7. **Stage the new summary and moved files**:

Call `custom_context_stage_and_inject_diff` with the active task file and an explicit `modified_files` list containing the generated milestone summary and every moved task-file path. Do not run `git add` directly.

## When to Run

Run this skill at the end of each milestone or when `tasks/completed/` contains more than 20 files. The milestone number should be determined by reading the highest existing milestone in `docs/history/` and incrementing by one.

---

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall