@hanzlaa/rcode 3.6.16 → 4.1.0

package/rihal/references/workstream-flag.md

@@ -1,166 +0,0 @@
-# Workstream Flag — When to Use Workspace Isolation
-
-This reference explains when to use `--workspace` flag vs. sequential phases in `.planning/`.
-
-## Sequential Phases (Default)
-
-Use the standard planning pipeline (`.planning/phases/`) for:
-
-- **Linear work** — Phase 1, Phase 2, Phase 3 in order
-- **Dependent phases** — Phase 2 cannot start until Phase 1 is done
-- **Single focus** — One team/project working on one thing
-- **Milestone-driven** — All phases contribute to the same goal
-
-**Example:**
-```
-/rihal-plan Build authentication system
-/rihal-plan Add user profile pages (depends on auth from Phase 1)
-/rihal-plan Write deployment guide (depends on both phases complete)
-```
-
-These run sequentially, each depending on the previous phase's completion.
-
-## Workspace Isolation (Parallel)
-
-Use workspaces (`--workspace` flag) for:
-
-- **Parallel work** — Multiple initiatives happening at the same time
-- **Independent goals** — Each workspace has its own ROADMAP
-- **Context switching** — "I need to pause Q2 roadmap and fix critical bugs"
-- **Team separation** — Team A works on Feature X, Team B works on Feature Y
-- **Risk isolation** — "Keep the hotfix separate from experimental work"
-- **Deadline urgency** — "Fast-track this in a separate workspace while main work continues"
-
-**Example:**
-```
-# Main workspace (Q2 roadmap)
-/rihal-plan Build search feature
-
-# Parallel workspace (critical bug)
-/rihal-new-workspace Critical Hotfix
-/rihal-plan Fix data corruption --workspace=Critical Hotfix
-
-# Both run independently
-# Query progress:
-/rihal-list-workspaces
-```
-
-## Decision Matrix
-
-| Scenario | Use | Why |
-|----------|-----|-----|
-| "Build feature A then feature B then feature C" | Sequential | Linear, dependent work |
-| "Build feature A AND debug production issue simultaneously" | Workspace | Parallel, independent |
-| "Phase 2 requires Phase 1 to be 100% done first" | Sequential | Depends-on relationship |
-| "Two teams working on unrelated features" | Workspace | No dependency, separate concerns |
-| "One-sprint roadmap with 5 tasks" | Sequential | Single focused initiative |
-| "Pause roadmap, fix urgent bug, resume roadmap" | Workspace | Context switch without losing state |
-| "Research + implementation of same feature" | Sequential | Both parts of one deliverable |
-| "Experiment in parallel with stable features" | Workspace | Risk isolation |
-
-## State Management
-
-### Sequential (default)
-
-- Single `.planning/STATE.md` — tracks all phases
-- Single `.planning/ROADMAP.md` — one set of goals
-- Phases inherit context from previous phases
-
-### Workspaces (parallel)
-
-- Each workspace has its own `STATE.md`
-- Each workspace has its own `ROADMAP.md`
-- No shared context between workspaces (intentional isolation)
-
-## Switching Context
-
-### Sequential phases
-
-```bash
-# View current phase
-/rihal-status
-
-# Execute next phase
-/rihal-execute <phase>
-
-# Switch to different task within same milestone
-/rihal-quick <small task>
-```
-
-### Workspaces
-
-```bash
-# List all workspaces
-/rihal-list-workspaces
-
-# Work within a workspace
-/rihal-plan <task> --workspace=Hotfix
-
-# Switch to another workspace's context
-/rihal-workstream switch --name <name>
-
-# Return to main planning
-/rihal-workstream switch --name main
-```
-
-## Merging Workspaces Back
-
-If you started a workspace but it should merge back into main planning:
-
-1. Complete the work in the workspace
-2. Create a phase in main planning that incorporates the workspace's findings
-3. Archive the workspace: `/rihal-remove-workspace <name> --archive`
-4. Continue in main planning with unified context
-
-## Common Patterns
-
-### Pattern: Feature branch + hotfix
-
-```bash
-# Main work (Q2 roadmap)
-/rihal-plan Implement real-time notifications
-
-# Critical bug emerges
-/rihal-new-workspace Critical
-/rihal-plan Fix payment processing --workspace=Critical
-
-# Two parallel tracks
-/rihal-list-workspaces
-
-# When bug is fixed
-/rihal-complete-workspace Critical
-# Resume main work
-/rihal-execute <Q2 phase>
-```
-
-### Pattern: Research + implementation
-
-```bash
-# Sequential phases (both parts of same feature)
-/rihal-plan Research WebSocket libraries and trade-offs
-/rihal-plan Implement chosen library with tests
-# Phase 2 reads Phase 1 findings
-```
-
-### Pattern: Experimental feature
-
-```bash
-# Keep experiments separate
-/rihal-new-workspace Experiment: Dark Mode
-/rihal-plan Build dark mode UI --workspace=Experiment
-/rihal-plan Test across 10 browsers --workspace=Experiment
-
-# Main work continues unaffected
-/rihal-plan Improve search relevance
-
-# If experiment succeeds, merge into main
-# If it fails, just archive and delete
-/rihal-remove-workspace --archive Experiment
-```
-
-## Summary
-
-- **Default (sequential):** Linear work, dependencies, single focus
-- **Workspaces (parallel):** Independent initiatives, context switching, risk isolation
-- Use sequential for 95% of work
-- Reach for workspaces when you truly have parallel, independent tracks

package/rihal/skills/SKILLS_INDEX.md

@@ -1,143 +0,0 @@
-# Rihal Code — Skills Index
-
-All 85 skills in Rihal Code, organized by category: 23 agent skills, 37 action skills, 25 core skills, plus 2 shared modules.
-
-## Agent Skills (23)
-
-Each agent has a persona, principles, and a capabilities table that lists which action skills it can invoke.
-
-| Rihal Name | Arabic | Role | Skill Path |
-|---|---|---|---|
-| **Waleed** | وليد | System Architect / CTO | `agents/waleed-architect/` |
-| **Sadiq** | صادق | Business Analyst / Strategy | `agents/sadiq-analyst/` |
-| **Hussain (PM)** | حسين | Product Manager | `agents/hussain-pm/` |
-| **Hussain (SM)** | حسين | Scrum Master | `agents/hussain-sm/` |
-| **Layla** | ليلى | UX Designer | `agents/layla-designer/` |
-| **Hanzla** | حنظلة | Senior Developer | `agents/hanzla-engineer/` |
-| **Fatima** | فاطمة | Test Architect (QA) | `agents/fatima-qa/` |
-| **Noor** | نور | Technical Writer | `agents/noor-writer/` |
-| **Ahmed Al Hassani** | أحمد الحسني | Technology & Development Director | `agents/ahmed-hassani-director/` |
-| **Haitham** | هيثم | Senior Frontend Engineer | `agents/haitham-frontend/` |
-| **Mariam** | مريم | Marketing Lead | `agents/mariam-marketing/` |
-| **Nasser** | ناصر | Engineering Manager | `agents/nasser-eng-manager/` |
-| **Yousef** | يوسف | Senior Backend Engineer | `agents/yousef-backend/` |
-| **Zahra** | زهرة | Branding & Creative Director | `agents/zahra-branding/` |
-| **Zayd** | زيد | Senior ML Engineer | `agents/zayd-ml/` |
-| **Raees** | رئيس | Orchestrator | `agents/raees-orchestrator/` |
-| **Majlis** | مجلس | Multi-Agent Council | `agents/majlis-council/` |
-| **Dalil** | دليل | Codebase Scout | `agents/dalil-scout/` |
-| **Cross-Platform Auditor** | — | Cross-Platform Auditor | `agents/rihal-cross-platform-auditor/` |
-| **Dep Auditor** | — | Dependency Health Auditor | `agents/rihal-dep-auditor/` |
-| **Deviation Analyzer** | — | Deviation Analyzer | `agents/rihal-deviation-analyzer/` |
-| **i18n Auditor** | — | i18n / L10n Auditor | `agents/rihal-i18n-auditor/` |
-| **Observability Auditor** | — | Observability Auditor | `agents/rihal-observability-auditor/` |
-
-Note: Hussain has two hats — **PM** (strategic product management) and **SM** (scrum master / sprint ops). Real teams often combine these.
-
----
-
-## Action Skills (37)
-
-Invoked by agents via the capabilities table in their SKILL.md. Organized by SDLC phase.
-
-### 1 — Analysis (6)
-- `actions/1-analysis/research/rihal-domain-research` — domain-specific research
-- `actions/1-analysis/research/rihal-market-research` — market and competitive research
-- `actions/1-analysis/research/rihal-technical-research` — technical deep-dive research
-- `actions/1-analysis/rihal-product-brief` — write product brief
-- `actions/1-analysis/rihal-prfaq` — Amazon Working Backwards PRFAQ challenge
-- `actions/1-analysis/rihal-document-project` — document an existing codebase (brownfield)
-
-### 2 — Planning (8)
-- `actions/2-plan/rihal-create-prd` — create product requirements doc
-- `actions/2-plan/rihal-edit-prd` — edit existing PRD
-- `actions/2-plan/rihal-validate-prd` — validate PRD completeness
-- `actions/2-plan/rihal-create-ux-design` — create UX design
-- `actions/2-plan/rihal-frontend-design` — typography, colours, motion, spatial design
-- `actions/2-plan/rihal-create-epics-and-stories` — break down PRD into epics and stories
-- `actions/2-plan/rihal-create-story` — prepare a dev-ready user story
-- `actions/2-plan/rihal-create-milestone` — create milestone definition
-
-### 3 — Solutioning (3)
-- `actions/3-solutioning/rihal-create-architecture` — architectural decision record (ADR)
-- `actions/3-solutioning/rihal-check-implementation-readiness` — verify PRD/UX/arch alignment
-- `actions/3-solutioning/rihal-generate-project-context` — generate project-context.md
-
-### 4 — Implementation (20)
-- `actions/4-implementation/rihal-dev-story` — execute a story (write tests + code)
-- `actions/4-implementation/rihal-code-review` — comprehensive code review
-- `actions/4-implementation/rihal-qa-generate-e2e-tests` — generate e2e test suite
-- `actions/4-implementation/rihal-sprint-planning` — plan a sprint
-- `actions/4-implementation/rihal-sprint-status` — sprint status report
-- `actions/4-implementation/rihal-retrospective` — retro workflow
-- `actions/4-implementation/rihal-correct-course` — course-correction for off-track stories
-- `actions/4-implementation/rihal-scaffold-project` — scaffold new project from Rihal template
-- `actions/4-implementation/rihal-checkpoint-preview` — LLM-assisted human-in-the-loop review
-- `actions/4-implementation/rihal-browser-verify` — verify browser behaviour via Chrome DevTools MCP
-- `actions/4-implementation/rihal-ci` — CI/CD setup and quality gates
-- `actions/4-implementation/rihal-debug` — root-cause debugging via the scientific method
-- `actions/4-implementation/rihal-git-flow` — branching, commits, conflicts, parallel work
-- `actions/4-implementation/rihal-harden` — security hardening checklist for SaaS apps
-- `actions/4-implementation/rihal-incremental` — ship code in small, atomic, verifiable steps
-- `actions/4-implementation/rihal-migrate` — move from MVP to production-grade infrastructure
-- `actions/4-implementation/rihal-perf` — performance optimisation (LCP / TBT / CLS / hydration)
-- `actions/4-implementation/rihal-prove-it` — test-first development
-- `actions/4-implementation/rihal-source-truth` — cite official docs before writing framework code
-- `actions/4-implementation/rihal-trim` — code simplification
-
----
-
-## Core Skills (25)
-
-Shared utilities used across agents and workflows.
-
-- `core/rihal-init` — INTERNAL config loader (installs to .rihal/skills/, not .claude/skills/)
-- `core/rihal-help` — meta-help on available skills
-- `core/rihal-brainstorming` — structured brainstorming workflow
-- `core/rihal-advanced-elicitation` — advanced requirements elicitation
-- `core/rihal-distillator` — distill information into concise summaries
-- `core/rihal-index-docs` — index documentation for search
-- `core/rihal-shard-doc` — shard large documents into linked sections
-- `core/rihal-clone-website` — reverse-engineer and clone a website
-- `core/rihal-editorial-review-prose` — editorial review for prose quality
-- `core/rihal-editorial-review-structure` — editorial review for structural quality
-- `core/rihal-review-adversarial-general` — adversarial review for robustness
-- `core/rihal-review-edge-case-hunter` — edge case hunting and boundary testing
-- `core/rihal-party-mode` — multi-agent collaboration mode
-- `core/rihal-auth-audit` — audit Keycloak ↔ AD sync, JWT validation, tenant isolation
-- `core/rihal-client-gate` — client requirement freeze gates and async-comm patterns
-- `core/rihal-deploy-unify` — detect and unify multiple deployment paths
-- `core/rihal-incident-record` — generate a change record + post-mortem
-- `core/rihal-memory-init` — bootstrap the Memory Bank for a project
-- `core/rihal-memory-update` — surgical update of specific Memory Bank files
-- `core/rihal-memory-audit` — audit the Memory Bank for stale entries and contradictions
-- `core/rihal-memory-distill` — regenerate token-optimised Memory Bank distillates
-- `core/rihal-mvp-graduate` — move an MVP to production-grade infrastructure incrementally
-- `core/rihal-ocr-consistency` — OCR pipeline determinism + ground-truth validation
-- `core/rihal-rebrand` — stack-wide rebranding migration
-- `core/rihal-theme-system` — audit a frontend's design tokens before launch
-
----
-
-## How Skills Work
-
-1. **Agent skills** give a persona and list capabilities
-2. **Action skills** are the actual capabilities that do work
-3. **Core skills** are shared utilities
-
-Agents reference actions by their skill name in their Capabilities table:
-
-```markdown
-| Code | Description | Skill |
-|------|-------------|-------|
-| DS | Write the next story's tests and code | rihal-dev-story |
-| CR | Comprehensive code review | rihal-code-review |
-```
-
-When a user picks capability `DS`, Claude invokes the `rihal-dev-story` skill.
-
----
-
-## Licensing
-
-Free to use and adapt.

package/rihal/skills/_shared/no-autonomous-bypass.md

@@ -1,37 +0,0 @@
-# No Autonomous-Mode Bypass
-
-This fragment is referenced by every step-file workflow that enforces halt-at-menu. Do not inline its contents into individual step files — reference this file so the rule stays single-sourced.
-
-## The Rule
-
-Step-file skills (`rihal-create-prd`, `rihal-sprint-planning`, `rihal-create-epics-and-stories`, etc.) halt at every menu and wait for user input. **This is invariant.** The agent MUST NOT invent an "autonomous mode", "research mode", or any other self-declared bypass that skips discovery questions.
-
-Phrases like *"just write it autonomously"*, *"create the full thing ready to execute"*, *"skip the questions"*, or *"use research mode"* from the user are **not** authorization to bypass halt. They are signals that the user wants the skill to move efficiently — answer by running the next step's questions compactly, not by skipping them.
-
-## The Only Sanctioned Bypass Paths
-
-There are exactly two ways to legitimately run a skill without halting at menus:
-
-1. **Project-wide:** `.rihal/config.yaml` → `mode: yolo`. The config loader flags `yoloMode=true` in the runtime context; step files check this flag and may auto-advance.
-2. **Per-invocation:** `/rihal-do --auto <question>` on the router. The router sets `autoMode=true` and passes it to the dispatched skill.
-
-If **neither** flag is set, halt is mandatory regardless of what the user's prompt text says.
-
-## Required Behavior When Asked to Bypass Without a Flag
-
-1. Acknowledge the user's intent in one sentence.
-2. Show the current step's menu anyway.
-3. Tell the user the two sanctioned paths (config flag or `--auto`) if they want fully hands-off execution.
-4. Do not generate any output artifact (PRD, sprint plan, roadmap, etc.) until the user either selects a menu option or sets one of the sanctioned flags.
-
-## Anti-Example (What NOT to Do)
-
-> User: *"use rihal research skills and create best PRD ready to execute"*
->
-> ❌ Agent: *"Switching to autonomous mode — researching the domain and drafting a complete execution-ready PRD."* *(then writes full PRD)*
-
-That response invents a mode that does not exist and violates the halt invariant.
-
-## Correct Response
-
-> ✅ Agent: *"I hear you want the PRD written end-to-end. The halt rule applies unless you set `mode: yolo` in `.rihal/config.yaml` or re-invoke via `/rihal-do --auto`. Here is the step-01 menu — pick Continue and I will drive each step concisely."*

package/rihal/skills/_shared/research-citation-rule.md

@@ -1,39 +0,0 @@
-# Research & Citation Rule
-
-Referenced by any step-file workflow that writes content derived from external sources (competitor pricing, API tiers, market sizing, benchmark numbers, vendor claims, etc.).
-
-## The Rule
-
-If an output artifact (PRD, research note, architecture doc, roadmap) contains a specific external claim — a price, a percentage, a named competitor feature, an API limit — then **every such claim must be traceable to a `WebFetch` (or equivalent document-fetch) call made in the same session**. `WebSearch` snippets alone are not sufficient evidence because snippets are paraphrased and may be stale.
-
-## What This Means in Practice
-
-Before writing a claim like *"Competitor X costs $12.50/mo"*:
-
-1. Run `WebFetch` on the source URL (not just `WebSearch` for a snippet).
-2. Quote the exact sentence from the fetched content in your internal reasoning.
-3. Include the URL in the citations block of the artifact.
-4. If the URL is paywalled, login-walled, or returns a different claim than expected, drop the number — do not paraphrase from memory or search-result previews.
-
-## The Trap to Avoid
-
-Observed failure pattern (rihal-code session, social-poster-x PRD generation):
-
-- Agent ran two `WebSearch` calls.
-- Agent wrote a PRD citing four specific URLs with specific dollar amounts.
-- Agent never ran `WebFetch` on any of the four URLs.
-- Numbers may be accurate-looking hallucinations.
-
-This pattern is forbidden. A citation block without `WebFetch` evidence is a lie to the reader.
-
-## If the User Is Running Autonomously
-
-`mode: yolo` and `/rihal-do --auto` bypass halt-at-menu, but they do **not** bypass this rule. A fully-autonomous run still has to fetch every cited URL before writing the claim.
-
-## Checklist Before Writing a Citation
-
-- [ ] `WebFetch` was called on this URL in this session.
-- [ ] The fetched content contains the specific number / claim being cited.
-- [ ] The claim in the artifact matches the fetched content verbatim (or is a clearly labeled summary).
-
-If any box is unchecked: remove the claim, replace with *"(needs source)"*, and flag to the user.

