ldphuong-vn
- 10 skills
- 0 followers
- 10 hours ago last updated
- ▌ Validate Market Gtm · ldphuong-vnStage 4 of the validation pipeline — market and go-to-market viability. Use to size the market (TAM/SAM/SOM), pick a beachhead, and pressure-test positioning against incumbents. Triggers when the orchestrator routes to MARKET_GTM. Apply the red-team lens here. Always run before committing to a business model.
- ▌ Validate Problem Val · ldphuong-vnStage 2 of the validation pipeline — problem validation. Use to verify the problem is real with evidence rather than opinion, using The Mom Test discipline. Triggers when the orchestrator routes to PROBLEM_VAL (MUST_RUN for greenfield/pivot; ASSERT when a live product already proves demand). Always run before validating any solution.
- ▌ Validate Solution Val · ldphuong-vnStage 3 of the validation pipeline — solution validation. Use to test whether the proposed solution actually moves the needle, via the Riskiest Assumption Test, Value Proposition Canvas, and an MVP/MLP plan. Triggers when the orchestrator routes to SOLUTION_VAL. Always run before market sizing — a great market for a solution nobody adopts is worthless.
- ▌ Validate Decision Gate · ldphuong-vnStage 6 of the validation pipeline — the decision gate. Use this whenever an idea/product/feature/decision has cleared the upstream stages and needs a Go/No-go/Pivot/Park verdict with a confidence score. Triggers when the user asks to "make the call", "should we build/ship/kill this", run a decision review, or when the orchestrator routes to DECISION_GATE. This is the stage that applies Six Thinking Hats, a weighted decision matrix, pre-mortem/inversion/red-team critique, and RAPID roles, then writes verdict + confidence + decision journal into the Dossier. Always use this rather than improvising a verdict, so the decision is evidence-based, reversible-aware, and recorded.
- ▌ Validate Lifecycle Ops · ldphuong-vnStage 8 of the validation pipeline — lifecycle operations and the re-validation loop. Use to define funnel metrics, cohort retention, expand/sunset criteria, and the tripwires that trigger re-running earlier gates. Triggers when the orchestrator routes to LIFECYCLE. Use for live-product audits (case B) and after any GO to close the loop from launch to ongoing operation.
- ▌ Validate Suite · ldphuong-vn bundleOrchestrator for the validation pipeline. Use this whenever the user wants to validate an idea, product, feature, pivot, or a point decision (pricing, channel, kill/sunset) — to prepare for GTM or to run a full-lifecycle operating review. Triggers on "validate this", "should we build/ship/kill X", "stress-test this idea", "is this worth pursuing", "GTM readiness", or any request to vet a concept and produce a decision with evidence and critique. This skill runs Intake (classifies the case and routes the stages), executes the staged gates in order, streams progress to the console, and renders an HTML Validation Dossier at the end. Always use this rather than improvising an ad-hoc analysis, so the result is gated, evidence-based, and recorded in a reusable Dossier.
- ▌ Validate Framing · ldphuong-vnStage 0 of the validation pipeline — framing. Use to turn a vague idea/product/decision into a testable problem statement, a 5W1H frame, and a risk-ranked assumption list, before any gate runs. Triggers when the orchestrator routes to FRAMING or when a user idea is still fuzzy and needs structuring. Always run this first so downstream stages have something concrete to test.
- ▌
- ▌ Validate Hardgate · ldphuong-vnStage 1 of the validation pipeline — the hard gate. A cheap, binary, no-LLM-judgment screen that kills most ideas early before any expensive analysis. Use right after framing. Triggers when the orchestrator routes to HARD_GATE. Always run for new ideas/features; any single FAIL stops the pipeline.
- ▌