Handsomeboy990

clarification-gate

Decides what must be asked before architecture and what can proceed on a recorded assumption, then asks it once in a single grouped batch. Prevents both expensive silent guessing and question spam. Run after requirements analysis, before technology and architecture work.

delivery-planning

Turns an approved architecture into an ordered plan of atomic engineering tasks with dependencies, affected modules, validation requirements and tests, grouped into milestones and sequenced so that nothing is built before what it depends on. Run immediately after the validation gate.

requirements-analysis

Turns a specification, brief, PRD, feature list, mockup or client request into an implementable engineering specification, separating explicit requirements, assumptions, constraints and unknowns without ever inventing a requirement. Run first on any project input.

scope-and-change-control

Protects an approved scope and architecture from silent drift. Classifies every discovery as in scope, follow up, or a change requiring approval, and runs the change protocol when implementation contradicts the approved design. Active from the validation gate until delivery.

validation-gate

The hard stop before implementation. Presents a short approval package covering architecture, stack, scope, assumptions, risks and cost, then waits for a human decision and records it. No production code is written before this gate returns an approval.

dependency-selection

Decides whether to add, replace, upgrade or refuse a library through a twelve point evaluation covering existing solutions, platform capabilities, maintenance, security, licence, size, transitive tree, types, accessibility and migration cost. Use before any dependency change.