package/rihal/skills/_shared/state-sync-rule.md

@@ -1,43 +0,0 @@
-# State Sync Rule
-
-Referenced by skills that write `ROADMAP.md`, `epics.md`, or sprint artifacts. These artifacts are not authoritative on their own — downstream workflows (`/rihal-status`, `/rihal-progress`, `/rihal-execute`) read `.rihal/state.json`. If you write a planning artifact and skip state sync, the project ends up with two divergent pictures.
-
-## The Rule
-
-Immediately after appending content to any of:
-
-- `.planning/ROADMAP.md` — milestones and phases
-- `.planning/epics.md` — epics and stories
-- `.rihal/phases/{phase}/sprint-{N}.md` — sprint commitments
-
-Call the state-sync helper:
-
-```bash
-node .rihal/bin/rihal-tools.cjs state sync --from-disk
-```
-
-or, for a more targeted write, use the JSON-API helpers exposed by `rihal-tools.cjs`:
-
-```bash
-node .rihal/bin/rihal-tools.cjs state upsert-milestone <json>
-node .rihal/bin/rihal-tools.cjs state upsert-phase <json>
-node .rihal/bin/rihal-tools.cjs state upsert-epic <json>
-```
-
-If `rihal-tools.cjs` does not yet expose the needed subcommand, fall back to `state sync --from-disk` which re-parses `ROADMAP.md` + `epics.md` and rebuilds the relevant sections of `state.json`.
-
-## Verification After Sync
-
-- `node .rihal/bin/rihal-tools.cjs state read` returns a phase count that matches the phase table in `ROADMAP.md`.
-- `/rihal-status` and `/rihal-progress`, run back-to-back, agree on the current milestone name and phase count.
-
-## Why This Matters
-
-Observed failure (rihal-code, social-poster-x install, Apr 2026):
-
-- User ran `/rihal-create-epics-and-stories`.
-- `ROADMAP.md` gained 10 phases; `epics.md` gained 62 stories.
-- `.rihal/state.json` remained at the initial bootstrap with 1 phase.
-- `/rihal-status` showed 1 phase; `/rihal-progress` showed 10.
-
-That divergence is what this rule exists to prevent.

