Przejdź do treści
Biblioteka skilli
Zarządzanie i produkt · Planowanie

init

/init

Konfiguruje w projekcie plan, backlog i dokument decyzji albo przenosi istniejące plany i zadania do wtyczki projektowej.

Repozytorium
claude-project ↗
Licencja
MIT
Ostatnia zmiana repozytorium
09.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
1
Przestarzałość

Brak sygnałów. Repozytorium zmienione 09.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Konfiguruje w projekcie plan, backlog i dokument decyzji albo przenosi istniejące plany i zadania do wtyczki projektowej.

Wyzwalacze z opisu

set up the projectprepara piano e compitimigra il progetto
Oryginalny opis (EN)

Set the project plugin up in the current project - the configuration and the plan, backlog and decisions docs - or migrate a project that already keeps a plan, tasks or decisions, with its own tools, onto the plugin. Use when the user asks to start keeping a plan, tasks or decisions here, or to move a project onto the plugin ("set up the project", "prepara piano e compiti", "migra il progetto", "/project:init").

Jak działa

  1. 1. Look
  2. 2. A new project
  3. 3. A migration
  4. The configuration
Sekcje z nagłówków SKILL.md, w oryginale · 77 linii, 1 263 słów
Podgląd SKILL.md
---
name: init
description: Set the project plugin up in the current project - the configuration and the plan, backlog and decisions docs - or migrate a project that already keeps a plan, tasks or decisions, with its own tools, onto the plugin. Use when the user asks to start keeping a plan, tasks or decisions here, or to move a project onto the plugin ("set up the project", "prepara piano e compiti", "migra il progetto", "/project:init").
---

# Setting a project up, or migrating one

The commands run with Bash from the project's folder: `node "<this skill's folder>/../../scripts/init.mjs" …`. Nothing is written before the user's yes.

## 1. Look

Run `init.mjs adopt`. It writes nothing. It finds the folder that holds a plan, a backlog or decisions (up to three levels down), the language of their headings, whether that folder is a git repo of its own, who holds tasks, the colleagues of Crew, and the parts of the project that cite a decision (`D-12`). It prints the configuration that would read them, and what reads and what does not.

- If `.claude/project.yaml` exists, say what it configures. If the project still has its own tools beside it (a configuration written to try the plugin), the migration is half done: go to 3 from the old tools, completing the configuration that is there with Edit. Otherwise stop, unless the user wants a change.
- If nothing is found, it is a **new project**: go to 2.
- If docs are found, it is a **migration**: go to 3.

## 2. A new project

Ask once, in the choice form, with the recommendation first, what the request leaves open:
- the docs' language (`en`, `it`; another one starts from `en` with its words overridden under `words:`);
- where the docs live: in the repo (`project/`, the default), or, for a public project whose plan stays private, in a **private repo of their own**, ignored by the project's: the docs' folder itself (`project/`, recommended), or a `private/` repo that holds them in `private/project/` beside other private things, such as manuals or assets. A submodule or a folder outside the repo is a path in `docs:` the user sets up;
- who besides Claude holds tasks (`people:`). Crew's colleagues, if the project has them, count by themselves. Where several people work on it, each with their own Claude, their GitHub logins go in `github: { logins: { Ann: ann-gh } }`, and private docs kept in sync among them take `sync: auto` (the project skill's Working together); each says who they are in `.claude/project.local.yaml`, `me: Ann`, which the start of a session writes from gh.

Then run `init.mjs --language it [--private project|private] [--docs <folder>] [--people "Claude,Ann"] [--name "<project>"]`. It writes the configuration and the docs that are missing, and never overwrites one. With `--private` it makes that folder a git repo on `main` and adds it to the project's `.gitignore`. Then fill the plan with the user: the phases and the first goals.

A project already set up, whose docs its repo keeps, makes them private later with `init.mjs private [--in private] [--write]`: the github skill's private docs.

Once it is written, look at GitHub with `github.mjs status`: when git or gh is missing or the project is not on GitHub, offer the `github` skill, which does each step on the user's yes.

## 3. A migration

Read what the survey found, and what else the project has around its docs:
- its own tools for them (scripts that number tasks or decisions, check the docs, serve a page);
- the hooks that start them (`.claude/settings.json`);
- the skills that tidy them;
- the instructions that cite them (AGENTS.md, CLAUDE.md, READMEs).

Then propose the migration as one numbered list, one decision per point, with what you recommend:

1. **The configuration**: the survey's, completed by what you read.
   - `people:` the user and whoever holds tasks.
   - `cites:` the survey's parts, plus sibling repos that cite the same numbers (`../app-*/src`).
   - `files:` names the survey did not guess, and the idea inbox.
   - `words:` headings that differ from the language's.
   - `page.port` only when the project wants a port of its own choosing: without it, each project gets its own, from its folder.
   - `extensions:` for the parts of an old page that belong to this project alone.
   - `documents:` the project's key documents (a GDD, a specification, a business plan), from its README and docs' index.
