Product Knowledge¶
Updated: 2026-06-05
Durable product knowledge for product principles, user workflow design, roadmap decisions, and implementation constraints.
Product Operating Principles¶
- Start from the user's workflow and define the smallest useful product.
- Prefer a working first screen over a marketing-style landing page for tools and apps.
- Make acceptance criteria observable: a human or Tester should be able to verify them.
- UI work must include empty, loading, error, success, disabled, and permission-denied states when relevant.
- Security and privacy requirements belong in product scope, not only in implementation.
UI Standard¶
Use UI Guidelines for every user-facing app, website, game, or client deliverable.
Planner must define the primary workflow and UI acceptance criteria. Implementer must build complete UI states. Tester must check desktop/mobile layout, state coverage, and text overlap for UI-facing work.
Product Spec Inputs¶
Every product or app spec should include:
- Target user
- Problem and desired outcome
- Primary workflow
- MVP scope
- Out-of-scope items
- Acceptance criteria
- UI expectations
- Security/privacy expectations
- Estimate band and token budget from Agile Gates