菜单
Use when running, resuming, inspecting, or troubleshooting Platty static analysis, project analysis, repository analysis, repo analysis, pipeline stages, analysis runs, run status, cancellation, or next analysis actions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | platty-static-analysis |
| description | Use when running, resuming, inspecting, or troubleshooting Platty static analysis, project analysis, repository analysis, repo analysis, pipeline stages, analysis runs, run status, cancellation, or next analysis actions. |
For direct invocation, set
PLATTY_INVOCATION_SOURCE=platty-static-analysis on every Platty CLI process
in this workflow. If an outer user-facing workflow routes here, the outer
workflow label wins and overrides this default. Preserve the active label for
retries, resumes, and every nextCommand or nextAction.command execution.
PLATTY_INVOCATION_SOURCE=platty-static-analysis platty analyze --project <project> --json
Use this after a project has at least one registered repository.
platty analyze --project <project> --json
platty analyze --project <project> --from build_route --json
platty status --project <project> --json
platty runs list --project <project> --json
platty runs show --run-id <run-id> --project <project> --json
platty runs cancel --run-id <run-id> --project <project> --reason "<reason>" --json
Keep calling platty status --project <project> --json between phases. When status reports build_docs, switch to platty-docs-target-curation for target curation, then to platty-generated-docs after target scope is accepted.
Static analysis no longer has a public confirmation command. Compatibility
recovery note: if an installed global CLI asks for platty confirm, treat that
CLI as stale and tell the user to rebuild or reinstall it before continuing.
At every pause or completion, use the Platty handoff card. Include the
latest status --json nextAction and any run ids inspected. Recommended Next
values:
run_static_analysis: platty analyze --project <project> --jsonbuild_docs: route to platty-docs-target-curation for target curation, then to platty-generated-docs after target scope is acceptednextAction (type, repoId, stage) repeats across 2+ analyze calls without completedRepositoryIds advancing: the loop is stalled — stop looping and debug with runs list / runs show.runs show reports the run status as failed, or analyze returns PIPELINE_CANCELLED or ANALYSIS_FAILED: stop, report the error payload to the user — do not restart the pipeline without being asked.Use when a Figma URL, Figma page, Figma section, or Figma frame must become reusable, revisioned design evidence before Platty MCP product specification or technical design.
Use when creating locally saved MCP-grounded SDD technical design and executable implementation plans from existing prd.md and user_stories.md.
Use when a user separately requests technical or system design from approved product documents with a Figma URL, current-session Figma evidence, or a validated figma_handoff.json discovered beside the product pair.
Use when a Figma URL accompanies a request to organize, draft, create, or improve a product plan, planning document, feature brief, requirements, PRD, user stories, 기획서, 요구사항, or 기능 기획, with or without existing product documents.
Use when creating locally saved MCP-grounded SDD PRD and user-story drafts from a product idea, feature request, PRD need, policy change, or requirements discussion.
Use when a task should use configured Platty MCP tools for remote project context, tool capability checks, Figma-backed product-plan or 기획서 authoring, Figma evidence routing, client setup routing, Platty MCP retrieval, memory or glossary-alias lifecycle routing, or MCP-grounded SDD file creation.