mishkan-initlisted
Install: claude install-skill Y4NN777/mishkan-cc-harness
# mishkan-init
Initialise a new project under MISHKAN. Run once per project. Surface a `/plan`
to Y4NN before the first doc is written — the plan is the scope contract for init.
## Preconditions
- Y4NN has converged on intent in exploration mode (Nehemiah + Bezalel).
- Working directory is the project root.
## Sequence (each phase feeds the next — do not skip, do not reorder)
1. **Nehemiah** — from the intent conversation, write `docs/PRD.md` (product
requirements: problem, users, use cases).
2. **Nathan** (Yasad) — `docs/SRS.md` (software requirements from the PRD).
3. **Zadok** (Yasad) — `docs/CONTRACT.md` (invariants + guarantees). `/plan` first.
4. **Bezalel + Nathan** — `docs/ARCHITECTURE.md`. `/plan` first.
5. **Benaiah** (Mishmar) — `docs/THREAT_MODEL.md` via STRIDE. `/plan` first.
6. **Meshullam** (Migdal) — `docs/diagrams/C4/` (Context, Container, Component).
`/plan` first.
7. **Jehoshaphat** (Sefer) — scaffold `docs/README.md`, `docs/adr/`,
`docs/runbooks/` (stub runbooks per team). `/plan` first.
8. **Automated** — knowledge setup (decisions D-007 + D-012 + D-015). Init composes
the two control verbs (the human-facing equivalents of the scripts):
- **Knowledge stack (shared, idempotent):** ensure the shared infra is up —
`mishkan knowledge-stack up` (memory :7777 + curated :7730 + ollama/pg;
wraps the compose + `ensure-curated-box.sh`; no-op if already running; ~5min
cold start on first run; preflights `.env` and guides to `mishka