V (5)

argus-repo-intake

argus

Use for Argus-style repository intake, baseline mapping, architecture discovery, required-file inspection, risk identification, and preparing a scoped work plan before edits.

Argus Repo Intake

IPurpose

Inspect a repository enough to understand its structure, constraints, validation commands, and safe edit boundaries.

IIWorkflow

  1. Confirm the repo root.
  2. Read local AGENTS.md or equivalent instructions first.
  3. Check whether .git exists; recommend Git by default when it is missing unless the operator marks the work disposable.
  4. Map root files, key folders, package metadata, and existing validation commands.
  5. Identify architecture boundaries and files likely affected.
  6. Produce a concise baseline summary and next-step plan.

IIIContext Control

Read only the files needed for the task. Use search and file listings before opening large files.

IVStop Conditions

Stop when the repo root is unclear, required baseline files are missing, or confidence is below 95%.

VOutput

Return:

  • repo root
  • architecture summary
  • relevant instructions found
  • validation commands
  • source-control status
  • safe edit scope
  • open risks
← back to the stoa