# Task Board
_Updated: 2026-04-28_

<!--
  Canonical layout. One block per task. Per-task deep context lives in
  .tasks/<task-slug>.md (created by using-tasks when a task becomes active
  or paused). Historical Done entries dropped — git log is the history.

  Status legend:
    🔴 Active     — only one at a time
    🟡 Paused     — in progress, resumable
    ⚪ Ready      — defined, not started
    🟢 Done       — kept until merged
    🔵 Blocked    — waiting on external input
-->

## ⚪ [cleanup-stale-skill-installs] — remove old wiki-maintainer and task-status-wiki installs
**Status:** ready
**Where I stopped:** (not started)
**Next action:** `rm -rf ~/.claude/skills/wiki-maintainer ~/.claude/skills/task-status-wiki` then verify only `using-wiki` and `using-tasks` remain
**Branch:** (no branch — local cleanup)

---

## ⚪ [compress-dedup] — resolve compress vs caveman-compress duplication
**Status:** ready
**Where I stopped:** (not started) — noticed during initial migration that both skills ship identical `scripts/` subtrees (`compress.py`, `cli.py`, `detect.py`, `validate.py`, `benchmark.py`)
**Next action:** `diff -r skills/compress skills/caveman-compress`; decide if one is canonical and the other should be removed (or aliased)
**Branch:** (not started)

---

## ⚪ [install-ps1] — PowerShell-native install.ps1
**Status:** ready
**Where I stopped:** (not started) — `install.sh` already works in git-bash on Windows, so this is convenience for PS-only users
**Next action:** mirror `scripts/install.sh` logic in PowerShell (copy `skills/<name>/` → `~/.claude/skills/<name>/`, support `$env:CLAUDE_SKILLS_DIR` override)
**Branch:** (not started)

---

## ⚪ [archive-roundtrip-test] — smoke-test for .skill archive shape
**Status:** ready
**Where I stopped:** (not started) — caught the PowerShell-Compress-Archive backslash bug manually; a smoke-test would catch the next regression automatically
**Next action:** add a script that builds `dist/<name>.skill`, unzips into a temp dir, and `diff -r` against `skills/<name>/`. Fail on any difference. Run from CI or pre-commit if we add one
**Branch:** (not started)

---

## ⚪ [active-platform-tuning] — tune active-platform triggers based on real usage
**Status:** ready
**Where I stopped:** (not started) — current triggers are best-guess; haven't observed real misfires/missed-fires yet
**Next action:** keep a tally of times the skill should have triggered but didn't (or vice versa); revise the description / trigger list after ~5 real signals. Also add WSL handling explicitly if it comes up
**Branch:** (not started)

---

## ⚪ [active-platform-eval] — run formal skill-creator eval loop on active-platform
**Status:** ready
**Where I stopped:** (not started) — depends on having ~5 real interactions logged for tuning context
**Next action:** invoke `skill-creator` to set up an eval set for `active-platform`; benchmark current vs revised description
**Branch:** (not started)
**Blocker:** waits on `active-platform-tuning` to gather signals first

---

## ⚪ [skills-grouping-revisit] — revisit flat vs grouped skills/ layout if count grows past ~30
**Status:** ready
**Where I stopped:** (not started) — current 14 skills fit fine in flat `skills/`; threshold for revisiting is ~30
**Next action:** when triggered (skill count crosses threshold), evaluate variant B (grouped by family) vs variant C (flat + manifest) from the original brainstorm in `.wiki/concepts/repo-layout.md`
**Branch:** (not started)