菜单
Engineering review of a development plan. Checks architecture, data model, API design, testing strategy, and implementation feasibility. Use when asked to 'review the engineering plan', 'technical review of the plan', or 'is this plan technically sound'.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | plan-eng-review |
| source | adapted from gstack (MIT License) |
| trigger | auto+manual |
| version | 1.0.0 |
| description | Engineering review of a development plan. Checks architecture, data model, API design, testing strategy, and implementation feasibility. Use when asked to 'review the engineering plan', 'technical review of the plan', or 'is this plan technically sound'. |
Review a development plan from an engineering perspective.
Read the active plan file (from .claude/plans/ or conversation context).
ENGINEERING PLAN REVIEW
═══════════════════════════════
Plan: {title}
Architecture: {score}/10 — {summary}
Data model: {score}/10 — {summary}
API design: {score}/10 — {summary}
Feasibility: {score}/10 — {summary}
Testing: {score}/10 — {summary}
Critical gaps:
1. {most critical missing consideration}
2. {second critical gap}
Recommendations:
1. {highest priority suggestion}
2. {second priority}
Automated plan review. Reads the active plan file and runs strategy, engineering, and design reviews automatically. Challenges assumptions, detects scope creep, suggests alternatives. Use when asked to 'review the plan', 'check my plan', 'is this plan good', 'validate the plan', 'review before implementing', 'plan review', 'technical plan review', 'architecture review of the plan', or 'does this plan make sense'.
Web performance benchmarking. Measures TTFB, FCP, LCP, bundle sizes, and resource loading. Compares against baselines to detect regressions. Use when asked to 'benchmark', 'performance audit', 'check page speed', 'how fast is this site', 'measure load time', 'performance regression', 'check bundle size', 'analyze page performance', 'why is this slow', 'measure web vitals', or 'LCP is too high'.
Use before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation. Chat triggers: 'let's brainstorm', 'brainstorming', 'what should we build', 'how should this work', 'explore options', 'think about this', 'what are the requirements', 'design before build', 'plan this feature', 'what do we need', 'help me think through', 'creative session', 'idea exploration', 'feature brainstorm', 'requirements gathering'.
Post-deploy visual monitoring. Watches the live app after a deploy, takes screenshots, checks console errors, compares against baselines. Use when asked to 'canary', 'monitor production', 'check deploy health', 'verify the site after deploy', 'is the deploy working', 'check for regressions after deploy', 'monitor the release', 'visual health check', or 'did the deploy break anything'.
Safety guardrails for destructive commands. Warns before rm -rf, DROP TABLE, force-push, git reset --hard, and similar destructive operations. Use when asked to 'be careful', 'safety mode', 'prod mode', 'careful mode', 'don't break anything', 'warning mode', 'protect against destructive commands', 'safe mode', or 'double check before running commands'.
Save and resume working state checkpoints. Captures git state, decisions made, and remaining work so you can pick up exactly where you left off — even across sessions. Use when asked to 'checkpoint', 'save progress', 'where was I', 'resume', 'what was I working on', 'pick up where I left off', 'save my work', 'save state', 'pause this', 'come back later', or 'what's left to do'.