OpeItcLoc03/claude-skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: split tasks — using-tasks (policy) + setup-tasks (one-time)

Browse Source 
Mirror the wiki split. Rename `task-status-wiki` → `using-tasks` (preserves
file history via `git mv`). Strip the "Initialization" section out — that
content moves to the new `setup-tasks` skill, which owns greenfield
creation and migration.

`setup-tasks` has 6 phases (sanity → discovery → plan + confirm → backup →
greenfield/migrate → verify → report) and two modes:
- greenfield: write `.tasks/STATUS.md` with the canonical board template
  (emoji legend in a comment block; no per-task files at bootstrap — they
  get created on demand by using-tasks when actual tasks are added)
- migrate: detect old flat STATUS.md (no emoji, plain `## Done`/`## In
  Progress` sections), back it up, then walk the user *interactively*
  through each task to extract slug / status / branch / where-stopped /
  next-action. Never auto-parses the old format — too varied, real work
  at stake.

`using-tasks` Prerequisites section delegates to `setup-tasks` when the
board is missing or non-canonical (no emoji, no per-task files).

`project-bootstrap` Step 4 now delegates to `setup-tasks`.

The user's manual follow-up after this commit:
  rm -rf ~/.claude/skills/{wiki-maintainer,task-status-wiki}/
to clean up the stale installs of the old names. (install.sh creates the
new ones but doesn't remove the old.)

This completes the three-commit refactor (a/b/c) tracked in
.tasks/STATUS.md.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
vitya
2026-04-28 13:26:46 +03:00
parent 36fe39e921
commit bd8c378f83
9 changed files with 253 additions and 75 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
skills/project-bootstrap/SKILL.md
View File

@@ -209,24 +209,11 @@ each get a `.gitkeep` so git tracks them.
## Step 4 — .tasks/
If `.tasks/` already exists — skip it, notify the user.
**Delegate to the `setup-tasks` skill.** It handles greenfield creation, migration from flat STATUS.md, and the no-op case uniformly, with its own confirmation gate. Don't recreate the layout inline.
If it does not exist — create the structure:
If `setup-tasks` is not installed, **stop** and tell the user — same rule as Step 3.
```
.tasks/
STATUS.md ← task board
```
Contents of `STATUS.md`:
```markdown
# Task Board
_Updated: <today's date>_
<!-- Tasks will appear here as work progresses.
Skill is activated by the phrase: use task management system -->
```
**Reference (for context only — `setup-tasks` is the source of truth):** the canonical layout is `.tasks/STATUS.md` (the board, with emoji status 🔴/🟡/⚪/🟢/🔵) plus `.tasks/<task-slug>.md` per active or paused task. The full pattern is documented in this repo at `.wiki/raw/setup-task-status-wiki.md`.
---