← ClaudeAtlas

scopelisted

Use when unsettled requirements or decisions need a spec, options, acceptance criteria, authority bounds, or decision record. Not for implementing approved scope or writing files during read-only advice; use implement.
mblauberg/provenant · ★ 2 · AI & Automation · score 68
Install: claude install-skill mblauberg/provenant
# Scope Turn an idea into decided, testable scope under project constraints. ## Frame Define the decision, users and done. Search specs and registers. Emit the minimum `config/risk-policy.json` tier plus allowed source/artifact paths, prohibited actions, external effects, expiry and approver. Ordinary authorised workspace content may cross approved provider families; credentials, secrets, platform rules and narrower task/project bans control. Only a user may downgrade risk. Judgement-bearing AI, ranking or heuristics require `evaluate`. Preserve decision context: intake/revision, goals, constraints, alternatives, evidence and decided/parked branches. Revise it; never fork competing scope. Record disclosure in the authority envelope, never private memory. ## Grill Load `grill-me` only when the user explicitly asks to be grilled or dependent owner decisions remain materially unresolved. Then work purpose -> users -> constraints -> edge cases -> failure modes -> success -> exclusions, one question per round. Otherwise present a compact decision packet with 2–3 choices, a recommendation and parked owner calls. Agents decide engineering calls. Business, legal or financial owner calls stay parked as named open-decision rows; never guess. Put every unresolved branch in the spec. ## Resolve uncertainty Research surviving questions; use `orchestrate` for fan-out and source retained claims. Use `prototype` when a timeboxed throwaway answers feasibility; harvest its result and