ワンクリックで
comms
Manage dev_communication inboxes, messages, and issue lifecycle across backend/frontend teams.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Manage dev_communication inboxes, messages, and issue lifecycle across backend/frontend teams.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Manage architecture decisions, gaps, and suggestions in dev_communication/shared/architecture.
Load relevant ADRs, patterns, and memory before implementation work.
Manage the project memory vault for notes, entities, patterns, and session summaries.
Periodically review patterns, promote mature patterns to ADRs, and identify coverage gaps.
Capture implementation learnings, pattern candidates, and architecture gaps after coding work.
SOC 職業分類に基づく
| name | comms |
| description | Manage dev_communication inboxes, messages, and issue lifecycle across backend/frontend teams. |
Use this skill when the user asks to check team comms, send a cross-team message, create or move issues, or archive completed message threads.
Before running actions, resolve active team defaults from:
.codex-workflow/config/active-team.json (project-local), elseconfig/active-team.json.Use team_profile.default_paths and issue_prefix from that file as defaults.
If no active team config exists, ask the user which team context to use.
Project policy:
team-only.dev_communication/backend/inbox and backend issue folders unless the user explicitly asks for frontend/cross-team status.check, send, issue, status, move, or archivebackend or frontend)Backend-Dev, Backend-QA, Frontend-Dev, Frontend-QAteam_profile.default_paths.inbox)team_profile.default_paths.issues_queue)team_profile.default_paths.issues_active)dev_communication/templates/message-request.md (or response template when replying).dev_communication/backend/inbox/ ordev_communication/frontend/inbox/YYYY-MM-DD_{subject_slug}.md.dev_communication/templates/issue-template.md.dev_communication/backend/issues/queue/ for API issuesdev_communication/frontend/issues/queue/ for UI issuesStatus: QUEUE.{TEAM}-ISS-{NNN}_{title_slug}.md.Guardrail:
dev_communication/backend/status.mddev_communication/frontend/status.mdqueue/, active/, or completed/.queue/ -> Status: QUEUEactive/ -> Status: ACTIVEcompleted/ -> Status: COMPLETEqueue/ or active/.dev_communication/archive/YYYY-MM-DD_{thread_subject}/check, provide short, scan-friendly status by team.send or issue, include exact filenames for traceability.completed/.