init-context
SolidSet 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.
Install
Quality Score: 84/100
Skill Content
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
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.
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.
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.