菜单
Implement planned product or code changes phase by phase using repo patterns and verification. Use when the user asks to build, modify, or finish implementation work.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Explore options, trade-offs, and decision paths without implementing code. Use when the user asks to brainstorm, compare approaches, choose architecture, or save a durable decision note.
Plan and implement safe schema, migration, relationship, index, query, and backfill changes with rollback awareness. Use when data shape or persistence contracts change.
Manage deployment, Docker, CI/CD, environment, secrets, and infrastructure changes with rollback and verification. Use for operational config or release safety work.
Create, update, and audit durable project documentation. Use when code, setup, workflow, architecture, API behavior, or project structure must be reflected in docs.
Coordinate multi-specialist work, handoffs, blockers, and durable progress artifacts. Use when tasks span roles, phases, or parallel workstreams.
Create structured implementation plans with repository research, phased execution, risks, and verification. Use when work is unclear, risky, multi-file, or the user asks for a plan.
基于 SOC 职业分类
| name | fullstack-implementation |
| description | Implement planned product or code changes phase by phase using repo patterns and verification. Use when the user asks to build, modify, or finish implementation work. |
Use this skill when the task is to implement code, not just plan or advise.
plan/*/plan.md; if several candidates exist, inspect their README.md or phase status before choosing.research/ notes and current phase file.mcp-* skill first. If crucial context is unavailable, state the assumption or ask a focused question.plan/<topic>-<timestamp>/plan.md as the execution source of truth when a plan exists. If no plan exists and the task is small, proceed with local context; if the task is multi-step or risky, create or request planning artifacts first.README.md or docs when it affects future work.research/ instead of keeping it only in chat.mcp-context7 for official framework or library docsmcp-github for PR, issue, workflow, or release contextmcp-figma for design-driven implementation detailsmcp-playwright for browser verification and UI flowsmcp-sentry for production issue context tied to the changemcp-open-bridge for implementation-option comparison, blocker analysis, and focused diff reviewReport with: