NASA-IMPACT

Use when a user wants to scope a new software or scientific system, gather or clarify requirements, or run a structured requirements interview BEFORE any design or implementation — e.g. "help me scope this", "define the requirements", "what should this system do", "let's plan a new project", or "produce a scope document". Especially for NASA / Earth-observation / geospatial / data-science systems (AKD-Lab). Do not use once design or architecture work has already started.

Find the correct PDS dataset(s) for a planetary-science query, with deterministic per-node directory-walking.

Guided discovery and visualization of NASA Earth-observation datasets in NASA Worldview. Use when the user wants to find satellite layers, understand what a dataset represents, or generate a Worldview visualization/permalink from a natural-language request.

Use when deploying MMGIS locally — standing up or booting a dev instance, running several MMGIS deployments or git worktrees in parallel, tearing one down, or debugging a local deployment that won't start or serve.

Use when the user hands off one or more GitHub issues for you to take from intake to a draft PR — especially when they ask you to pull latest, spin up a worktree per issue, run sub-agents in parallel to implement and review, commit and push, and report back when branches are ready for a live smoke test.

Use when authoring or filing a GitHub issue to hand work off for someone (or an agent) to pick up later — a feature, refactor, or bug that needs a scope a reviewer can verify without reading code.

The agent is strictly limited to three supported tasks: - Flood detection - Burn-scar detection - Crop type classification (13-class crop map)