stackchan-contract-changeContract-change workflow for codex-stackchan-bridge. Use when changing ROS 2 messages, services, actions, topic names, QoS, stackchanctl command behavior, CommandMeta, Result, device_id handling, audio/camera/NFC/IMU contracts, or the bridge facade between CLI, ROS, and firmware.
stackchan-dev-workflowRepository development workflow for codex-stackchan-bridge. Use when Codex is asked to plan, implement, review, or route work in this repository, especially changes spanning docs, firmware, ROS 2 packages, stackchanctl, repo-local Codex agents, or repo-local Codex skills.
stackchan-quality-gatesValidation workflow for codex-stackchan-bridge. Use before committing, pushing, or marking work complete, and when choosing tests or CI gates for changes to docs, stackchanctl, ROS 2 interfaces, the bridge, firmware, repo-local Codex agents, or repo-local Codex skills.
stackchan-setup-workflowUse when setting up codex-stackchan-bridge for local development, ROS 2 container use, mock stackchanctl checks, local TTS, firmware upload, or K151 hardware bring-up. Do not use for feature implementation, contract changes, motion tuning, or review-only requests.
codex-stackchanUse when Codex should express work state through a local M5StackChan or interpret StackChan-origin observations such as button, IMU, NFC, IR, or transcript_ready. Do not use for lower-level hardware-control or telemetry workflows.