Mission Preflight
Unique OpenClaw plugin that turns vague requests into execution-ready briefs with ambiguity scanning, risk stress tests, decision comparison, and high-value clarification prompts.
Install
openclaw plugins install clawhub:openclaw-mission-preflightMission Preflight for OpenClaw
Turn vague requests into execution-ready briefs — before any agent work begins.
Most agent failures don't happen because the model is weak. They happen because the task was underspecified.
Mission Preflight is a native OpenClaw plugin that adds a clarity layer before execution: it scans vague requests for ambiguity, stress-tests plans for failure modes, converts messy notes into structured briefs, and now compares two options side-by-side before you commit.
Why this is unique
ClawHub already has plugins for git workflows, memory, tasks, finance, and security guardrails. None of them fill this specific gap: catching underspecified work before the agent starts executing. That is exactly what Mission Preflight does.
- ✅ No API key required
- ✅ No external service dependency
- ✅ Deterministic, fast, offline-friendly
- ✅ Pure JavaScript logic — instant and free
- ✅ Works across product, marketing, ops, research, and build workflows
Install
openclaw plugins install openclaw-mission-preflight
That's it. The agent immediately gets four new tools.
Tools
1. mission_preflight_scan
Analyze a raw request and return a readiness report.
| Output | What it tells you |
|---|---|
readinessScore | 0–100. Is this request ready to execute? |
ambiguityScore | 0–100. How vague is the request? |
riskScore | 0–100. How risky is the implied work? |
missingInfo | What essential context is missing |
contradictions | Conflicts between scope, timeline, and resources |
suggestedQuestions | Top clarification questions to ask the user |
firstSafeAction | The smallest reversible next step |
priorityLane | Where to focus first |
Example call:
mission_preflight_scan({
request: "Build a popular plugin and upload it today",
strictness: "hard",
maxQuestions: 5
})
Sample output:
Priority lane: Clarify scope first
Readiness: 11/100 | Ambiguity: 68/100 | Risk: 39/100
Ready to execute: Not yet
Missing info:
- Primary user or audience
- Success metric or acceptance criteria
- Budget or resource limits
Suggested questions:
- Who is the main user, and what pain point should it solve first?
- How will we judge success: downloads, revenue, time saved?
- What budget, resources, or limits should the plan respect?
2. mission_preflight_stress_test
Pressure-test a plan or rollout checklist before execution.
Returns failure modes, mitigations, stress level (0–100), and a verdict (Fragile / Needs reinforcement / Reasonably stable).
mission_preflight_stress_test({
plan: "1. Build MVP today 2. Publish tonight 3. Launch tomorrow",
objective: "Ship a viral OpenClaw plugin"
})
3. mission_preflight_brief
Convert messy notes into a compact execution brief.
Returns objective, deliverable, constraints, risks, acceptance criteria, open questions, and next steps. Three output styles: concise, detailed, checklist.
4. mission_preflight_compare (new in v0.2.0)
Compare two plans, ideas, or proposals side-by-side and get a recommendation.
mission_preflight_compare({
optionA: "Build a CRM dashboard in 2 weeks for our 50-person sales team. Budget $5000.",
optionB: "Quickly make something CRM-like ASAP for sales people. Premium quality enterprise platform.",
criteria: "speed, cost, audit risk"
})
Sample output:
Verdict: Option A is the stronger choice
Wins: Option A=4 · Option B=2
| Dimension | Option A | Option B | Winner |
|--------------------|----------|----------|----------|
| Readiness | 98 | 0 | Option A |
| Ambiguity | 0 | 70 | Option A |
| Strength signals | 5 | 0 | Option A |
| Missing info items | 2 | 6 | Option A |
| Contradictions | 0 | 0 | tie |
Recommendations:
- Option A is more fully specified; Option B still needs:
Exact output, Primary user, Deadline, Success metric.
- Both options share 1 risk; pick will not solve it.
Use cases
- Evaluate startup ideas before you build
- Check if a client brief is actionable
- Prepare safer publishing or deployment workflows
- Turn chat chaos into a clean handoff brief
- Stress-test launch plans before you ship
- NEW: Compare two implementation approaches before committing
Configuration
None required. The plugin works out of the box with no environment variables, no auth, no external API.
How it works (under the hood)
The plugin uses deterministic rule-based detection across several signal categories:
- Ambiguity terms (asap, soon, best, optimize, somehow…)
- Big-scope terms (platform, system, integration…)
- Deliverable terms (report, plugin, MVP, dashboard…)
- Audience terms, compliance terms, constraint detection
- Deadline extraction via regex
- Contradiction detection (scope vs. timeline vs. budget)
Scores are bounded 0–100 and stable across runs. No LLM call is made inside the plugin — it is pure logic, so it is instant and free.
Compatibility
- OpenClaw:
>=2026.4.20 - Plugin API:
>=2026.4.20 - Plugin SDK:
2026.4.20
v0.2.0 changes
- Added
mission_preflight_compare— side-by-side decision support across readiness, ambiguity, risk, strengths, missing info, and contradictions. - Improved README with concrete sample outputs visible on the ClawHub listing.
- No breaking changes to the original three tools.
Links
- 📦 ClawHub: https://clawhub.ai/plugins/openclaw-mission-preflight
- 🐙 GitHub: https://github.com/gopendrasharma89-tech/openclaw-mission-preflight
- 🐛 Issues: https://github.com/gopendrasharma89-tech/openclaw-mission-preflight/issues
License
MIT — see LICENSE.