plan-validate

Validate implementation plans against intent using reverse-questioning, assumption stress-testing, and gap analysis

跳到安装

仓库: InugamiDev/ultrathink-oss
最近来源活动: 2026年3月24日 23:57
检测到的 SKILL.md 语言: 英语
星标: 43
分支: 10

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/InugamiDev/ultrathink-oss --skill plan-validate

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

design-kit

Unified design foundations — design system architecture, tokens, component specs, visual principles, creative vision, figma integration, plus brand design system loader (66 real brands via DESIGN.md). Absorbs design, design-system, design-systems, design-principles, design-router, creative-vision, figma, design-md.

2026-05-14

preview

Render, summarize, and present markdown documents and structured content in multiple output modes

2026-05-14

ultra-ui

Ultra UI skill - combines Google's DESIGN.md spec (machine-readable design tokens) with the ui-ux-pro-max knowledge base (91 styles, 161 palettes, 73 font pairings, 161 products, 104 UX guidelines, 25 chart types). Generates lint-clean DESIGN.md files, validates token references and WCAG contrast, exports Tailwind/DTCG tokens, and diffs design systems version-over-version.

2026-05-14

查看这个仓库的全部 Skills

Plan-Validate Skill

Purpose

Serve as the adversarial reviewer of implementation plans. This skill's job is to find what is wrong, missing, or fragile in a plan BEFORE execution begins. It uses reverse-questioning, assumption stress-testing, and gap analysis to surface problems that are cheap to fix on paper and expensive to fix in code.

Think of this as a pre-mortem: imagine the plan has already failed, then work backward to find out why.

Workflow

Pass 1: Intent Alignment Check

Restate the original intent in one sentence. If the original intent is not available, infer it from the plan's objective.
Compare plan scope to intent -- Does the plan actually deliver what was asked for? Common misalignments:
- Plan is broader than intent (scope creep baked in)
- Plan is narrower than intent (missing features)
- Plan solves an adjacent problem (misunderstood requirement)
Generate 3-5 reverse questions -- Questions phrased as "If we complete this plan exactly as written, will we have [X]?" where X tests different facets of the original intent.

Pass 2: Assumption Stress Test

Extract every assumption -- Both explicitly stated and implicit ones buried in the plan.
For each assumption, apply the inversion test: "What happens if the opposite is true?"
- If the answer is "the plan still works" -- the assumption is non-critical.
- If the answer is "the plan breaks" -- the assumption is load-bearing and must be verified before execution.
Flag unverified load-bearing assumptions as blockers.

Pass 3: Completeness Audit

Check for missing phases -- Is there a gap between phases where work would need to happen but is not accounted for?
Check for missing tasks within phases -- Are there implied subtasks not listed?
Check for missing cross-cutting concerns:
- Error handling / failure modes
- Testing strategy
- Rollback plan
- Data migration (if applicable)
- Security implications
- Performance implications
- Accessibility (if UI work)
- Documentation updates
Check dependency chain -- Are there circular dependencies? Missing dependencies? Implicit ordering that is not stated?

Pass 4: Feasibility Check

Complexity calibration -- Are the complexity estimates realistic? Look for:
- "Low complexity" phases with high uncertainty (likely underestimated)
- Phases with no unknowns (likely overconfident)
- Integration phases marked as simple (integration is rarely simple)
Resource check -- Does the plan assume resources (APIs, services, permissions) that may not be available?
Timeline sanity -- If a timeline is given, does it account for testing, review, and iteration?

Pass 5: Verdict

Assign a readiness score:
- Green: Plan is solid. Minor suggestions only. Proceed to execution.
- Yellow: Plan has gaps or unverified assumptions that should be addressed first. Revise specific sections.
- Red: Plan has fundamental issues. Major revision needed. Return to plan skill.
Produce the validation report using the template below.

Validation Report Template

# Plan Validation Report

## Intent Alignment
**Original intent**: [one sentence]
**Plan delivers**: [one sentence summary of what the plan actually produces]
**Alignment**: Aligned | Partially Aligned | Misaligned

