hanzlahabib

rcode-prfaq

Working Backwards PRFAQ challenge to forge product concepts.

rcode-product-brief

Create a product brief through guided discovery or autonomous research. Activates when the user says "create a product brief", "write a product brief", "draft a brief for", "product briefing", or "create the brief". Do NOT use for full PRD (use rcode-create-prd) or market analysis alone (use rcode-market-research).

rcode-create-milestone

Design the milestone roadmap (M1..Mn) for a project from an approved PRD. Activates when the user says "create milestones", "plan milestones", "create roadmap", "what milestones do I need", "break this project into milestones", or "roadmap for this product". Do NOT use for milestone lifecycle (use rcode-new-milestone / rcode-complete-milestone), for decomposing one milestone into epics (use rcode-create-epics-and-stories), or for single-phase planning (use rcode-plan-phase).

rcode-create-prd

Create a new Product Requirements Document from scratch through guided facilitation. Activates when the user says "create a PRD", "write product requirements document", "lets make a PRD", "I want to create a new PRD", "draft requirements for", "new product spec", or "start a PRD". Do NOT use for updating an existing PRD (use rcode-edit-prd), or validating an existing PRD (use rcode-validate-prd).

rcode-frontend-design

Create distinctive, production-grade frontend interfaces with a committed aesthetic direction — typography, colour, motion, spatial composition, backgrounds, visual details — that avoid generic "AI slop". Activates when the user says "design this UI", "build a beautiful frontend", "distinctive design", "creative UI", "unforgettable interface", "award-winning design", "not generic", "bold aesthetic", "brutalist", "editorial", "maximalist", "minimalist luxury", "design a landing page", "standout hero section", "make this look amazing", or "frontend design". Pairs with rcode-clone-website (for copying) and rcode-agent-zahra (branding). Do NOT use for: cloning existing sites (use rcode-clone-website), pure backend, or documentation.

rcode-browser-verify

Use Chrome DevTools MCP to verify browser behaviour — DOM state, console errors, network requests,.

rcode-ci

CI/CD setup and quality gates for the rcode-default stack — GitHub Actions for Node test matrix,.

rcode-dev-story

Execute an approved story file by writing tests and code that fulfill every acceptance criterion. Activates when the user says "dev this story", "implement story {id}", "execute the story", "code the next story", "run dev-story on", or "implement .rcode/phases/{phase}/stories/{file}". Do NOT use without a prepared story file (use rcode-create-story first).

rcode-git-flow

Branching, commits, conflicts, parallel work — aligned with the rcode Epic→Feature→Task hierarchy.

rcode-harden

Security hardening checklist for SaaS applications.

rcode-migrate

Plan and execute the move from MVP to production-grade infrastructure without rewriting from.

rcode-perf

Performance optimisation for the rcode-default stack — Next.js (LCP / TBT / CLS / hydration),.

rcode-scaffold-project

Scaffold a new project for rcode users using the official rcode template repo. Activates when the user says "scaffold project", "create project", "new project", "initialize project", "setup new project", "scaffold from template", "create from template", "rcode new project", or "start a new rcode project". Do NOT use for generating project context files (use rcode-generate-project-context) or cloning websites (use rcode-clone-website).

rcode-source-truth

Cite official documentation before writing or recommending any framework, library, or API code.

rcode-checkpoint-preview

LLM-assisted human-in-the-loop review.

rcode-incremental

Ship code in small, atomic, verifiable steps.

rcode-prove-it

Test-first development.

rcode-trim

Code simplification.

rcode-document-project

Analyze an existing codebase and produce documentation for both human and LLM consumption (brownfield analysis). Activates when the user says "document this project", "analyze this codebase", "generate docs for existing code", "brownfield analysis", or "create LLM-friendly docs". Do NOT use for writing net-new docs (use write-document prompt).

rcode-domain-research

Conduct industry domain deep-dive research to build subject matter expertise on a specific business domain. Activates when the user says "research this domain", "domain deep dive", "explain this industry", "help me understand X industry", or "domain research for". Do NOT use for market analysis (use rcode-market-research) or technical feasibility (use rcode-technical-research).

rcode-market-research

Analyze market size, competitive landscape, customer needs, and trends for a product or industry. Activates when the user says "market research", "competitive analysis", "market analysis for", "size the market", "competitor scan", or "analyze the market for X". Do NOT use for domain deep-dives (use rcode-domain-research) or technical feasibility.

rcode-technical-research

Research technical feasibility, architecture options, and implementation approaches for a proposed product or feature. Activates when the user says "technical research", "feasibility study", "research implementation options", "how would we build X", "what stack for", or "technical feasibility for". Do NOT use for final architecture decisions (use rcode-create-architecture) or market analysis.

rcode-create-epics-and-stories

Break a PRD into epics and user stories that drive development. Activates when the user says "create epics", "break this into stories", "generate the epic list", "epic and story breakdown", "decompose the PRD", or "create the backlog". Do NOT use to prepare a single story for dev (use rcode-create-story).

rcode-create-story

Prepare a dev-ready user story with full implementation context. Activates when the user says "create the next story", "prepare a story", "create story {id}", "write the story for", "get next story ready for dev", or "assemble story context". Do NOT use to execute a story (use rcode-dev-story).

rcode-create-ux-design

Guide through realizing a UX design that informs architecture and implementation — user flows, wireframes, design system updates. Activates when the user says "create UX design", "design the user flow", "wireframe this", "UX plan", "design this screen", or "create the design for". Do NOT use for UI code (use rcode-dev-story) or visual code review.

rcode-edit-prd

Update an existing Product Requirements Document with new sections, revisions, or clarifications. Activates when the user says "update the PRD", "edit the PRD", "add a section to the PRD", "revise requirements", or "change the scope in the PRD". Do NOT use to create a new PRD (use rcode-create-prd) or to validate quality (use rcode-validate-prd).

rcode-validate-prd

Validate an existing PRD for comprehensiveness, leanness, organization, and internal consistency. Activates when the user says "validate the PRD", "review the PRD", "check the PRD", "is the PRD ready", "PRD quality check", or "audit the PRD". Do NOT use to create or edit a PRD.

rcode-check-implementation-readiness

Verify that PRD, UX designs, architecture decisions, and epics/stories are all aligned and ready for implementation. Activates when the user says "check implementation readiness", "is this ready for dev", "verify alignment", "readiness check", "IR check", or "can we start building". Do NOT use during active implementation (use rcode-correct-course instead).

rcode-create-architecture

Write an Architecture Decision Record (ADR) to lock a significant technical decision. Activates when the user says "write an ADR", "create architecture decision", "document this architectural choice", "write an architecture record", "lock this technical decision", or "record the decision to use X". Do NOT use for implementation code (use rcode-dev-story) or sprint planning (use rcode-sprint-planning).

rcode-generate-project-context

Generate a project-context.md file that summarizes project standards, conventions, tech stack, and key patterns for AI agents to reference. Activates when the user says "generate project context", "create context file", "document project conventions", "setup AI context", or "create project-context.md". Do NOT use for full project documentation (use rcode-document-project).

Code & Development Listed

rcode-review

Review code changes using parallel adversarial review layers and produce actionable findings. Activates when the user says "review this code", "run code review", "do a PR review", "review the diff", "critique this implementation", or "CR". Do NOT use for documentation review (use rcode-validate-prd or editorial skills).

rcode-correct-course

Course-correct when major change is discovered mid-sprint or mid-implementation. Activates when the user says "course correct", "change the scope mid-sprint", "we need to pivot", "correct course", "handle scope change", or "change story mid-way". Do NOT use for normal sprint updates (use rcode-sprint-status).

Testing & QA Listed

rcode-qa-generate-e2e-tests

Generate end-to-end tests for an existing feature using the project's standard test framework. Activates when the user says "generate e2e tests", "write e2e tests for", "add end-to-end test coverage", "qa this feature", or "generate integration tests". Do NOT use for unit test generation or code review (use rcode-review).

rcode-retrospective

Run an epic retrospective that reviews completed work, extracts learnings, and produces owned action items. Activates when the user says "run retrospective", "retro", "sprint retrospective", "review completed work", or "extract learnings from this sprint". Do NOT use for active sprint status (use rcode-sprint-status).

rcode-sprint-planning

Generate or update a sprint plan that sequences stories for dev execution. Activates when the user says "plan the sprint", "create sprint plan", "run sprint planning", "sequence the next sprint", or "generate sprint N plan". Do NOT use for epic breakdown (use rcode-create-epics-and-stories) or status reporting (use rcode-sprint-status).

rcode-sprint-status

Generate a sprint status report showing progress, blockers, and recommended next actions. Activates when the user says "sprint status", "how is the sprint going", "generate status report", "sprint progress", or "where are we in the sprint". Do NOT use for retrospectives (use rcode-retrospective).

rcode-ahmed-hassani-director

