Menu
Process a source from raw/ into the wiki — write a summary page, update affected entity and concept pages, and record the ingest in the index and log
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | wiki-ingest |
| description | Process a source from raw/ into the wiki — write a summary page, update affected entity and concept pages, and record the ingest in the index and log |
| category | researching |
| model | claude-sonnet-4-6 |
| argument-hint | <raw-file-path> |
| disable-model-invocation | false |
| user-invocable | true |
Integrate a raw source document into the persistent wiki. The source is read once, distilled, and woven into the existing page network — summary page, entity pages, concept pages, index, and log — so the wiki compounds rather than the source sitting unprocessed.
Source to ingest: $ARGUMENTS
$ARGUMENTS to a file under raw/. If the path is ambiguous or missing, use Bash with find raw/ -iname "*<pattern>*" to locate candidates and confirm with the user.Read — never summarize from a partial read. For long files, read in sequential chunks until complete.Before writing anything, present a brief summary to the user:
wiki/index.md to determine this)Keep this short — it is a checkpoint, not a report. Incorporate any emphasis or corrections the user offers.
Bash with ls wiki/knowledge/sources/ to check whether a summary page for this source already exists.wiki/knowledge/sources/ with a kebab-case filename derived from the source title (e.g. raw/Some Article.md → wiki/knowledge/sources/some-article.md). Create the directory if it does not exist.---
id: some-article
title: Some Article
updated: YYYY-MM-DD
sources:
- ../../raw/some-article.md
tags: []
---
rel::[[Entity Name]] (e.g. derived_from::, uses::, relates_to::).For each person, organisation, tool, or component mentioned significantly in the source:
people, organisations, tools, or components (components = this project's own modules/skills/scripts).Bash with ls wiki/knowledge/entities/<sub-type>/ to check for an existing page.> **Contradiction:** callout if the new claim conflicts.wiki/knowledge/entities/<sub-type>/<entity-slug>.md with frontmatter:
---
id: entity-slug
title: Entity Name
aliases: [Alternative Name]
updated: YYYY-MM-DD
sources:
- ../../../raw/some-article.md
tags: []
---
For each pattern, idea, convention, or recurring theme the source illuminates:
Bash with ls wiki/knowledge/concepts/ to check for an existing page.wiki/knowledge/concepts/<concept-slug>.md with frontmatter (id, title, updated, sources, tags) and a focused distillation.In wiki/index.md:
- [Source Title](knowledge/sources/source-slug.md) — one-line summary (knowledge pages are listed in the home index; work items are not).Use a single Edit call per section.
Append to wiki/log.md:
## [YYYY-MM-DD] ingest | <source title>
Ingested from raw/<filename>. Key claims: [2–3 bullet summary]. [N] entity pages touched, [M] concept pages touched.
raw/ is immutable — never create, modify, move, or delete files under raw/.wiki/knowledge/; never file a source summary or concept page under wiki/work/.> **Contradiction:** callout citing both the new source and the conflicting page; never silently overwrite.wiki/knowledge/sources/ reaches raw/ as ../../raw/, reaches concepts as ../concepts/, reaches entities as ../entities/.id: and aliases: frontmatter to every page you create or touch.derived_from::, uses::, relates_to::, contradicts::) wherever a link has a meaning — see wiki/conventions.md for the full vocabulary.Update the ai-sdd framework binary + skills to the latest release — an apply-on-confirm wrapper that runs `ai-sdd update --check`, surfaces the current-to-latest version transition, and (only on explicit confirmation) runs `ai-sdd update` and lands a standalone reseed commit. Agent-agnostic (claude-code or codex). Use when a teammate wants to update / upgrade ai-sdd, sees the update-available notice, or invokes `/ai-sdd-update`.
Stand up (or refresh) an ai-sdd factory for a repository so any coding agent — claude-code, codex, … — can drive it. Discovers the repo's conventions, scaffolds the .ai-sdd/ home, authors worker skills + schemas, compiles the deterministic gates, and wires provider-neutral skill surfacing (AGENTS.md + per-agent symlinks). Use when onboarding a repo to ai-sdd or re-bootstrapping after the codebase/conventions drift.
Drive a software-factory run by dispatching a sub-agent per worker — the deterministic `ai-sdd` engine plans (next), a fresh sub-agent does each worker's work via its skill, the engine gates and advances (submit), and each completed slice is committed. Agent-agnostic (claude-code or codex). Use when asked to run, drive, continue, or advance a factory run / pipeline / orchestration, or when the user mentions `ai-sdd next` / `ai-sdd submit`.
Print the diagram-driven ai-sdd workflow cheatsheet — the canonical command sequence (bootstrap → plan → run, validate/next/submit/status) that travels with the binary. Use when a user forgets which command comes next, asks "how do I drive a run / what's the workflow", or needs the command reference without leaving the repo.
Turn a complete PROGRAM brief into a runnable master plan — a decision-closed program requirements doc and a master orchestration graph whose nodes are whole sub-features (kind:pipeline) sequenced by milestone validation gates with owners. The program tier above ai-sdd-plan. Requires a real program brief (refuses a one-liner) and human approval of the program requirements draft before emitting the graph. Use when planning a multi-feature, multi-person project in a bootstrapped repo (run ai-sdd-bootstrap first); each sub-feature is then planned with ai-sdd-plan. Re-run on an existing program to amend it in place (create-vs-amend is auto-detected from disk): append sub-features/milestones and rewire pending nodes; a started node (completed or in-flight) is immutable and corrected forward with a downstream `<node>-revert` node.
Turn a complete feature brief into a runnable plan for a bootstrapped repo — a decision-closed requirements doc and an orchestration graph (slices + depends_on) the engine executes. Requires a real brief (refuses a bare one-liner — asks for one) and human approval of the requirements draft before generating slices. The planning layer between an idea and ai-sdd-run. Use when starting a new feature in a repo that already has a .ai-sdd/ (run ai-sdd-bootstrap first). Re-run on an existing feature to amend it in place (create-vs-amend is auto-detected from disk): append slices and rewire pending ones; a started slice (completed or in-flight) is immutable and corrected forward with a downstream `<slice>-revert` slice.