package/rihal/skills/actions/1-analysis/research/rihal-domain-research/SKILL.md

@@ -1,46 +0,0 @@
----
-name: rihal-domain-research
-internal: true
-description: >
-  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 rihal-market-research) or technical feasibility (use
-  rihal-technical-research).
-triggers:
-  - "research this domain"
-  - "domain deep dive"
-  - "explain this industry"
-  - "help
-  me understand X industry"
-  - "domain research for"
-user-invocable: true
----
-@.rihal/references/karpathy-guidelines.md
-
-
-## Overview
-
-Conduct industry domain deep-dive research to build subject matter expertise on a specific business domain.
-
-## Workflow
-
-Follow the instructions in ./workflow.md.
-
-## Output Format
-
-- Report: Domain Overview | Key Players | Terminology Glossary | Common Workflows | Regulatory Notes | References
-- Every claim cited with a source URL or flagged as assumption
-- Saved to .rihal/artifacts/research/domain-{slug}.md
-- Do NOT include unsourced statistics
-
-## Examples
-
-### Happy Path
-**Input:** "Research the real estate brokerage domain in Oman"
-**Expected behavior:** Multi-source research, produce report with glossary of Omani real estate terms, regulatory citations, and key players.
-
-### Edge Case: Narrow Domain
-**Input:** "Research quantum basket weaving"
-**Expected behavior:** Report: "Insufficient verifiable sources. Can narrow or pivot to adjacent domain?"

package/rihal/skills/actions/1-analysis/research/rihal-domain-research/workflow.md

