القائمة
Send agent messages, acknowledge inbox items, and persist shared context pins. Use when working in Claude Code and the user needs tx commands from this area.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Turn a design spec into an explicit tx task graph with `tx decompose`, then refine the graph using normal tx task and dependency primitives.
Generate a detailed design document via `tx doc add design`. Covers architecture, interfaces, data model, invariants, failure modes, verification, and testing strategy. References plan via file path instead of embedding. Plan lives in ~/.claude/plans/<name>.md. Reads companion PRD automatically to map EARS requirements to invariants. Output lands in specs/design/<name>.md.
Generate a system overview spec via `tx doc add overview`. Produces an architectural overview covering problem, scope, components, data flows, and non-goals. References plan via file path instead of embedding. Plan lives in ~/.claude/plans/<name>.md. Output lands in specs/<name>.md with tx-managed frontmatter.
Generate a detailed Product Requirements Document via `tx doc add prd`. Uses EARS requirement syntax with traceable IDs, acceptance criteria, and non-functional requirements. References plan via file path instead of embedding. Plan lives in ~/.claude/plans/<name>.md. Designed to be created alongside a companion `/design-doc`. Output lands in specs/prd/<name>.md.
Internal closed-loop skill: drive CLI/API/MCP to 100% shape parity (same service methods) AND behaviour parity (same response shapes). Uses ESLint rules tx/require-surface-parity + tx/interface-parity. NOT shipped to tx users.
Generate a system-level design document via `tx doc add design`. Covers cross-cutting architecture, service boundaries, data flows, scalability, and deployment topology. References plan via file path instead of embedding. Plan lives in ~/.claude/plans/<name>.md. Use for system-wide or multi-domain designs rather than feature-scoped subsystem docs.
| name | tx-messaging-pins |
| description | Send agent messages, acknowledge inbox items, and persist shared context pins. Use when working in Claude Code and the user needs tx commands from this area. |
| metadata | {"short-description":"Send agent messages, acknowledge inbox items, and persist shared context pins."} |
Use when coordinating agents through channels or syncing pinned context into agent files.
tx msg inbox <channel>tx msg send <channel> "message"tx pin synctx ack: Acknowledge a messagetx ack all: Acknowledge all pending messages on a channeltx inbox: Read messages from a channeltx msg: Agent messagingtx msg ack: Acknowledge a messagetx msg gc: Garbage collect old messagestx msg inbox: Read messages from a channeltx msg pending: Count pending messagestx msg send: Send a message to a channeltx outbox gc: Garbage collect old messagestx outbox pending: Count pending messagestx pin: Context pins for agent memory injectiontx pin get: Show a pin's contenttx pin list: List all context pinstx pin remove: Remove a context pintx pin rm: Remove a context pintx pin set: Create or update a context pintx pin sync: Re-sync all pins to target filestx pin targets: Show or set target filestx send: Send a message to a channelRead references/commands.md for the full generated CLI help text for this skill's commands.
When working in Claude Code, prefer rg -n <pattern> <path> and rg --files <path> over broad grep -r or fragile find pipelines.
If a shell/search command fails because of malformed flags, truncated paths, or broken quotes:
rg command with an explicit directorynode_modul or unterminated quotesgrep -r with rg -n unless rg is unavailablefind probes with rg --files when you are really locating source files