Govern changes to the JM Labs Claude Desktop workspace ecosystem. Use whenever a task touches bootstrap, refresh, sync, export, local overlays, repo-local skills or agents, `workspaces/tasks`, generated `tasklog.md`, task intake flows, or when you need to decide whether an artifact belongs in the core, the workspace instance, or ignored local state.

Govern the JM Labs persistent task filesystem and intake workflow. Use whenever the task mentions `workspaces/tasks`, `tasklog.md`, `rag-memory-*`, task intake, task close, task resume, ambiguous inputs, session-state orchestration, or the rule that every new work input must be recoverable from disk.

Curate durable `rag-memory-*` files for JM Labs tasks. Use whenever an input, attachment, ephemeral note, conversation snippet, or admin repair step must be preserved so the workspace can recover context even if the original artifact disappears.

Audit parity between the JM Labs core contracts and the live Claude Desktop or Codex environment. Use whenever MCPs, plugins, connectors, local overlays, NotebookLM, Tessl, admin dashboard health, task orchestration scripts, or readiness claims are involved, especially before declaring the workspace healthy.

Operate the JM Labs local admin dashboard and its repair surface. Use whenever the task mentions `dashboard.html`, `admin-app`, `dashboard-doctor.sh`, `dashboard-repair.sh`, the local mini app server, task admin views, filesystem inspection, or safe MCP/config visibility.

Report a bug against an existing feature — creates a structured bugs.md record, generates fix tasks in tasks.md, and optionally imports from or creates GitHub issues. Use when fixing a bug, reporting a defect, importing a GitHub issue into the workflow, or triaging an error without running the full specification process.

Generate a technical design document from a feature spec — selects frameworks, defines data models, produces API contracts, and creates a dependency-ordered implementation strategy. Use when planning how to build a feature, writing a technical design doc, choosing libraries, defining database schemas, or setting up Tessl tiles for runtime library knowledge.

Create or update a CONSTITUTION.md that defines project governance — establishes coding standards, quality gates, TDD policy, review requirements, and non-negotiable development principles with versioned amendment tracking. Use when defining project rules, setting up coding standards, establishing quality gates, configuring TDD requirements, or creating non-negotiable development principles.

SDD project initialization, status, feature selection, and help. Enhanced fork of iikit-core with workspace sessions, heartbeat init, ALM deployment, and SDD branding.

SDD Utility — Resolve ambiguities in any artifact at any phase. Enhanced: auto-detect artifact, structured questions per ambiguity taxonomy, RAG capture.

SDD Bug report + fix tasks. Enhanced: Quick Flow triage, GitHub issue inbound (#number), scope guard against AP-06 (consecutive quick flows).

SDD Phase 8 — Export tasks to GitHub Issues with labels and dependencies. [GATE G3] Enhanced: mandatory gate, issue-map tracking, cross-check verification.

SDD Phase 7 — Iterative TDD implementation with BDD verification chain. [GATE G2] Enhanced: mandatory gate, step coverage verification, assertion integrity, feature immutability.

SDD Phase 6 — Cross-artifact consistency validation, traceability FR→TS→Tasks. Enhanced: knowledge graph rebuild, orphan detection, health scoring.

SDD Phase 5 — Dependency-ordered task breakdown with parallel markers and story labels.

SDD Phase 4 — Gherkin BDD test specs with cryptographic assertion hashing. Enhanced: SHA-256 hash generation, traceability tag validation, assertion integrity.

SDD Phase 3 — BDD Analysis quality checklists. [GATE G1] Enhanced: mandatory gate enforcement, FR→plan alignment check.

SDD Phase 2 — Technical Specs: architecture, data model, API contracts, technology decisions. Enhanced: Tessl tile discovery, context validation, schema enforcement.

SDD Phase 1 — User Specs from natural language. FR-NNN, SC-NNN, acceptance scenarios. Enhanced: bug-fix intent detection, semantic diff on re-run, workspace RAG capture.

SDD Phase 0 — Define governance principles, coding standards, quality gates, and TDD policy. Enhanced: validates context.json, updates pipeline state, suggests workspace creation.