init-context

Solid

Set a project up with the surfaces manifest-dev works from — a glossary, ADR conventions, and the context-file wiring that makes every session use them — seeding them from the project's own history where there is any. Use when a repository has no CONTEXT.md or decision records, when adopting manifest-dev in an existing codebase, when starting a new project, or when the user asks to initialize project context, bootstrap ADRs, or reconstruct decisions from history.

AI & Automation 73 stars 10 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
62
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

Install the project surfaces a repository needs so that every future session — and every teammate, with or without manifest-dev — works from the same vocabulary and the same decision record. Two things get installed, and only the first is essential: - **The wiring** — an ADR conventions file the project owns, a glossary, and a project-context-file section that makes sessions read and maintain both. This runs on every project, including one with no history at all. - **A seed** — vocabulary and decision records reconstructed from the project's own history. This runs wherever there is history to read, and it is enrichment on top of the wiring, never a substitute for it. Aim for a good starting point rather than a complete record. Most of a project's past reasoning is genuinely unrecoverable; a seed that is honest about what it could not recover is worth far more than one that reads complete and isn't. ## Flags `--no-mine` skips the seed and installs the wiring alone. Mining otherwise runs wherever there is history — a project with no commits, no docs and no code simply has nothing to seed from, which needs no flag to express. Interpret only top-level options as flags; quoted or code-formatted mentions of them are topic text. ## What already exists governs Read before writing, and never overwrite a surface the project already maintains: - **`docs/adr/CONVENTIONS.md` exists** → the project has its own ADR convention. It governs. Do not replace it; follow it for anything w...

Details

Author
doodledood
Repository
doodledood/manifest-dev
Created
7 months ago
Last Updated
3 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

context-creation

The brownfield back-fill. Routed to by /create-context, and by startup when .codearbiter/CONTEXT.md lacks the <!--INITIALIZED--> body marker but source code exists. Six gated phases — pre-flight, scout dispatch, synthesis, gap interview, write, lock. Reads the existing codebase through parallel scouts, drafts every surviving project-state doc, resolves gaps with the user, and locks the project as initialized.

144 Updated yesterday
arbiterForge
AI & Automation Listed

project-context-ledger

Maintain autonomous Markdown-first, per-project continuity and coordinate live work across devices and agent sessions with ContextJoin MCP or CLI tools. Use on EVERY turn of material work in a project containing `.project-context` — start of turn, immediately when a conflict-relevant change or confirmed decision happens mid-turn, and compulsorily at end of turn — plus when onboarding an existing project into the ledger, linking the same project across devices, or moving work between Codex, Claude, Cursor, or another harness. Do not use for casual questions, routine command output, raw transcripts, secrets, or unverified work.

0 Updated 4 weeks ago
rohitmenonhart-xhunter
AI & Automation Listed

domain-model

Build and sharpen a project's domain model — the `CONTEXT.md` glossary of terms and the `docs/adr/` record of architectural decisions. Use when the user wants to pin down terminology or a ubiquitous language, asks "what should we call this", says the glossary is wrong or missing a term, wants to record or revisit an architectural decision ("write an ADR", "record why we did this"), or when another skill needs the model changed rather than merely read. Also use mid-design, the moment a term or a hard-to-reverse decision crystallises. NOT for reading `CONTEXT.md` for vocabulary — that is a habit every skill has, not a reason to load this one.

0 Updated 1 months ago
ltatarev