RaulAM7

Distill raw materials from 00_inbox into concise context files in 02_context and prepare 03_specs inputs. Use when inbox is noisy, long, duplicated, or unstructured.

Generate a smart, minimal ICP (Ideal Customer Profile) from any input — messy notes, product descriptions, founder hypotheses, or existing context. Produces a dual-render artifact (human-readable + machine-structured YAML) with observable signals for agentic scraping. Use when the user mentions ICP, ideal customer, target customer, who to sell to, customer profile, buyer persona, target market, or needs to define who they're going after commercially — even if they don't use the term "ICP" explicitly.

Bootstrap the full context layer at project start. Reads everything available (00_inbox, existing 02_context files, 01_harness files, root README and any root-level .md) and fills all context slots in one pass. Also seeds 03_specs/backlog.md and 03_specs/decisions.md when sufficient context exists, and writes a gap report to 05_scratch/. Invoke this skill when starting a new project, when context files are empty or stub-only, or before running write-spec for the first time.

Review a deliverable against the active spec and QA gate, then produce a pass/fail verdict with gaps and fixes. Use before closing any task.

Produce the requested deliverable from the active spec and place it in 04_outputs with predictable naming. Use when a spec is approved and ready to execute.

Create or refine one active SDD-light spec in 03_specs/now from distilled context. Use when execution is unclear, drifting, or missing acceptance criteria.

Extract factual client context from raw inputs (transcripts, notes, discovery materials). Produces a Context Document preserving client voice, structural problems, requirements, beliefs, and transformation desire. Strictly extractive — no Hormozi interpretation. Use when raw materials exist in deals/[name]/00-context/raw/.

Transform a factual Context Document into an interpretive Customer Map using Hormozi logic. The critical bridge between raw context and offer design. Produces 6 blocks (Avatar Day 1, Avatar Day 90, Obstacle Map, Belief Architecture, Value Equation Diagnosis, Transformation Promise) with user validation at each block. HIGH interactivity — pauses after every block for user feedback.

Design a Hormozi Grand Slam offer from Context Document + Customer Map. Applies Value Equation systematically across 12 sections. HIGH interactivity — pauses at strategy direction, stack design, plan architecture, and guarantee for user validation. Produces offer document + self-critique. Use after customer-mapping is complete.

Analyze a completed proposal from the perspective of an implacable buyer/negotiator. Produces a diagnostic with weighted scorecard, bottleneck checklist, improvement playbook, concrete rewrites, and offer-to-proposal fidelity check. LOW interactivity — diagnostic output, user reads and decides. Use after template-formatting is complete.

Validate any deal document before declaring it complete. Checks acceptance criteria, unresolved placeholders, cross-document consistency, and naming conventions. ZERO interactivity — pure validation. Produces a pass/fail report with shortest fix path. Can be invoked at any stage of the pipeline.

Transform an approved Offer Design into a formal business proposal. Mechanical formatting — faithful translation of offer content into proposal template structure. LOW-MEDIUM interactivity — 2 mandatory gates only (methodology at 4.3, guarantee + pricing at 8.1). Batch drafts sections between gates. Use after offer-design is complete.