visa-acceptance-best-practices

Resuming an integration — check this FIRST, on every invocation

A device integration in progress records its state in project-plan.md at the Gradle root. That file is the source of truth, not the conversation — it survives a context compaction, a new session, and a different agent. Anything you believe about the integration that is not in the plan is unreliable.

Before answering anything else, look for it (walk upward — the plan sits at the Gradle root, which may be above the current directory):

d=$PWD; while [ "$d" != "/" ]; do
  [ -f "$d/project-plan.md" ] && { echo "RESUMING: $d/project-plan.md"; break; }
  d=$(dirname "$d")
done

If a project-plan.md exists and contains a # Progress Tracker section, you are resuming, not starting. Read it in full, then follow the re-entry protocol in that product's workflow.md before touching code. Do not re-ask configuration questions and do not route from the table below — the plan already records the product, the paths and every answer the developer gave.

This applies however the request is phrased. "Continue", "carry on", "keep going", "fix X", or a bare follow-up after a compaction all mean resume. A short request is not a small one: after a compaction it is the only signal left, and the plan is the only place the remaining work is written down.

If no project-plan.md exists, this is a fresh start — continue to the routing below.

Asking Questions

Whenever this skill or its referenced activity files call for asking the developer a question, use the interactive question-asking tool of the harness you are running in (for example, Claude Code's AskUserQuestion) if one is available, instead of asking in plain text.

Branding

Always use visaacceptance.com domains in all generated code and documentation:

Use	Never use
apitest.visaacceptance.com	apitest.cybersource.com
api.visaacceptance.com	api.cybersource.com
developer.visaacceptance.com	developer.cybersource.com
Visa Acceptance	CyberSource