Technology & Development Director who bridges CTO vision to executable delivery across rcode's engineering teams. Activates when the user says "delivery plan", "engineering standards", "RACI matrix", "cross-team coordination", "DORA metrics", "engineering scorecard", "tech debt backlog", "quality review for team", "delivery timeline", "hand off from architecture to execution", "rcode engineering culture", "talk to Ahmed Al Hassani", or asks about coordinating multiple engineering squads on a single initiative. Do NOT use for: core architecture decisions (use Waleed, CTO), individual engineer 1:1s or performance (use Nasser, Engineering Manager), writing code (use Hanzla/Haitham/ Yousef/Zayd), or sprint ceremonies (use Hussain-SM).

rcode-dalil-scout

Codebase Scout — Dalil (دليل) — for repository discovery, multi-root exploration, focused topic sweeps, and producing structured codebase documents (STACK, ARCHITECTURE, STRUCTURE, INTEGRATIONS, CONVENTIONS, TESTING, CONCERNS). Activates when the user says "scan the codebase", "map the codebase", "what's in this repo", "discover X across the project", "audit instrumentation", "find all callers of Y", "is there any Sentry / GraphQL / Redis usage", "explore the project structure", "talk to Dalil", or "scout this repo". Also activates via /rcode-scan and /rcode-map-codebase. Do NOT use for: plan execution (use executor), strategic decisions (use Sadiq / Waleed), test design (use Fatima), or code modification (use Hanzla / Omar).

Testing & QA Listed

rcode-fatima-qa

QA engineer for test generation, test strategy, edge-case hunting, bug triage, and release gating. Activates when the user says "write tests for", "generate e2e tests", "add test coverage", "test this feature", "find edge cases", "bug report", "test strategy", "release gate", "go/no-go decision", "quality check", "what could break", "talk to Fatima", or pastes code and asks for tests. Also activates when asked to verify acceptance criteria, audit test coverage, or review a PR from a quality lens. Do NOT use for: writing production code (use Hanzla), planning sprints (use Hussain-SM), deployment (use Khalid), or UX testing like usability studies (use Layla).

rcode-haitham-frontend

Senior frontend engineer for React, Next.js, Tailwind, shadcn/ui, Arabic RTL layouts, pixel-perfect UIs, website clones, and production frontend work at rcode scale. Activates when the user says "build this UI", "implement the frontend", "React component", "Next.js page", "clone this website", "pixel-perfect build", "Arabic RTL layout", "responsive design", "implement this mockup", "shadcn component", "Tailwind styling", "frontend bug", "talk to Haitham", "rcode frontend", or pastes a Figma/screenshot and asks for implementation. Also activates for accessibility implementation (keyboard nav, ARIA, focus management) and bilingual (Arabic-English) UI work. Do NOT use for: UX design decisions (use Layla), backend APIs (use Yousef), ML/data integration (use Zayd), or architecture decisions (use Waleed).

rcode-hanzla-engineer

Senior full-stack software engineer for story execution, code implementation, bug fixes, refactoring, and hands-on development work. Activates when the user says "implement this", "build this feature", "write the code for", "fix this bug", "refactor this", "dev this story", "code review this", "implement the next story", "work through the sprint", "ship this", "write tests for", "debug this", "talk to Hanzla", or pastes a story file and asks for implementation. Also activates when the user shares an error message and asks for a fix, or asks how to structure specific code. Do NOT use for: choosing tech stack (use Waleed), planning sprints (use Hussain-PM), UX design (use Layla), testing strategy design (use Fatima), deployment (use Khalid), or writing product requirements (use Hussain-PM).

rcode-hussain-pm

Product Manager for PRD creation, requirements discovery, user research framing, and scope prioritization. Activates when the user says "create a PRD", "write product requirements", "what should we build", "define the scope", "user story", "acceptance criteria", "validate this PRD", "edit the PRD", "create epics and stories", "course correct", "implementation readiness check", "as the PM", "talk to Hussain", or pastes a feature idea and asks what to build first. Also activates for Jobs-to-be-Done analysis, opportunity scoring, and stakeholder alignment questions. Do NOT use for: sprint planning and story flow (use Hussain-SM), architecture decisions (use Waleed), implementation (use Hanzla), testing strategy (use Fatima), or visual design (use Layla).

rcode-hussain-sm

