meridian

Creates a Meridian user story in SQLite after epics and versions exist. Use when adding work to the backlog with concrete acceptance criteria.

Refines a Meridian user story in SQLite for implementation — deepens Approach, architecture refs and tests. Use between /create-us and coding.

Gates implementation of a Meridian user story — verifies ready true, Plan, deps and architecture refs before product code. Use with /implement-us US-XXXX.

Maintainer procedure to add or change Meridian kit artifacts — skill, agent, workflow, routing, and every registry surface. Use when extending the harness, creating /investigate, or onboarding a new slash command.

Closes a Meridian sprint in SQLite after sprint review — fills Retrospective, sets status complete, logs decisions. Use with /complete-sprint vX-SY.

Closes a Meridian user story in SQLite after implementation — fills Record, acceptance, status. Use when marking US done or after /implement-us.

Creates a Meridian epic in SQLite after architecture is approved. Use when defining a new product capability before user stories.

Creates a Meridian sprint row in SQLite linked to a version. Use when planning execution slices within a release.

Creates a Meridian release row in SQLite. Use when defining a new product version before user stories.

Read-only codebase investigation — trace flows, map dependencies, explain behavior with evidence. Use with /investigate before refine-us, spike US, or architecture updates.

Automatic Meridian agent selection and task routing. Analyzes requests and picks v11 agents (scrum-master, product-owner, technical-writer, security-champion, technical-architect, design-system-owner, quality-owner, sprint-planner, backlog-refiner, developer, code-investigator) without explicit user mentions.

Initializes a project with Meridian phase docs, SQLite delivery profile, and minimum governance. Use when starting a new project or repairing a missing Meridian structure. Also handles existing codebases migrating into Meridian.

Audits a Meridian user story in SQLite against writing quality and section contracts — report only. Use for /review-us US-XXXX before refine or implement.

Reviews Meridian security posture, including secrets, threat model, AI-agent safety, OWASP, dependencies and Git hygiene. Use for 02_security.md or security hardening.

Maintains optional docs/12_marketing_seo.md and seo-pass workflow for public indexable web products. Use with /seo-pass when scope includes marketing sites or public app routes.

Audits Meridian phase docs against each other and the codebase; reports gaps and optionally applies draft improvements. Use with /audit-docs for brownfield or Meridian-started projects.

Maintains docs/10_test_strategy.md and stack-aware test bootstrap — Vitest, Jest, Playwright, pytest. Use for /test-pass, /test-review, test pyramid, coverage, or US tests field alignment.

Maintains docs/09_design_system.md and stack-aware UI bootstrap — shadcn, MUI, Chakra, Ant Design, Streamlit, NiceGUI, Django HTMX, Go templ, Leptos; composed App* templates over read-only primitives. Use for /design-pass, /design-showcase, /design-review, 09_design_system, tokens, showcase catalog, or UI acceptance criteria.

Prepends a project decision to SQLite (.meridian/meridian.db decisions table). Use when scope, stack, security, architecture, versions or acceptance criteria change.

Runs Meridian product discovery — interviews, codebase context, and docs/discovery/product-brief.md before scope is locked. Use with /discover before or alongside init.

Documents an existing codebase in Meridian phase docs and as-is inventory without creating epics or user stories. Use with /document-project for brownfield adoption or refreshing docs from code.