メニュー
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when styling artifacts with professional themes. Triggers include requests to style slides, docs, reports, HTML landing pages, or any visual artifact with consistent colors and fonts. Provides 10 pre-set professional themes with curated color palettes and font pairings, or generate custom themes on-the-fly.
Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.
Use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when building MCP (Model Context Protocol) servers to enable LLMs to interact with external services through well-designed tools. Triggers include requests to create MCP servers, integrate external APIs or services, or build MCP tools in Python (FastMCP) or Node/TypeScript (MCP SDK).
Use when building elaborate, multi-component HTML artifacts using modern frontend technologies (React, Tailwind CSS, shadcn/ui). Triggers include requests for complex web artifacts requiring state management, routing, or shadcn/ui components. Not for simple single-file HTML/JSX artifacts — use direct generation for those.
Use when co-authoring documentation with users through a structured workflow. Triggers include requests to write documentation, proposals, technical specs, decision docs, RFCs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers.
| name | executing-plans |
| description | Use when you have a written implementation plan to execute in a separate session with review checkpoints |
| compatibility | opencode |
Load plan, review critically, execute all tasks, report when complete.
Announce at start: "I'm using the executing-plans skill to implement this plan."
Note: Tell your human partner that opencode skills work much better with access to sub-agents. The quality of its work will be significantly higher if run on a platform with sub-agent support (such as opencode with the Task tool). If sub-agents are available, use subagent-driven-development instead of this skill.
For each task:
After all tasks complete and verified:
STOP executing immediately when:
Ask for clarification rather than guessing.
Return to Review (Step 1) when:
Don't force through blockers - stop and ask.
Required workflow skills:
