pm-archive

Use after implementation to apply gstack-inspired quality gates such as review, validation, QA or browse, security checks, and ship readiness without turning them into always-on orchestration.

Use when a request is new, ambiguous, likely to sprawl, or strategically important and you need to turn it into a scoped build-ready plan with prompt, PRD, plan, assumptions, and a readiness check before implementation.

Use when a bug is unclear, recurring, or expensive to guess at and you need a disciplined loop to reproduce the issue, isolate the root cause, apply the smallest fix, and verify the result before moving on.

Use when implementation is approved and you need to run a disciplined build loop with a single writer, scoped execution, validation slices, document updates, and controlled handoff into review and QA gates.