Imported from giodra96/project-wiki (
SKILL.md). Install upstream withnpx skills add giodra96/project-wiki. Copyright stays with the author.
Project Wiki
Create and maintain an agent-readable project knowledge base in .project-wiki/ without loading the entire wiki into context. The skill is IDE-neutral.
Current project wiki schema version: 1.5.1 (canonical value: ./schema/project-wiki.yml).
Route The Task
Select one primary mode for an explicit wiki request and load only its workflow:
| Trigger | Load |
|---|---|
init - Initialize an empty project wiki |
Init Workflow |
scan - Scan an existing repository |
Scan Existing Project Workflow |
update - Process notes, requirements, meetings, or durable analysis |
Update Workflow |
update - Ingest PDF, DOCX, text, or Markdown sources |
Document Intake Workflow, then Document Ingestion |
sync - Reconcile code changed outside the current agent task |
Sync Workflow |
maintain - Validate, migrate, repair, or semantically lint a wiki |
Maintain Workflow |
Before implementing, modifying, debugging, refactoring, testing, documenting, or planning code when .project-wiki/INDEX.md exists |
Automatic Context Preflight |
| After agent-made source changes | Automatic Post-Implementation Wiki Update |
Load Document Templates only when creating an artifact. Load Wiki Structure or the Schema Contract only when exact structure or contract values are needed. Use Common Policies when finalizing wiki edits.
Operating Contract
- Read
.project-wiki/INDEX.mdfirst when it exists, follow its routes, and open only the smallest relevant set of files. UseREGISTRY.ymlonly when indexes do not resolve the task. - Before code planning or changes, run the automatic context preflight. After agent-made source changes, run the automatic post-implementation workflow; reserve
syncfor external or manual changes. - Follow the selected workflow completely. Prefer the supplied deterministic scripts over reproducing structural, validation, duplicate, extraction, or ledger logic in model reasoning.
- After every meaningful wiki edit, reconcile affected indexes,
REGISTRY.yml,STATUS.md, traceability, andlogs/wiki-log-YYYY-MM.mdas required by the selected workflow.
Invariants
- Keep stable IDs, required frontmatter, relative wiki links, and the complete canonical structure. Preserve history and original requirements rather than silently replacing them.
- Put explicit business or product intent in
requirements/; put implemented or observed behavior intechnical/. Record unconfirmed product intent inferred from code as an open question. - Reconcile existing open questions before creating new ones. Represent significant risks, contradictions, blocking gaps, or critical assumptions as alerts and resolve rather than delete them.
- Mark uncertain scan findings as
confidence: inferredorconfidence: unknown. - Keep indexes as compact routing maps. File durable non-canonical synthesis only when significant and link it to evidence or related records.
- Treat document intake as immutable provenance. Never load external PDF or DOCX files directly into model context; use the ingestion and review-progress scripts and complete every chunk disposition.
- Write all wiki content and generated instruction blocks in English. Reply in the user's language unless requested otherwise.