Product research and PRDs
Turn an early idea into a clearer problem, user need, assumptions, constraints, edge cases, trade-offs, success criteria, and acceptance criteria. Sometimes the right answer is still: we should not build this.
Product architecture in training
Marketing, business and growth background. I learn Product Architecture by getting close enough to code, Git, tests, docs, maintenance and AI-assisted development to see the constraints before they turn into expensive confusion.
Snapshot of the GitHub profile, committed on 2026-09-19.
What I own
The useful part of this profile sits between commercial context and engineering constraints. These are the pieces of work I can carry end to end.
Turn an early idea into a clearer problem, user need, assumptions, constraints, edge cases, trade-offs, success criteria, and acceptance criteria. Sometimes the right answer is still: we should not build this.
Keep READMEs, onboarding, decision notes, architecture context, and product documentation close to the thing that actually exists, not the version everyone remembers from three months ago.
Reproduce problems, gather evidence, narrow scope, write useful issues, and take small changes as far as a reviewable PR when they are inside my technical range. Engineering keeps the final judgment.
Translate product intent into user stories, user journeys, acceptance scenarios, test suites, and test cases that cover expected behavior, edge cases, regressions, and failure paths.
Look at repeated work, decide what AI can prepare safely, define where human review belongs, and turn recurring research, checks, or procedures into reusable skills, workflows, or small internal tools.
Inspect repeated prompts, unnecessary context growth, oversized models doing simple work, weak verification, and duplicated generation. Then test alternatives and measure before claiming savings or quality gains.
Builds
Selected, not exhaustive. Each one is a public repository you can read, clone and challenge.
A coding-agent harness built around research, planning, TDD, verification, review, red-teaming, recovery, and persistent context.
Memory, governance, trust boundaries, and failure lessons for coding agents across multiple hosts.
Evidence gates and session continuity for AI coding agents. No evidence, no ship.
A CLI for routing bounded coding work across local agents with explicit task ownership and a reviewable shipping chain.
A repository-owned hardening playbook that turns security and quality work into explicit, verifiable steps with rollback paths.
Frontend quality gates that challenge generic UI decisions before an agent starts writing the implementation.
An open-source multimodal AI companion for Egyptian Arabic with persona synthesis, stateful behavior, tools, and multi-agent orchestration.
Decision-safe Bayesian marketing science for agents: MMM, diagnostics, CLV, experimentation, budget allocation, provenance, and decision gates.
A model-agnostic AI supervisor and deterministic permission engine for WhatsApp Cloud API.
A cross-host skill compiler for ChatGPT, Codex, Claude Code, and Antigravity, built to make one skill definition portable across runtimes.
A cross-agent marketing strategy pack with specialist skills, challenge gates, and evidence-aware decision workflows.
A commercial art-direction plugin with 21 focused skills, bounded specialist agents, AI image and video direction, and independent visual QA.
A cross-host visual storytelling workflow for animated 1080x1350 infographics with motion craft, RTL support, and visual QA.
Turns ChatGPT Web into a PR-only GitHub agent. It inspects a repo, implements one focused change, opens a reviewable PR, and stops there.
Research, drafting, and copy-audit pipeline tuned for MENA markets and Arabic conversion work.
Linter and pattern analyzer that removes predictable AI writing tropes from product and software copy.
Stack
Some of this I use daily. Some I am learning deeper through current builds.
Method
Four rules that decide what gets built and what gets thrown away.
The starting point is repeated friction, never a tool category.
The system knows the audience, the repo, the rules, and the evidence before it acts.
A test, a report, a PR, or a measured result carries the conclusion.
Agents prepare, inspect, and verify. People own the consequential calls.
Background
I came into software from the commercial side: performance marketing, conversion, campaign strategy and digital leadership across MENA.
After years of asking technical teams to build things, I started building and maintaining my own tools so I could understand the other side of those decisions.
Founder of PrePilot, built around Arabic conversion work. Digital Director with a background in performance marketing, Meta and Google campaign architecture, and direct-response work across MENA. Earlier work included large-scale event marketing at the Hajj Conference and Exhibition.
Today I use public software projects to learn the technical constraints behind product decisions while continuing to work from the commercial context I already know.
A vague issue becomes a reproducible issue with evidence. An early feature becomes research plus a brief. Stale docs get fixed. A small technical change becomes a bounded PR. A day does not have to end with a lot of code. It should end with something another person can inspect and use.
PrePilot gives ChatGPT and Claude 526 structured agency workflows across strategy, paid media, SEO, AEO, GEO, content, ad copy, UGC scripts, landing pages, proposals, decks and reporting. It handles Arabic, English and mixed-language briefs, and keeps review, editing and approval with the team.
Open PrePilot (opens in a new tab)Questions
He works between business questions and engineering handoffs: product research and PRDs, technical documentation, issue discovery and bounded pull requests, test and acceptance design, AI-assisted workflows, and evaluation of AI cost and context discipline.
Yes. He is open to freelance, full-time and part-time work, across Egypt, Saudi Arabia, the United Arab Emirates and the wider GCC. Email mamdouhfces1997@gmail.com or message him on WhatsApp.
No. He comes from marketing, business and growth, and is learning Product Architecture by building, documenting, testing and maintaining real software in public. Engineering keeps the final technical judgment on his work.
PrePilot is a marketing workflow product for agencies, freelancers and marketing teams that already work inside ChatGPT or Claude. It provides 526 structured agency workflows and supports Arabic, English and mixed-language briefs. Mamdouh co-founded it and authors its product and workflow direction.
All of it sits on GitHub under github.com/imMamdouhaboammar, with an interactive catalogue of 142 repositories and a full markdown catalogue organised into ten categories.