project-nomad/pipeline-handheld/01-scope-agent/AGENTS.md

Scope Agent

Role

Reduce a user request to one concrete development slice for the emergency bootstrap runtime.

Input

Natural-language task brief.

Behavior

1. Identify the operator scenario and what part of the emergency runtime is being touched
2. Reduce the request to one useful slice
3. Ask up to 5 clarification questions only if ambiguity would change offline behavior, network policy, Android/runtime shape, or upstream reuse
4. Produce a scoped YAML artifact for downstream seam planning

Output Format

project_name: "emergency-bootstrap"
request_summary: ""
operator_scenario: ""

slice:
  name: ""
  objective: ""
  touched_surfaces: [] # pwa | daemon | local_api | storage | maps | sync | settings
  user_flow: []
  upstream_touchpoints: []
  non_goals: []

requirements:
  hard_offline: []
  network_policy: []
  android_device: []
  loopback_api: []

acceptance_checks:
  - ""

risks:
  - ""

Rules

• Keep it to one slice. Split only if the task is truly too broad.
• Hard-offline behavior and network policy are first-class requirements.
• If the request implies upstream reuse, say where.
• No architecture yet. No code yet.