메뉴
Post a structured Linear project update document on a version release. Orchestrates tapps_release_update → docs_validate_release_update → save_document → cache invalidation. Use when posting a release announcement to Linear after shipping a new version.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Persistent cross-session memory + knowledge graph for AI coding agents. Use when you need to recall prior decisions before making a non-trivial choice, save the rationale behind a decision so it survives the session, share findings across agents in a project (Hive), or record an experience event / KG triple. Talk to the deployed brain at http://127.0.0.1:8080/mcp/ via MCP tools — never via raw psycopg.
Frontend work flow combining UX playbook and standard finish pipeline. Use when the task is primarily UI/UX implementation or accessibility.
Write a structured cross-session handoff and close the TAPPS session lifecycle so the next chat can continue without a long paste. Use when ending a session, handing off to a fresh chat, or the user says hand off, save session state, or continue next time.
Frontend work flow combining UX playbook and standard finish pipeline. Use when the task is primarily UI/UX implementation or accessibility.
Write a structured cross-session handoff and close the TAPPS session lifecycle so the next chat can continue without a long paste. Use when ending a session, handing off to a fresh chat, or the user says hand off, save session state, or continue next time.
Persistent cross-session memory + knowledge graph for AI coding agents. Use when you need to recall prior decisions before making a non-trivial choice, save the rationale behind a decision so it survives the session, share findings across agents in a project (Hive), or record an experience event / KG triple. Talk to the deployed brain at http://127.0.0.1:8080/mcp/ via MCP tools — never via raw psycopg.
| name | linear-release-update |
| description | Post a structured Linear project update document on a version release. Orchestrates tapps_release_update → docs_validate_release_update → save_document → cache invalidation. Use when posting a release announcement to Linear after shipping a new version. |
| mcp_tools | ["tapps_release_update","docs_generate_release_update","docs_validate_release_update","docs_release_gate","linear_save_document","tapps_linear_snapshot_invalidate"] |
Post a structured Linear project update document when a new version is released. The user's request to post a release update is standing authorization for the full pipeline — do NOT pause mid-flow to ask "should I post this?"
Flow:
tapps_release_update(version, prev_version, team, project).
version and prev_version are required. Parse from the user's prompt or ask once if both are missing.team and project: read from .tapps-mcp.yaml if present (linear_team, linear_project fields), otherwise pass empty strings.dry_run=true is requested, pass it through — the tool returns the body without requiring validation to pass.1b. Docs release gate (required unless dry_run): Call docs_release_gate. Stop on fail.
Check the response:
success=false: surface the error.message and findings to the user. Stop — do not post.agent_ready=false (and not dry_run): surface findings, stop.agent_ready=true: proceed.Call linear_save_document:
project: use data.project from the tool response.title: use data.document_title from the tool response (format: Release vX.Y.Z — YYYY-MM-DD).content: use data.body from the tool response verbatim.After save_document succeeds, call tapps_linear_snapshot_invalidate:
team: use data.team from tool response.project: use data.project from tool response.Report the document URL from save_document response and the version that was posted.
Rules:
save_document without a prior agent_ready=true from tapps_release_update (unless dry_run=true).document_title must use the em-dash format from data.document_title — do not construct it manually.data.body verbatim.