straymark-newlisted

# StrayMark New Skill Create StrayMark documentation based on recent changes. ## Instructions When invoked, follow these steps: ### 1. Check for Parameters If the user specified a document type (e.g., `/straymark-new ailog`), skip to step 4 using that type. Valid types: `ailog`, `aidec`, `adr`, `eth`, `req`, `tes`, `inc`, `tde`, `sec`, `mcard`, `sbom`, `dpia` > **Charter is not a `straymark new` type.** Charters are bounded units of work (filename `NN-slug.md`, sequential prefix) and have their own command. If the user asks for a Charter (`/straymark-new charter`, *"create a Charter"*, *"declare a Charter"*), redirect to `/straymark-charter-new`. ### 2. Analyze Context Gather information about recent changes: ```bash # Get current date date +%Y-%m-%d # Get modified files (staged and unstaged) git status --porcelain # Summarize the CURRENT work (staged + unstaged + untracked) — label each block, # do NOT use `HEAD~1`, which describes the previous commit, not current work. git diff --cached --stat # staged changes git diff --stat # unstaged changes git status --porcelain # includes untracked files # Only if the user explicitly asks to document an already-committed range: # git diff --stat <range> # e.g. origin/main..HEAD # Count lines changed in current work git diff --cached --numstat ; git diff --numstat # Check code complexity (primary method for AILOG trigger) straymark analyze --output json 2>/dev/null # If CLI unavailabl