intent

name	intent
description	Route a vague request into the smallest StackPilot execution lane before planning or editing.

intent

Use this skill when the user gives a broad, fuzzy, or multi-program request and the next lane should be chosen before implementation.

This is a lightweight router, not a planning document. It borrows the intent-first entrypoint style from external skill frameworks while keeping the actual work inside StackPilot packs and provider-native execution.

Flow

1. Restate the requested outcome in one sentence.
2. Name the relevant provider, repo, files, app, or workflow boundary.
3. Pick exactly one next lane:
   • execute for a bounded edit with an obvious verification path.
   • deep-init when repository shape or validation is unclear.
   • team when independent ownership slices can run in parallel.
   • investigate when the cause is unknown.
   • review when the user asks for risks or regressions.
   • qa or ship when acceptance proof is the main work.
4. Name the smallest proof command or check.
5. Stop and ask only when the route would be destructive or materially branching.

Output

• Outcome:
• Boundary:
• Lane:
• Proof:
• Blocker: