Purpose
Initialize or refresh project-local development context for the project development skill collection.
This skill creates a usable .llm-wiki skeleton, discovers modules conservatively, and migrates legacy docs/ai-coding as read-only source context. It does not modify production code.
Required Shared References
Read these role-level references:
../references/north-star.md../references/lifecycle-mvp.md../references/tool-bridge.md../references/llm-wiki-mvp.md../references/legacy-ai-coding-migration.md
If installed in a flattened environment, locate equivalent references/ paths near the skill root.
Workflow
- Resolve
project_root. - Decide mode:
init: no.llm-wikiexists or user asks to adopt a repositoryrefresh:.llm-wikiexists and user asks to rescan, after docs were copied in, or after modules changed
- Inspect project markers:
.git- build files
docs/- existing
.llm-wiki/ - legacy
docs/ai-coding/ .codegraph/
- Create missing
.llm-wikidirectories and starter files. - Ensure
.llm-wiki/working-context/exists for future complex or cross-module work. - Create or update
.llm-wiki/modules/index.md. - Detect modules conservatively from build files and top-level service directories.
- Mark modules:
active: explicitly selected by user or current taskreference-only: shared libraries, API contracts, DTOs, SDKs, or direct dependenciesdiscovered: found but not in current workunknown: found but unclear; ask or leave as gap
- If
.codegraph/or generated graph files exist, record them as read-only supporting context in.llm-wiki/index.mdor.llm-wiki/modules/index.md; do not generate codegraph during MVP. - Summarize legacy
docs/ai-codinginto.llm-wikiwithout deleting or rewriting legacy files. - On refresh, preserve existing statuses unless evidence or user instruction changes them.
- Write a
.llm-wiki/log.mdentry. - Report created files, refreshed files, discovered modules, migrated context, codegraph context, and open questions.
Required Outputs
Report:
Project root:
Mode:
Created:
Updated:
Preserved:
Modules:
Codegraph context:
Legacy migration:
Open questions:
Next action:
Module Index Minimum
Use this shape:
| Module | Path | Type | Context | Status | Notes |
|---|---|---|---|---|---|
Allowed Status values: active, reference-only, discovered, unknown.
Safety
- Do not modify production code.
- Do not delete, move, or rewrite legacy
docs/ai-coding. - Do not deep-read every module in a monorepo.
- Do not treat generated AI docs as source of truth.
- Do not overwrite existing
.llm-wikisummaries without preserving useful user or agent decisions.