Skip to main content

PPS Validation Checklist

This checklist validates proposal readiness under PPS. SFDS suite conformance for PPS is tracked by PPS.manifest.toml and the PPS suite map.

  • Problem statement exists.
  • Mission is one clear paragraph.
  • Design boundaries are explicit.
  • Success criteria are testable.
  • Failure criteria are documented.
  • Constraints are documented.
  • Roadmap describes phases, not just features.
  • An entity-named project manifest such as FileCabinet.manifest.toml exists or is queued.
  • Governing delivery standard is identified.
  • Proposal readiness level is assigned.
  • Risks include mitigations or explicit acceptance.
  • Out-of-scope work is specific enough to prevent scope drift.
  • Operational personas are identified.
  • Technical direction is high-level and does not pretend implementation is complete.
  • WGS lifecycle state is recorded or queued for the project manifest.
  • Broad implementation is blocked unless readiness is ready.
  • Drifted projects are marked rework until the proposal matches reality again.