Scrum master for sprint planning, story preparation, sprint status reporting, retrospectives, and mid-sprint course correction. Activates when the user says "plan the sprint", "create the next story", "prepare the story", "sprint status", "run retrospective", "retro", "sprint review", "daily standup", "story ready for dev", "what's the sprint goal", "course correct", "change the sprint mid-way", or "scrum master". Also activates for epic reviews and agile ceremony facilitation. Do NOT use for: writing PRDs or defining product vision (use Hussain-PM), market research (use Sadiq), architecture (use Waleed), implementation (use Hanzla), or testing (use Fatima).

rcode-layla-designer

UX Designer and UI specialist for interaction design, user flows, design systems, accessibility audits, and visual craft reviews. Activates when the user says "design this", "user flow", "wireframe", "UX review", "design system", "accessibility audit", "a11y", "UI states", "empty state", "loading state", "error state", "mobile layout", "responsive design", "user journey", "usability", "talk to Layla", or pastes a screen mockup and asks for feedback. Also activates for WCAG compliance checks and design token generation. Do NOT use for: writing front-end code (use Hanzla), backend architecture (use Waleed), writing PRDs (use Hussain-PM), or test cases (use Fatima).

rcode-majlis-council

Multi-agent consulting council that convenes the rcode team to discuss any topic, collects perspectives from all relevant specialists, and delivers a synthesised answer with explicit dissent noted. Activates when the user says "convene the majlis", "consult the team", "ask everyone", "what does the team think", "get all perspectives", "team consultation", "council decision", "discuss this with the team", "multi-agent discussion", "ask all agents", "sab sa consult karo", "team meeting", "crisis mode", "incident response", or asks a question that touches multiple domains (strategy + tech + product + ops). Do NOT use for: single-specialist questions where one agent is clearly the right owner (invoke that agent directly), or running the read-only dashboard (use Diwan).

rcode-mariam-marketing

Marketing lead for go-to-market strategy, positioning, enterprise and government client messaging, Arabic-English bilingual content, case studies, pitch support, brand consistency, and B2B lead generation at rcode. Activates when the user says "marketing strategy", "GTM", "go to market", "positioning for", "write the pitch", "case study", "sales enablement", "pricing strategy", "elevator pitch", "value proposition", "competitive messaging", "website copy", "client proposal", "sales deck support", "talk to Mariam", or asks about winning a specific client (government, telecom, oil & gas, logistics). Also activates for Omani and GCC market-specific messaging. Do NOT use for: market research or competitive analysis (use Sadiq — strategic research), writing technical docs (use Noor), or product requirements (use Hussain-PM).

rcode-nasser-eng-manager

Software Engineering Manager who runs day-to-day team operations at rcode — 1:1s, hiring, onboarding, growth plans, performance feedback, burnout detection, and squad composition. Activates when the user says "1:1 with", "prepare for 1 on 1", "performance review", "hiring plan", "interview loop", "growth plan", "career conversation", "new hire onboarding", "give feedback to", "team health", "burnout check", "squad composition", "engineering manager question", "talk to Nasser", or asks about an individual engineer's growth or performance. Do NOT use for: delivery timelines or cross-team coordination (use Ahmed Al Hassani, Tech Director), core architecture decisions (use Waleed, CTO), sprint ceremonies (use Hussain-SM), or writing code (use Hanzla/Haitham/Yousef/Zayd).

rcode-noor-writer

Technical writer, scribe, and presentation lead for documentation, README files, API docs, architecture diagrams (Mermaid), pitch decks, changelog entries, and blog posts. Activates when the user says "write the README", "document this", "explain this code", "create a diagram", "Mermaid diagram", "write the changelog", "draft a blog post", "pitch deck", "presentation", "write the announcement", "create the API docs", "user guide", "technical explanation", "validate this doc", or "talk to Noor". Also activates for executive summaries, meeting notes, and release notes. Do NOT use for: writing PRDs (use Hussain-PM), code implementation (use Hanzla), market research (use Sadiq), or test cases (use Fatima).

rcode-raees-orchestrator

Project orchestration director — Raees (رئيس) — that dispatches work to the right rcode specialist(s), sequences phases, identifies parallel vs sequential work, and coordinates handoffs. Activates when the user says "who should do this", "dispatch this", "coordinate the team", "orchestrate", "plan the execution", "sequence the work", "build the dispatch plan", "what order should we do this in", "who owns this", "route this request", "handle this end to end", "kaam ko route karo", or brings a multi-step request that touches more than one domain. Do NOT use for: strategic decisions that need full council discussion (use Majlis), single-owner questions where the specialist is obvious, or running the dashboard (use Diwan).