2b. **Decisions in another format**: a numbered list under a heading (`72. **Title** text`) moves into the table with `init.mjs adopt --decisions <file> "<heading>"`, the numbers kept, so every citation stays true; the list leaves a link in its place. Proposals still open go under the table's heading of what is to decide, by hand.
2. **What does not read**: lines of the backlog in another format, decisions without the table, a plan whose steps are checkboxes. The plan's checkbox steps under its goals go into the backlog with `init.mjs adopt --steps`: open ones to do, done ones archived, their sub-lines joined to the text. Other formats you convert with Edit, line by line, after the user's yes. A specifications' document of its own (a functional spec, requirements) becomes the core's SPECS.md with `specs.mjs adopt <file>`: see first what it would do, then `--write` on the yes; its specs numbered S-1, S-2…, its text as it was.
2c. **Tasks kept in another tool** (Trello, Jira, Linear, Notion, GitHub Projects, a spreadsheet): propose bringing them in once with the `project` skill's import from another tool, from an export the user gives or the service's connector; nothing stays in sync.
3. **The old tools** the plugin replaces, point by point: what each did, which command of the plugin does it now (see the `project` and `tidy` skills), and that it goes. A tool that does something the plugin does not keeps its place, or becomes an extension.
4. **The texts that cite them**: the instructions, the docs' index, the colleagues' memory. Each line rewritten to the plugin's commands.

On the user's yes, point by point:
- `init.mjs adopt --write`, which writes the configuration and the missing docs, and never overwrites one; `--language`, `--people "Claude,Ann"` and `--name "…"` before `--write` put the user's choices over what adopt found;
- `--steps` if they chose it;
- the configuration's additions with Edit;
- then the rest.

At the end run `check.mjs --fix`, which gives every doc of the plugin its frontmatter (the core with its archive, notes and releases, and the project-management docs beside it or in `documents:`; not the folders added inside the docs, nor the project's own markdown), and compare the plugin's outputs with the old tools' ones while they are still there (the backlog's list, the next decision number, the check). Tell the user what changed and what to verify: the panel (`/project-panel`) and the page (`http://localhost:<page.port>`), from a new session. Commit only when they ask; in a private docs repo, with `git -C <its folder>`.

## The configuration

`.claude/project.yaml`:

```yaml
name: My app                 # the title of the README when left out
language: it
docs: private/project        # the docs' folder, from the project's root
people: [Claude, Ann]
cites: [private/project, .claude, src, docs]   # where a decision number may be cited; a * in a part matches any name
markdown: [private/project]  # the folders whose .md the check looks after (default: the docs and their subfolders)
files: { inbox: IDEAS.md }   # a core file under another name; the core names are English in every language
repos: [{ name: app, path: . }, { name: docs, path: private }]   # the commits the page counts
page: { port: 5790 }         # optional: by default a port of 5800–5999 from the project's folder
extensions: []               # modules that add the project's own parts to the page and links to the panel
documents: [{ name: GDD, path: private/project/GDD.md }]   # the key documents, in the panel and the page
words: {}                    # any heading or marker of the language, overridden
```

Wersje

RepozytoriumWynikLicencja
Ta strona · stefanocaronia/claude-project100MIT
CodaColaLight/nightmill100Apache-2.0
userKael/rastro100MIT
elalfner/relevo100MIT
abatyuk/okf100MIT
duronext/jig100MIT
sh5623/e2e-rail100MIT
Calvin-LLC/skills100MIT
arxdsilva/ai-loops100MIT

Migawka bazy z 13.11.2026 · wersja paczki d7302f68a85a (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 90tidy
    Porządkuje projekt: dokumenty zgodne z architekturą wtyczki, indeks, strukturę folderów oraz backlog z decyzjami, priorytetami i duplikatami.
  • 90specsmith-init
    Tworzy w projekcie strukturę katalogu specs z szablonami specyfikacji, planu i zadań z zainstalowanej wtyczki Specsmith.
  • 100workflow-init
    Inicjalizuje nowy lub istniejący projekt jako przepływ AI-Native: tablicę Backlog.md, kontrakty AGENTS.md i skille pomocnicze.
  • 100project
    Prowadzi plan, backlog, decyzje i specyfikacje projektu w plikach markdown za pomocą deterministycznych poleceń.
  • 100cc-spex-init
    Instaluje lub odświeża przepływy Spex oparte na specyfikacji w bieżącym projekcie ze źródła dołączonego do wtyczki cc-spex oraz konfiguruje rozszerzenia i ustawienia bezpieczeństwa.
  • 90Backlog Management
    Prowadzi backlog projektu w pliku BACKLOG.md: dodaje pozycje, aktualizuje je, sprawdza i ustala priorytety.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.