@@ -1,49 +0,0 @@
-# Domain Research Workflow
-
-**Goal:** Conduct comprehensive domain/industry research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.
-
-**Your Role:** You are a domain research facilitator working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.
-
-## PREREQUISITE
-
-**⛔ Web search required.** If unavailable, abort and tell the user.
-
-## CONFIGURATION
-
-Load config from `{project-root}/.rihal/config.json` and resolve:
-- `project_name`, `output_folder`, `planning_artifacts`, `user_name`
-- `communication_language`, `document_output_language`, `user_skill_level`
-- `date` as a system-generated value
-
-## QUICK TOPIC DISCOVERY
-
-"Welcome {{user_name}}! Let's get started with your **domain/industry research**.
-
-**What domain, industry, or sector do you want to research?**
-
-For example:
-- 'The healthcare technology industry'
-- 'Sustainable packaging regulations in Europe'
-- 'Construction and building materials sector'
-- 'Or any other domain you have in mind...'"
-
-### Topic Clarification
-
-Based on the user's topic, briefly clarify:
-1. **Core Domain**: "What specific aspect of [domain] are you most interested in?"
-2. **Research Goals**: "What do you hope to achieve with this research?"
-3. **Scope**: "Should we focus broadly or dive deep into specific aspects?"
-
-## ROUTE TO DOMAIN RESEARCH STEPS
-
-After gathering the topic and goals:
-
-1. Set `research_type = "domain"`
-2. Set `research_topic = [discovered topic from discussion]`
-3. Set `research_goals = [discovered goals from discussion]`
-4. Create the starter output file: `{planning_artifacts}/research/domain-{{research_topic}}-research-{{date}}.md` with exact copy of the `./research.template.md` contents
-5. Load: `./domain-steps/step-01-init.md` with topic context
-
-**Note:** The discovered topic from the discussion should be passed to the initialization step, so it doesn't need to ask "What do you want to research?" again - it can focus on refining the scope for domain research.
-
-**✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`**

package/rihal/skills/actions/1-analysis/research/rihal-market-research/SKILL.md

@@ -1,45 +0,0 @@
----
-name: rihal-market-research
-internal: true
-description: >
-  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 rihal-domain-research) or technical feasibility.
-triggers:
-  - "market research"
-  - "competitive analysis"
-  - "market analysis for"
-  - "size the market"
-  - "competitor scan"
-  - "analyze the market for X"
-user-invocable: true
----
-@.rihal/references/karpathy-guidelines.md
-
-
-## Overview
-
-Analyze market size, competitive landscape, customer needs, and trends for a product or industry.
-
-## Workflow
-
-Follow the instructions in ./workflow.md.
-
-## Output Format
-
-- Report: TAM/SAM/SOM (with sources) | Direct Competitors (3-5) | Indirect Alternatives | Customer Segments | Trends | Recommendation
-- Every number cites a source
-- Saved to .rihal/artifacts/research/market-{slug}.md
-- Do NOT invent market sizes
-
-## Examples
-
-### Happy Path
-**Input:** "Market research for AI legal assistants in the GCC"
-**Expected behavior:** Source-backed TAM/SAM/SOM, competitor scan, segment analysis, recommendation.
-
-### Edge Case: Niche Market
-**Input:** (tiny addressable market)
-**Expected behavior:** Report honestly: "SAM is ~$X — may be too small for VC-scale investment. Consider adjacency or pivot."

package/rihal/skills/actions/1-analysis/research/rihal-market-research/workflow.md

@@ -1,49 +0,0 @@
-# Market Research Workflow
-
-**Goal:** Conduct comprehensive market research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.
-
-**Your Role:** You are a market research facilitator working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.
-
-## PREREQUISITE
-
-**⛔ Web search required.** If unavailable, abort and tell the user.
-
-## CONFIGURATION
-
-Load config from `{project-root}/.rihal/config.json` and resolve:
-- `project_name`, `output_folder`, `planning_artifacts`, `user_name`
-- `communication_language`, `document_output_language`, `user_skill_level`
-- `date` as a system-generated value
-
-## QUICK TOPIC DISCOVERY
-
-"Welcome {{user_name}}! Let's get started with your **market research**.
-
-**What topic, problem, or area do you want to research?**
-
-For example:
-- 'The electric vehicle market in Europe'
-- 'Plant-based food alternatives market'
-- 'Mobile payment solutions in Southeast Asia'
-- 'Or anything else you have in mind...'"
-
-### Topic Clarification
-
-Based on the user's topic, briefly clarify:
-1. **Core Topic**: "What exactly about [topic] are you most interested in?"
-2. **Research Goals**: "What do you hope to achieve with this research?"
-3. **Scope**: "Should we focus broadly or dive deep into specific aspects?"
-
-## ROUTE TO MARKET RESEARCH STEPS
-
-After gathering the topic and goals:
-
-1. Set `research_type = "market"`
-2. Set `research_topic = [discovered topic from discussion]`
-3. Set `research_goals = [discovered goals from discussion]`
-4. Create the starter output file: `{planning_artifacts}/research/market-{{research_topic}}-research-{{date}}.md` with exact copy of the `./research.template.md` contents
-5. Load: `./steps/step-01-init.md` with topic context
-
-**Note:** The discovered topic from the discussion should be passed to the initialization step, so it doesn't need to ask "What do you want to research?" again - it can focus on refining the scope for market research.
-
-**✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`**

package/rihal/skills/actions/1-analysis/research/rihal-technical-research/SKILL.md

@@ -1,48 +0,0 @@
----
-name: rihal-technical-research
-internal: true
-description: >
-  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
-  rihal-create-architecture) or market analysis.
-triggers:
-  - "technical research"
-  - "feasibility study"
-  - "research implementation
-  options"
-  - "how would we build X"
-  - "what stack for"
-  - "technical
-  feasibility for"
-user-invocable: true
----
-@.rihal/references/karpathy-guidelines.md
-
-
-## Overview
-
-Research technical feasibility, architecture options, and implementation approaches for a proposed product or feature.
-
-## Workflow
-
-Follow the instructions in ./workflow.md.
-
-## Output Format
-
-- Report: Problem Framing | Approach Options (3+) | Trade-off Table | Recommended Approach | Risks | Next Steps
-- Each approach is feasible and buildable with known tech
-- Do NOT propose speculative tech without disclaimer
-- Saved to .rihal/artifacts/research/technical-{slug}.md
-
-## Examples
-
-### Happy Path
-**Input:** "Technical research: how to build real-time collaboration like Figma"
-**Expected behavior:** Compare CRDTs vs OT vs event sourcing, trade-off table, recommended approach with risks.
-
-### Edge Case: Speculative Request
-**Input:** "Research how to build AGI"
-**Expected behavior:** Decline speculative. "This is a research problem, not a technical feasibility. I can research narrower applications of current AI tech instead."