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

chore(skills): delete setup-tasks/setup-wiki — мета в сервисе (#983)

Browse Source 
Нечего настраивать (решение 14/15). Свип ссылок: project-bootstrap v2.1.0
(Steps 3/4 → mappa, манифест без setup-строк), project-discipline (Rule 1),
setup-projects-meta README, using-tasks/using-wiki README.
This commit is contained in:
vitya
2026-08-24 16:45:59 +03:00
parent c5ebde174d
commit afca818a05
5 changed files with 39 additions and 45 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -1,7 +1,7 @@
---
name: project-bootstrap
author: ours
version: 2.0.1
version: 2.1.0
description: >
Initializes or upgrades a project in the current folder: git, .gitignore, README.md,
.wiki/ using Karpathy's method, .tasks/ for task tracking, AGENTS.md (canon) with
@@ -178,13 +178,14 @@ If it exists — leave it untouched.
---
## Step 3 — .wiki/
## Step 3 — вики (mappa, решение 14/15)
**Delegate to the `setup-wiki` skill.** It handles greenfield creation, canon migration, and the no-op case (already canon) uniformly, with its own confirmation gate. Don't recreate the layout inline here — that's how drift happens.
If `setup-wiki` is not installed on this machine, **stop** and tell the user: project-bootstrap requires `setup-wiki` (and `setup-tasks`) installed. Don't fall back to ad-hoc creation.
**Reference (for context only — `setup-wiki` is the source of truth):** the canonical layout per Karpathy (gist: https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f) and `using-wiki`:
**Канал — mappa:** вики проекта = сущности `type=wiki` в сервисе (решения 14/15:
мета в сервисе). Ничего файлового создавать не нужно; операции — `using-wiki`
v2 (mappa wiki-тулы). Файловый `.wiki/` — только для проектов вне mappa
(легаси): layout по Karpathy (gist: https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f).
`setup-wiki` умер (нечего настраивать) — при необходимости создания страниц
используй `wiki.create` под лизом (см. using-wiki).
```
.wiki/
@@ -311,13 +312,14 @@ each get a `.gitkeep` so git tracks them.
---
## Step 4 — .tasks/
## Step 4 — таски (mappa, решение 14/15)
**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 `setup-tasks` is not installed, **stop** and tell the user — same rule as Step 3.
**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`.
**Канал — mappa:** борд проекта = сущности `type=task` в сервисе (решения
14/15: мета в сервисе). Ничего файлового создавать не нужно; операции —
`using-tasks` v2 (mappa task-тулы). Файловый `.tasks/` — только для проектов
вне mappa (легаси: `STATUS.md` + per-task файлы). `setup-tasks` умер
(нечего настраивать) — таски создаются через `task_create` под лизом
(см. using-tasks/task-format).
---
@@ -474,8 +476,6 @@ Skills used to initialize this project's `.wiki/` and `.tasks/` layout, with the
| Skill | Version | Role |
|---|---|---|
| `project-bootstrap` | <version> | orchestrator |
| `setup-wiki` | <version> | wiki canonical layout |
| `setup-tasks` | <version> | tasks canonical layout |
| `project-discipline` | <version> | cross-project policy |
| `setup-interns` | <version> | interns MCP server install (one-time, per machine) |
| `using-interns` | <version> | interns runtime policy + per-session permission grant |