sysml-modeling-session-checklist

name	sysml-modeling-session-checklist
description	Short preflight before substantive SysML v2 modeling: MemNet warm, project context, plan-with-user, validate, outputs sync. Triggers: start modeling session, new chat, new project folder, batch .sysml edits, preflight checklist before sysml, memnet sysml.
metadata	{"pattern":"pipeline","domain":"sysml-v2","version":"1.9","product":"memnet-llm==0.19.3","pairs_with":["sysml-memnet-documentation","sysml-memnet-cache","sysml-modeling-workflow","project-planner","mcp-sysml-v2","mcp-memnet","sysml-view-doc-sync","memnet-nested-sessions","memnet-multitask"]}
token_guardrails	- **Thin:** run the checklist mentally or as bullets; do not paste long repo trees. - **MemNet first:** steps 0-1 before any `.sysml` Read (see sysml-memnet-read-policy.md). Nested: memnet-nested-sessions (one interior per generate). - **Model SSOT:** plan edits to `.sysml` first; commissioning / power-cycle / setup flows -> behaviour + requirements (refine/derive), then outputs diagrams. - **After edits:** mcp-sysml-v2 validate; step 6 MemNet delta when structure changed. - Use project-planner in a separate turn for full requirements interview + roadmap.

system_instruction: | Prefer plain Markdown tables or domain wire; do not use TOON/TRON. JSON only at tool boundaries.

SysML modeling session checklist

Alias in SKILL-GRAPH: smsc (routing / edges -- not a second skill).

Not a replacement for project-planner. Use when you are about to edit .sysml.

Output contract

After the checklist, state briefly:

• project -- model root + short name (from repo AGENTS.md if present)
• campaign -- TSK_model_<short> (cue goal=; leftover anchor= is leftover)
• session -- catalog id; interior session= if the catalog pin carries one
• warm -- warm_hit | warm_miss (if miss -> initial snap; catalog vs Path-B per snap.md)
• read plan -- symbols from warm only; no full deploy read unless warm_miss
• pipe -- TSK_turn_* id if serve up; else serve_down
• next -- target file from @SYM if known, else which models/*.sysml
• plan status -- agreed roadmap / skipped + one-line why

Pipeline

0. MemNet (steps 1-2) -- TCP/HTTP / unsure: serve_status. Skip probe only under single-agent in-process. Multitask MUST NOT in-process. Cue catalog pin_map(kind='TSK', locators=['goal=TSK_model_<short>'], depth=2, max_rows=50); if the cut has session=, goldfish that interior next generate (memnet-nested-sessions). leftover anchor= / id= named leftover. Catalog id from MEMNET_SESSION or the header line of AGENT-CONTEXT.md. On warm_miss -> initial snap. If serve down -> note stale graph; skip warm.

1. Project context -- Confirm model root (sysml-v2-models/projects/<name>/ or repo AGENTS.md path such as sysml-models/), config.yaml, files to touch. Read policy: sysml-memnet-read-policy.md -- no full deploy/AGENT-CONTEXT when warm hit. Submodules: edit in canonical repo if applicable (open repo root AGENTS.md).

2. Plan-with-user -- Non-trivial / ambiguous work without agreed plan: stop and plan--or project-planner for documented roadmap. If user skipped planning, state in one line.

3. Cross-file scope -- For rename, impact, or search, use Grep / Read on live .sysml files, then Cursor user-sysml-v2 MCP (parse / validate / getSymbols / getDefinition / getReferences) on the file or code just loaded. Do not use abandoned sysmledgraph or treat an MCP workspace URI index as model SSOT.

4. Modeling sequence -- requirements (prefer refine / derive under parents) -> deploy / connections -> behaviour (incl. commissioning / power-cycle when in scope) -> satisfy / allocate -> outputs + ( 6-step turn). Model first; do not author architecture only in Markdown.

Hub: AGENTS.md * MemNet: sysml-memnet-snap.md * Read policy: sysml-memnet-read-policy.md