meridian-trello-test

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

Closes a Meridian user story after implementation — fills Record, acceptance, status and board. Use when marking US done, completing US-XXXX, or after implementing a user story.

Creates a Meridian epic file in docs/epics after architecture is approved. Use when defining a new product capability block before user stories.

Creates a Meridian sprint file in docs/sprints linked to a version. Use when planning execution slices within a release.

Creates a valid Meridian user story after epics and versions are approved. Use when adding work to docs/us and keeping acceptance criteria concrete.

Creates a Meridian release file in docs/versions. Use when defining a new product version before user stories.

Generates docs/kanban/board.json from Meridian user story frontmatter. Use after creating or changing user stories.

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

Initializes a project with Meridian docs, decision log, board JSON and minimum governance. Use when starting a new project or repairing a missing Meridian structure. Also handles existing codebases migrating into Meridian.

Automatic Meridian agent selection and task routing. Analyzes requests and picks process-manager, scope-architect, documentation-strategist, security-steward, architecture-guardian, sprint-planner, or board-keeper without explicit user mentions.

Refines a Meridian user story for implementation — deepens Approach, architecture refs and tests. Use between /create-us and coding, or /refine-us US-XXXX.

Audits a Meridian user story against writing quality, section contracts and refine checklist — report only, no ready flag. Use for /review-us US-XXXX, quality audit, or before refine/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.

Prepends relevant project decisions to docs/decisions/YYYY-MM-DD.json (newest first in entries). Use when scope, stack, security, architecture, versions or acceptance criteria change.