### Reverse Questions
1. If we complete this plan exactly, will [X]? → [Yes/No/Unclear]
2. ...

---

## Assumption Audit
| # | Assumption | Load-Bearing? | Verified? | Risk if Wrong |
|---|-----------|---------------|-----------|---------------|
| A1 | ... | Yes | No | [consequence] |

### Blockers (Unverified Load-Bearing Assumptions)
- A1: [assumption] — Must verify before Phase [N]

---

## Completeness Gaps
- [ ] [Missing element] — Affects Phase [N]
- [ ] ...

## Feasibility Concerns
- [concern 1]
- [concern 2]

---

## Verdict: 🟢 Green | 🟡 Yellow | 🔴 Red

### Recommendations
1. [Highest priority fix]
2. [Second priority fix]
3. ...

### Suggested Next Steps
- [ ] [action]

Usage

After creating a plan

/plan-validate

(Automatically picks up the most recent plan from context)

With explicit plan reference

/plan-validate Check the authentication migration plan against the original requirement: "Users must be able to log in with Google and GitHub OAuth"

Quick validation

/plan-validate Is this plan ready to execute?

Examples

Example: Catching scope misalignment

Plan objective: "Build user authentication with JWT" Original intent: "Users need to log in"

Reverse question: "If we complete this plan, will users be able to reset their password?" Finding: Plan covers login/signup but not password reset, which is implied by "users need to log in."

Example: Catching a hidden assumption

Plan task: "Migrate user table to new schema" Hidden assumption: Existing data can be transformed without loss Inversion: What if some existing data does not fit the new schema? Finding: Plan needs a data audit task before migration phase.

Guidelines

Be constructively adversarial -- The goal is to make the plan better, not to prove it is bad.
Prioritize findings -- Not all gaps are equal. Flag blockers separately from nice-to-haves.
Do not rewrite the plan -- Identify problems and let the user (or plan skill) fix them.
Ask the uncomfortable questions -- "What happens when this fails?" is always a valid question.
One round is usually enough -- If a plan fails validation badly, it needs replanning, not more validation passes.
Verify, do not assume -- If you are unsure whether an assumption holds, flag it rather than guessing.

name	plan-validate
description	Validate implementation plans against intent using reverse-questioning, assumption stress-testing, and gap analysis
layer	hub
category	workflow
triggers	["/plan-validate","validate this plan","stress test the plan","check the plan","review the plan"]
inputs	[{"plan":"The implementation plan to validate (from plan skill or user-provided)"},{"originalIntent":"The original goal or request that spawned the plan (optional but recommended)"}]
outputs	[{"validationReport":"Structured report with findings, gaps, and recommendations"},{"reverseQuestions":"Questions that expose hidden assumptions or misalignments"},{"strengthScore":"Qualitative assessment of plan readiness (Red/Yellow/Green)"}]

name	plan-validate
description	Validate implementation plans against intent using reverse-questioning, assumption stress-testing, and gap analysis
layer	hub
category	workflow
triggers	["/plan-validate","validate this plan","stress test the plan","check the plan","review the plan"]
inputs	[{"plan":"The implementation plan to validate (from plan skill or user-provided)"},{"originalIntent":"The original goal or request that spawned the plan (optional but recommended)"}]
outputs	[{"validationReport":"Structured report with findings, gaps, and recommendations"},{"reverseQuestions":"Questions that expose hidden assumptions or misalignments"},{"strengthScore":"Qualitative assessment of plan readiness (Red/Yellow/Green)"}]

plan-validate

来源信息

安装方式

检查来源文件

同仓库更多 Skills

同仓库更多 Skills

Plan-Validate Skill

Purpose

Workflow

Pass 1: Intent Alignment Check

Pass 2: Assumption Stress Test

Pass 3: Completeness Audit

Pass 4: Feasibility Check

Pass 5: Verdict

Validation Report Template

Usage

After creating a plan

With explicit plan reference

Quick validation

Examples

Example: Catching scope misalignment

Example: Catching a hidden assumption

Guidelines