Skip to content

Prototype And Current-State Discovery

Purpose: understand the existing software delivery system and classify prototype evidence before assigning agent work.

Use this section by itself when the team needs to map current workflow, evidence, permissions, or data sensitivity before changing how agents are used.

Inputs

  • Repository instructions, README files, build files, package files, and environment files.
  • Repositories and delivery paths the user is allowed to disclose.
  • Application entry points, routes, screens, APIs, services, and use cases.
  • Prototype elements to retain, refactor, replace, spike, or classify as unknown.
  • Data sensitivity.
  • Review and release gates.
  • Known friction.

Outputs

  • Current-state map.
  • Prototype disposition inventory.
  • Source and evidence list.
  • Permission boundary.
  • Data-sensitivity summary.
  • Productionization gaps.
  • Open-question register.

Agent Task Contract

Create a discovery plan that names the evidence to inspect, the questions to ask, and the risks to classify.

Help keep the current-state map, evidence list, permissions summary, and data-sensitivity notes current as new facts appear. Keep human review and acceptance explicit.

Do not infer permission, compliance, or production authority from incomplete evidence.