# Task Board _Updated: 2026-05-05_ ## 🟑 [skill-readmes] β€” write English README.md for every skill + translate root README **Status:** paused **Where I stopped:** infra-skill cluster done β€” READMEs for `project-bootstrap`, `setup-wiki`, `setup-tasks`, `using-wiki`, `using-tasks`; root README translated; cross-links between all five skills wired up **Next action:** continue with the next batch β€” suggest the caveman cluster (`caveman`, `caveman-commit`, `caveman-review`, `caveman-help`, `caveman-compress`, `compress`) since they form a coherent group; or jump to `active-platform`, `find-skills`, `setup-context7`, `using-context7`, `using-markitdown` if the caveman cluster needs deduplication first (see `compress-dedup` task) **Branch:** master --- ## βšͺ [bootstrap-skill-deps-check] β€” refactor project-bootstrap Step 5.6 into a generic skill-dependencies check (replaces per-skill `Step 5.X` mirror shape) **Status:** ready **Where I stopped:** (not started) β€” design agreed in chat 2026-05-05 after `[interns-skills-mvp]` shipped: adding `delegate to interns when allowed` to the canonical CLAUDE.md template made it visible that every new trigger would need its own `Step 5.X` detector mirror, which doesn't scale. Decision: collapse Step 5.6 (superpowers plugin) and the deferred `[bootstrap-recommend-projects-meta]` into a single generic `Step 5.6` that reads the canonical trigger list and maps each line to a fulfiller (skill or plugin) for missing-deps detection. Hard rule "never auto-install" carries over verbatim β€” chat-only recommendation block with copy-pasteable install commands **Next action:** Read `.tasks/bootstrap-skill-deps-check.md` for the full spec β€” initial triggerβ†’fulfiller seed table is in the Notes section. Write `.wiki/concepts/bootstrap-skill-deps-check.md` design page first (rationale: why generic over per-skill mirrors, kind: skill vs plugin distinction, MCP server caveat). Then edit `skills/project-bootstrap/SKILL.md` Step 5.6 in place, bump `version:` 1.6.0 β†’ 1.7.0. Update `skills/project-bootstrap/README.md` Workflow Step 5.6 description. Rebuild + install. Close `[bootstrap-recommend-projects-meta]` with a note in commit message **Branch:** (not started) --- ## βšͺ [bootstrap-recommend-projects-meta] β€” Step 5.7 in project-bootstrap: recommend `setup-projects-meta` if MCP tools missing **Status:** superseded **Where I stopped:** (not started) β€” opened as follow-up to `[bootstrap-projects-meta-trigger]`. The `check across all projects` trigger is now in every CLAUDE.md template, but on a fresh machine without `projects-meta-mcp` registered the trigger is silently no-op until the user verbally asks for cross-project work **Next action:** **superseded by `[bootstrap-skill-deps-check]`** (2026-05-05) β€” that task absorbs this one into a generic `Step 5.6` that walks the whole canonical trigger list, not just projects-meta. Kept here for git-log archaeology; close once `[bootstrap-skill-deps-check]` ships **Branch:** (not started) **Blocker:** waits on observing a real fresh-machine bootstrap that silently misses the dependency β€” defer until we see the failure mode in practice --- ## βšͺ [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//` β†’ `~/.claude/skills//`, 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/.skill`, unzips into a temp dir, and `diff -r` against `skills//`. 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) --- ## βšͺ [refresh-project-bootstrap] β€” Run the `project-bootstrap` skill in this repo to refresh its layout to the canonical state (git, .gitignore, README.md, .wiki/, .tasks/, CLAUDE.md). The skill handles both greenfield bootstrap and refresh of existing repos. **Status:** ready **Where I stopped:** (not started) **Next action:** Invoke the `project-bootstrap` skill at the repo root, confirm each file write, push to main. **Branch:** n/a ---