straymark-charter-newlisted

# StrayMark Charter Scaffold Skill Declare a Charter at the start of a bounded, auditable unit of work — *not* every change. Charters wrap multi-session work that warrants a stable scope contract you can drift-check at close. They are conceptually distinct from the 12+4 governance document types (AILOG, ADR, AIDEC, …): Charters live at `.straymark/charters/NN-slug.md` and use a sequential prefix instead of a date prefix. > See `STRAYMARK.md §15` and `.straymark/00-governance/SPECKIT-CHARTER-BRIDGE.md` for the lifecycle and the SpecKit ↔ Charter bridge. ## When to use this skill Trigger on any of: - Multi-session implementation block (>1 day, >5 tasks across phases). - Work that warrants external audit at completion. - A SpecKit feature has reached `tasks.md` and the operator wants a stable scope contract before `/speckit-implement`. - The user asks to "declare", "open", or "start" a Charter. If the work is a single-session change → use `/straymark-ailog` instead. ## Instructions ### 1. Gather context ```bash # Sequential number of the Charter being created straymark charter list 2>/dev/null | tail -5 || true # Surrounding spec / AILOG context — Charters frequently originate from one ls specs/*/spec.md 2>/dev/null | head -5 ls .straymark/07-ai-audit/agent-logs/AILOG-*.md 2>/dev/null | tail -5 ``` ### 2. Confirm with user ``` ╔══════════════════════════════════════════════════════════════════╗ ║ StrayMark Charter — declare a bounded unit of work ║ ╠══