hamzaish

Slice a goal into the smallest feature slices that can each be PROVEN — every slice ships with a named eval and an end-to-end test, and a slice you can't evaluate or test doesn't get selected. Use after the goal is set and before the spec, so only provable features make the build.

Guided, stateful provisioning of a product's production stack — deep-links, key-format validation, a secrets backend (fnox recommended, or user-touched .env.local), a resumable ledger, CLI automation after signup, and a blocking A1–A10 live gate. Hands off to /security-check → /ship. The walked version of SETUP.md.

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.

Launch the factory's control plane — scaffold and fill FACTORY-ORDERS (weekly mandate + hard budget), STANDING-ORDERS (autonomous-program authority), HEARTBEAT (weekly pulse), and write lifecycle gates for every registered product. A deliberate one-time ritual (re-run to audit); invoke as /factory-launch, not auto-triggered.

One-shot a new product — folders, Next.js starter, product.config.json, CLAUDE.md, scope.md, PRD skeleton, SETUP.md checklist. The Lovable-like ignition.

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

Stress-test an idea or hypothesis. Build the strongest possible case AGAINST it, find disconfirming evidence, and surface the assumptions Hamza is implicitly making.

Quarterly portfolio review. Hard call on what to kill, what to maintain, what to double down on. Forces decisions.

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.

Run a full validation pass on an idea — sharpening, devil's advocate, market sizing, competitor mapping, customer discovery plan.

Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.

Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.

QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.

Map the competitive landscape by tier (direct/indirect/acquirer/adjacent) and argue why each could win. Antidote to competitor neglect.

Plan customer discovery — define target profile, build prospect list, draft interview script, set up outreach + scheduling logistics.

Generate startup ideas grounded in Hamza's existing patterns, current trends, and validated demand signals. Never just brainstorms — pulls from real signals.

Synthesize a batch of customer interviews into evidence-for + evidence-against the hypothesis, with pattern surfacing and bias flagging.

Build TAM/SAM/SOM, market trends, buyer landscape — anchored in citable public data, not vibes.

Turn vague problem observations into testable hypothesis statements with specific who/when/severity/current-workaround dimensions.

Build the brand foundation — positioning, story, voice, naming, visual primitives — so every other launch asset (landing, content, outreach) sings the same song.

First 100 customers by hand. Sourcing → personalized cold messages → follow-up cadence → tracking. Volume × signal, not spam.

Build a community around the product — Discord/Slack/forum, waitlist nurture, early-user comms. Choose the right venue, don't default to Discord.

Build content calendars and draft individual pieces — blog posts, social, LinkedIn, threads — anchored on keyword research and brand voice.

Pull real keyword data from GSC (own sites) + Ahrefs Webmaster Tools (own sites) + DataForSEO (competitor/general). Produce a clustered keyword brief.

Write landing page copy that converts. Hero + 3 value props + social proof + objections + CTA. Anchored on validated user language.

Plan and execute the launch — Product Hunt, Hacker News, X/Twitter, LinkedIn, newsletters, communities — sequenced for compounding signal.

Initial pricing for a product — packaging, tiers, anchor, monthly vs annual, free vs trial. Anchored on value-based pricing + van Westendorp where data exists.

Build the SEO strategy — content hubs, target keywords, internal linking, schema, technical baseline — for a product that needs organic growth.

Define a product's architecture BEFORE Claude Code writes a line. Produces CLAUDE.md, scope.md, and a 1-page architectural decisions doc.

Drive Claude Code build sessions inside a product folder. Enforces session discipline: read CLAUDE.md + scope.md first, log decisions after.

Define the measurement framework BEFORE launch. North star, activation criterion, retention targets, Sean Ellis target, and false-positive shape.

Block scope creep. Every feature ask gets pressure-tested against scope.md. Bar to amend: specific evidence from real users.

Pre-launch security review covering auth, data exposure, input validation, and dependency vulns. Produces a remediation list, not a "looks good" stamp.

Top-level routing brain. Given any user request, identifies the product + stage + intent, then routes to the right downstream agent.

Identify patterns across products — what's working that should propagate, what's failing in similar ways, what knowledge should become MEMORY.md entries.

Decide where attention goes today across the 10-product portfolio. The "if you had 4 hours to work on the portfolio, do this" agent.

Pull metrics across all products into a single view. Powers the dashboard and the daily/weekly briefings.

Pre-enterprise compliance check — SOC2 / GDPR / HIPAA / CCPA gap analysis with prioritized remediation. Not a substitute for real audit.

Design growth loops (Reforge/Balfour framework). Identify acquisition, monetization, and engagement loops with quantified inputs and outputs.

Identify and deepen moats — workflow lock-in, data network effects, domain depth, integration depth. Audit current moats + propose investments.