菜单
Validate implementation confidence and surface uncertainties before coding. Use when user says "confidence check", "ask for more details", "validate plan", or after task document is created but before implementation. Ensures 95%+ confidence on all items and surfaces change requests.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | confidence-check |
| description | Validate implementation confidence and surface uncertainties before coding. Use when user says "confidence check", "ask for more details", "validate plan", or after task document is created but before implementation. Ensures 95%+ confidence on all items and surfaces change requests. |
Validates implementation readiness by evaluating confidence levels and surfacing uncertainties.
Examine all descriptions, plans, and decisions made so far:
For each implementation item, evaluate confidence level:
| Item | Confidence | Gap |
|------|------------|-----|
| Database schema changes | 98% | — |
| Server action authorization | 85% | Unclear role hierarchy |
| UI component props | 90% | Missing loading state spec |
Confidence criteria:
Re-evaluate whether implementation would modify settled work:
Only consider modifications if they materially affect correctness, scalability, or safety.
Ignore:
- Elegance improvements
- Stylistic changes
- Speculative future needs
If material impacts found, prepare Change Requests:
⚠️ Change Request #1: [Settled Item]
- Current: [What exists]
- Required change: [What needs to change]
- Why material: [Correctness/Scalability/Safety reason]
- Approval needed before implementation
If no material impacts:
"No change requests required — implementation does not materially impact settled work."
For items below 95% confidence, ask clarifying questions:
**Q[N]: [Topic]**
Current understanding: [What I think is needed]
Uncertainty: [What's unclear]
- **Option A:** [Interpretation 1]
- **Option B:** [Interpretation 2]
- **Option C:** [Interpretation 3]
*My recommendation: Option [X]* - [Rationale]
Present final assessment:
## Confidence Summary
**Overall: [X]%**
✅ Ready (95%+):
- [Item 1]
- [Item 2]
⚠️ Clarified this session:
- [Item 3] — resolved via Q1
- [Item 4] — resolved via Q2
🔄 Change Requests (require approval):
- CR#1: [Description]
**Status:** [Ready for implementation / Awaiting answers / Awaiting CR approval]
Only proceed when:
State clearly:
"Confidence check complete. All items at 95%+ confidence. Ready for implementation."
OR
"Awaiting [answers to Q1-Q3 / approval for CR#1] before implementation can proceed."
User: "confidence check"
Response:
Thorough post-implementation code review. Use when user says "code review", "review code", "review changes", or after implementation is complete. Reviews all changes, identifies issues, checks for unintended settled work modifications, and produces prioritized fix list.
Commit and push all changes from the session. Use when user says "commit and push", "commit push", "push changes", "git commit", or at the end of an implementation session. Creates descriptive commit message and pushes to remote.
Analyze a roadmap Phase for dependencies and implementation order. Use when user says "prep section", "prepare phase", "analyze phase dependencies", or wants to plan implementation order for a Phase. Creates visual workflow and saves to file.
Thorough post-implementation code review. Use when user says "code review", "review code", "review changes", or after implementation is complete. Reviews all changes, identifies issues, checks for unintended settled work modifications, and produces prioritized fix list.
Update task document and roadmap with session results. Use when user says "status update", "update status", "update roadmap", "update task", or after code review is complete. Documents what was completed, decisions made, and updates roadmap progress.
Start implementing a roadmap subsection with impact analysis and structured Q&A. Use when user says "start subsection", "work on subsection", "implement [Phase X] [Subsection Y]", or references working on a specific phase/subsection from the roadmap. Analyzes settled work for impacts, asks clarifying questions with options, then delegates to task-creator for file creation.