← ClaudeAtlas

ai-feature-go-no-golisted

Strategy-stage skill: turns an AI-feature idea plus context into a build/kill decision that names the single criterion it turns on. Use when the user asks for a go/no-go, build-or-kill, or ship-worthiness call on an AI or LLM-powered feature — 'should we build AI auto-replies', 'build or kill: LLM search', 'make the call on this AI feature' — or when /pm routes such a request here. Do NOT use for non-AI feature prioritization, for mapping assumptions without deciding (assumption-mapper), for model/vendor selection, or for launch-timing decisions.
Abhillashjadhav/PM-agent-OS · ★ 1 · AI & Automation · score 60
Install: claude install-skill Abhillashjadhav/PM-agent-OS
# AI Feature Go/No-Go A decision, not a discussion. The output is GO or NO-GO, and it names the one criterion doing the deciding — everything else is ranked context. ## Verification gates (defined first; output is blocked until all pass) - **G1 — Pivot criterion named:** the decision states the SINGLE disqualifying (for NO-GO) or qualifying (for GO) criterion it turns on. Five co-equal reasons with no named pivot fails the gate. A conditional GO states its exact condition; "it depends" is not a decision. - **G2 — Non-decisive factors marked:** supporting factors are ranked below the pivot and explicitly marked non-decisive. If removing the pivot wouldn't flip the decision, the pivot is wrong — find the real one. - **G3 — No fabricated context:** the decision argues from provided context only. No invented compliance rulings, competitor moves, usage benchmarks, or user demand. Arithmetic uses input numbers; anything else is a labeled estimate. ## Steps 1. **Fix the failure surface.** What happens when the AI is wrong, who sees it, and can it be caught before harm? Error tolerance × review point is where most AI features live or die — check it first. 2. **Check the remaining axes,** in order: value density (does the feature remove real work — do the arithmetic on volume and FTEs), feasibility at quality bar (can current models meet the tolerance found in step 1), economics (per-unit cost vs. price/margin — route deep dives to roadmap-reality-check), and trust/adoption (will