Map Territory Workflow

Use this skill as the suite entrypoint. The map is the prompt, plan, context, and artifacts. The territory is the actual codebase, domain, runtime, data, users, constraints, and reviewer expectations. The job is to keep the map and territory close enough that agentic work can proceed without hidden drift.

Phase Map

Pre-implementation:

• blindspot: find relevant unknown unknowns and cheap probes.
• brainstorm-prototype: generate options or disposable prototypes when the user has taste or criteria they can recognize but not yet describe.
• interview-unknowns: ask high-leverage questions that can change the plan.
• reference-alignment: extract requirements from examples, source code, screenshots, docs, or prior work.
• implementation-plan-review: write a plan that foregrounds decisions likely to change.