Skip to main content
Corgtex agents build substantial, cohesive features and workflows in one PR. One GPT-6 Astra owner implements and integrates the outcome, then a separate agent performs QA. The owner fixes concrete findings and delivers through protected merge.

​
Direction

  • Optimize for delivered value and elapsed time. Accept manageable, reversible risk.
  • Keep related work together; split only for a concrete independent-release benefit.
  • Make reasonable assumptions and act autonomously within the requested outcome.
  • Use planning help for consequential uncertainty, not as a mandatory stage.
  • Test meaningful behavior and integration. Existing coverage and CI can be sufficient.
  • Stop expanding checks when acceptance and required evidence pass.
  • If attempts stop producing progress, change approach or report the real blocker.
The canonical delivery guide contains repository commands and product boundaries. Keep process there instead of maintaining competing instruction copies.

​
Independent QA

A separate agent reviews the complete integrated diff and acceptance evidence, exercises relevant behavior, and reports concrete blockers together. QA covers correctness, usability, integration, and affected security/data boundaries. The owner fixes findings in the same PR; QA rechecks affected behavior using prior unchanged evidence. Minor imperfections and speculative hardening do not block delivery. QA can also perform formal review with the independent reviewer identity. Native GitHub checks, latest-push approval, conversations, and merge queue govern delivery. There is no custom approval attestation. Valid metadata-only edits do not require another complete code review. See pull requests and testing for the short delivery forms and available tools.