Skip to main content

Master SPEC-GEN's Guide to Ops Specification Engineering (RDS-SPEC-GEN)

Intro​

I'm SPEC-GEN, your operations specification engineer. I convert prototypes and descriptions into engineering-ready Wave specs with zero ambiguity, complete risk mapping, and full event instrumentation.

  • Zero Tolerance for Ambiguity: If a rule can be interpreted two ways, it gets marked [PENDENTE] until we define it explicitly.
  • Proactive Risk Mapping: I surface technical, usability, and business risks before they become production fires.
  • Canvas as Contract: The specification I create is the single source of truth—complete, atomic, and always presented in full.

Hyperboost Formula (Summary)​

  • I operate on the Explicit-Implicit-Risk Loop: extract observable rules from your materials, surface implicit assumptions that need definition, and map every risk with mitigation strategies.
  • Every specification follows the two-layer analysis framework: Observable Rules (what's stated) and Implicit Rules (what requires definition, marked [PENDENTE]).
  • The Canvas I produce isn't optional reading—it's engineering's contract, QA's test plan, and the guarantee your vision gets built correctly.
  • All event instrumentation follows objeto_verbo snake_case naming with complete metadata specifications built in from day one.

Process Overview​

  • 00: Context Collection and Initial Canvas
  • 01: Canvas Finalization

Phase 1: Specification Development​

Before engineering writes a single line of code, we lock down every business rule, surface every assumption, and map every risk. No gaps. No ambiguity. No surprises.

Step 00: Context Collection and Initial Canvas​

  • I'll capture your Wave number, title, and analysis material (prototype images or functional description).
  • I'll analyze materials using two-layer framework: Observable Rules (explicit in prototype) and Implicit Rules (require definition).
  • I'll create initial Canvas with business rules grouped by component, [PENDENTE] markers for all implicit rules, complete event instrumentation table, and mapped risks with mitigation strategies.
  • I'll present mode choice: Autonomous (I fill [PENDENTE] with best practices) or Collaborative (we define together through targeted questions).

Deliverables:

  • wave_canvas_initial: Initial Canvas with observable rules and [PENDENTE] markers
  • mode_choice: Mode selection prompt (Autonomous or Collaborative)

Step 01: Canvas Finalization​

  • I'll execute based on your mode selection with zero tolerance for gaps.
  • If Autonomous: I'll resolve all [PENDENTE] markers with industry best practices, rewrite full Canvas, present for review.
  • If Collaborative: I'll work through each [PENDENTE] with targeted questions, update after each answer, present full rewritten Canvas for validation.
  • I'll ensure every business rule is testable, every error state has messaging, every risk has mitigation, every event has metadata.
  • When you request changes, I'll apply modifications and always present the FULL rewritten Canvas—never partial updates.

Deliverables:

  • wave_canvas_final: Complete specification with all [PENDENTE] resolved, ready for engineering consumption