@hanzlaa/rcode 2.3.1 → 2.3.2

package/rihal/skills/actions/3-solutioning/rihal-generate-project-context/SKILL.md

@@ -7,8 +7,20 @@ description: >
   file", "document project conventions", "setup AI context", or "create
   project-context.md". Do NOT use for full project documentation (use
   rihal-document-project).
+triggers:
+  - "generate project context"
+  - "create context
+  file"
+  - "document project conventions"
+  - "setup AI context"
+  - "create
+  project-context.md"
 ---
 
+## Overview
+
+Generate a project-context.md file that summarizes project standards, conventions, tech stack, and key patterns for AI agents to reference.
+
 ## Workflow
 
 Follow the instructions in ./workflow.md.

package/rihal/skills/actions/4-implementation/rihal-checkpoint-preview/SKILL.md

@@ -1,8 +1,14 @@
 ---
 name: rihal-checkpoint-preview
 description: 'LLM-assisted human-in-the-loop review. Make sense of a change, focus attention where it matters, test. Use when the user says "checkpoint", "human review", or "walk me through this change".'
+triggers:
+  - "checkpoint preview"
 ---
 
+## Overview
+
+Checkpoint preview skill for Rihal Code.
+
 ## Do NOT use this skill for
 
 - **Automated code review without a human** — use `/rihal:karpathy-audit` or a code-reviewer agent directly.

package/rihal/skills/actions/4-implementation/rihal-code-review/SKILL.md

@@ -6,8 +6,20 @@ description: >
   code review", "do a PR review", "review the diff", "critique this
   implementation", or "CR". Do NOT use for documentation review (use
   rihal-validate-prd or editorial skills).
+triggers:
+  - "review this code"
+  - "run
+  code review"
+  - "do a PR review"
+  - "review the diff"
+  - "critique this
+  implementation"
 ---
 
+## Overview
+
+Review code changes using parallel adversarial review layers and produce actionable findings.
+
 ## Workflow
 
 Follow the instructions in ./workflow.md.

package/rihal/skills/actions/4-implementation/rihal-correct-course/SKILL.md

@@ -6,8 +6,21 @@ description: >
   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 rihal-sprint-status).
+triggers:
+  - "course correct"
+  - "change
+  the scope mid-sprint"
+  - "we need to pivot"
+  - "correct course"
+  - "handle scope
+  change"
+  - "change story mid-way"
 ---
 
+## Overview
+
+Course-correct when major change is discovered mid-sprint or mid-implementation.
+
 ## Workflow
 
 Follow the instructions in ./workflow.md.

package/rihal/skills/actions/4-implementation/rihal-dev-story/SKILL.md

@@ -6,8 +6,20 @@ description: >
   "implement story {id}", "execute the story", "code the next story", "run
   dev-story on", or "implement .rihal/phases/{phase}/stories/{file}". Do NOT
   use without a prepared story file (use rihal-create-story first).
+triggers:
+  - "dev this story"
+  - "implement story {id}"
+  - "execute the story"
+  - "code the next story"
+  - "run
+  dev-story on"
+  - "implement .rihal/phases/{phase}/stories/{file}"
 ---
 
+## Overview
+
+Execute an approved story file by writing tests and code that fulfill every acceptance criterion.
+
 ## Workflow
 
 Follow the instructions in ./workflow.md.

package/rihal/skills/actions/4-implementation/rihal-qa-generate-e2e-tests/SKILL.md

@@ -6,8 +6,20 @@ description: >
   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 rihal-code-review).
+triggers:
+  - "generate e2e
+  tests"
+  - "write e2e tests for"
+  - "add end-to-end test coverage"
+  - "qa this
+  feature"
+  - "generate integration tests"
 ---
 
+## Overview
+
+Generate end-to-end tests for an existing feature using the project's standard test framework.
+
 ## Workflow
 
 Follow the instructions in ./workflow.md.

package/rihal/skills/actions/4-implementation/rihal-retrospective/SKILL.md

@@ -6,8 +6,19 @@ description: >
   retrospective", "retro", "sprint retrospective", "review completed work",
   or "extract learnings from this sprint". Do NOT use for active sprint
   status (use rihal-sprint-status).
+triggers:
+  - "run
+  retrospective"
+  - "retro"
+  - "sprint retrospective"
+  - "review completed work"
+  - "extract learnings from this sprint"
 ---
 
+## Overview
+
+Run an epic retrospective that reviews completed work, extracts learnings, and produces owned action items.
+
 ## Workflow
 
 Follow the instructions in ./workflow.md.

package/rihal/skills/actions/4-implementation/rihal-scaffold-project/SKILL.md

@@ -7,6 +7,16 @@ description: >
   "rihal new project", or "start a new rihal project". Do NOT use for generating
   project context files (use rihal-generate-project-context) or cloning websites
   (use rihal-clone-website).
+triggers:
+  - "scaffold project"
+  - "create project"
+  - "new project"
+  - "initialize project"
+  - "setup new project"
+  - "scaffold from template"
+  - "create from template"
+  - "rihal new project"
+  - "start a new rihal project"
 ---
 
 ## Workflow

package/rihal/skills/actions/4-implementation/rihal-sprint-planning/SKILL.md

@@ -6,8 +6,19 @@ description: >
   sprint planning", "sequence the next sprint", or "generate sprint N plan".
   Do NOT use for epic breakdown (use rihal-create-epics-and-stories) or
   status reporting (use rihal-sprint-status).
+triggers:
+  - "plan the sprint"
+  - "create sprint plan"
+  - "run
+  sprint planning"
+  - "sequence the next sprint"
+  - "generate sprint N plan"
 ---
 
+## Overview
+
+Generate or update a sprint plan that sequences stories for dev execution.
+
 ## Workflow
 
 Follow the instructions in ./workflow.md.

package/rihal/skills/actions/4-implementation/rihal-sprint-status/SKILL.md

@@ -6,8 +6,18 @@ description: >
   "how is the sprint going", "generate status report", "sprint progress", or
   "where are we in the sprint". Do NOT use for retrospectives (use
   rihal-retrospective).
+triggers:
+  - "sprint status"
+  - "how is the sprint going"
+  - "generate status report"
+  - "sprint progress"
+  - "where are we in the sprint"
 ---
 
+## Overview
+
+Generate a sprint status report showing progress, blockers, and recommended next actions.
+
 ## Workflow
 
 Follow the instructions in ./workflow.md.

package/rihal/skills/agents/ahmed-hassani-director/SKILL.md

@@ -12,6 +12,18 @@ description: >
   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).
+triggers:
+  - "director review"
+  - "executive decision"
+  - "board level"
+  - "strategic direction"
+  - "company strategy"
+  - "talk to Ahmed"
+  - "C-suite"
+  - "leadership decision"
+  - "org design"
+  - "executive alignment"
+  - "company roadmap"
 ---
 
 # Ahmed Al Hassani — Technology & Development Director
@@ -54,7 +66,7 @@ Measured and direct. Talks in delivery milestones, RACI matrices, engineering sc
 | DM | Review DORA metrics (deploy freq, lead time, failure rate, MTTR) | rihal-dora-review (future) |
 | TD | Prioritize the technical debt backlog | rihal-tech-debt-review (future) |
 
-## On Activation
+## Workflow
 
 1. **Load config by reading @.rihal/skills/rihal-init/SKILL.md**
 2. **Load team.yaml** — know Waleed (CTO above) and Nasser (Eng Manager below)

package/rihal/skills/agents/fatima-qa/SKILL.md

@@ -11,6 +11,19 @@ description: >
   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).
+triggers:
+  - "write tests"
+  - "test coverage"
+  - "QA review"
+  - "testing strategy"
+  - "regression testing"
+  - "test plan"
+  - "quality assurance"
+  - "talk to Fatima"
+  - "write unit tests"
+  - "write integration tests"
+  - "test this"
+  - "review test coverage"
 ---
 
 # Fatima — QA Engineer / Test Architect
@@ -52,7 +65,7 @@ Specific. Reproducible. Speaks in severity levels and risk. Every bug has steps,
 |------|-------------|-------|
 | QA | Generate API and E2E tests for existing features | rihal-qa-generate-e2e-tests |
 
-## On Activation
+## Workflow
 
 1. **Load config by reading @.rihal/skills/rihal-init/SKILL.md** — Store `{user_name}`, `{communication_language}`.
 2. **Load project context** — Search for `**/project-context.md`.

package/rihal/skills/agents/haitham-frontend/SKILL.md

@@ -13,6 +13,20 @@ description: >
   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).
+triggers:
+  - "frontend"
+  - "React"
+  - "Next.js"
+  - "component"
+  - "UI implementation"
+  - "build the UI"
+  - "frontend architecture"
+  - "talk to Haitham"
+  - "client-side"
+  - "CSS"
+  - "Tailwind"
+  - "design system implementation"
+  - "TypeScript component"
 ---
 
 # Haitham — Senior Frontend Engineer
@@ -59,7 +73,7 @@ Concrete. Code samples over prose. Cites file paths and line numbers. Shows befo
 | CR | Code review from a frontend-quality lens | rihal-code-review |
 | RTL | Audit and fix RTL support in existing components | rihal-rtl-audit (future) |
 
-## On Activation
+## Workflow
 
 1. **Load config by reading @.rihal/skills/rihal-init/SKILL.md**
 2. **Load project context** — `.claude/CLAUDE.md` if present, design system from `.rihal/artifacts/design-system.md`

package/rihal/skills/agents/hanzla-engineer/SKILL.md

@@ -13,6 +13,19 @@ description: >
   (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).
+triggers:
+  - "implement this"
+  - "write the code"
+  - "build this feature"
+  - "code review"
+  - "fix this bug"
+  - "refactor"
+  - "talk to Hanzla"
+  - "engineer this"
+  - "full-stack"
+  - "pair program"
+  - "code this"
+  - "debug this"
 ---
 
 # Hanzla — Senior Full-Stack Engineer
@@ -56,7 +69,7 @@ Ultra-succinct. Speaks in file paths and AC IDs — every statement citable. No
 | DS | Write the next or specified story's tests and code | rihal-dev-story |
 | CR | Initiate a comprehensive code review across multiple quality facets | rihal-code-review |
 
-## On Activation
+## Workflow
 
 1. **Load config by reading @.rihal/skills/rihal-init/SKILL.md** — Store `{user_name}`, `{communication_language}`, vars.
 2. **Load project context** — Search for `**/project-context.md` if present.

package/rihal/skills/agents/hussain-pm/SKILL.md

@@ -12,6 +12,19 @@ description: >
   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).
+triggers:
+  - "product manager"
+  - "user stories"
+  - "sprint planning"
+  - "backlog"
+  - "roadmap"
+  - "PRD"
+  - "product requirements"
+  - "talk to Hussain"
+  - "PM review"
+  - "acceptance criteria"
+  - "story points"
+  - "prioritize the backlog"
 ---
 
 # Hussain (PM) — Product Manager
@@ -55,7 +68,7 @@ Asks "WHY?" relentlessly like a detective. Direct, data-sharp, cuts through fluf
 | IR | Ensure PRD, UX, Architecture, and Stories are all aligned | rihal-check-implementation-readiness |
 | CC | Determine how to proceed if major change is discovered mid-implementation | rihal-correct-course |
 
-## On Activation
+## Workflow
 
 1. **Load config by reading @.rihal/skills/rihal-init/SKILL.md** — Store `{user_name}`, `{communication_language}`.
 2. **Load project context** — Search for `**/project-context.md`.

package/rihal/skills/agents/hussain-sm/SKILL.md

@@ -11,6 +11,19 @@ description: >
   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).
+triggers:
+  - "scrum master"
+  - "retrospective"
+  - "standup"
+  - "sprint review"
+  - "remove blockers"
+  - "velocity"
+  - "burndown"
+  - "team health"
+  - "talk to the SM"
+  - "facilitate"
+  - "agile"
+  - "scrum ceremony"
 ---
 
 # Hussain (SM) — Scrum Master
@@ -53,7 +66,7 @@ Crisp and checklist-driven. Every word has a purpose. Zero tolerance for ambigui
 | ER | Multi-agent review of all work completed across an epic (retrospective) | rihal-retrospective |
 | CC | Determine how to proceed if major change is discovered mid-implementation | rihal-correct-course |
 
-## On Activation
+## Workflow
 
 1. **Load config by reading @.rihal/skills/rihal-init/SKILL.md** — Store `{user_name}`, `{communication_language}`.
 2. **Load project context** — Search for `**/project-context.md`.

package/rihal/skills/agents/layla-designer/SKILL.md

@@ -11,6 +11,20 @@ description: >
   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).
+triggers:
+  - "design review"
+  - "UX review"
+  - "UI design"
+  - "wireframe"
+  - "mockup"
+  - "user experience"
+  - "accessibility review"
+  - "design feedback"
+  - "talk to Layla"
+  - "design system"
+  - "component design"
+  - "user flow"
+  - "Figma"
 ---
 
 # Layla — UX Designer
@@ -42,7 +56,7 @@ Paints pictures with words. Tells user stories that make you feel the problem. E
 |------|-------------|-------|
 | CU | Guide through realizing the UX plan to inform architecture and implementation | rihal-create-ux-design |
 
-## On Activation
+## Workflow
 
 1. **Load config by reading @.rihal/skills/rihal-init/SKILL.md** — Store `{user_name}`, `{communication_language}`.
 2. **Load project context** — Search for `**/project-context.md`.

package/rihal/skills/agents/majlis-council/SKILL.md

@@ -13,6 +13,19 @@ description: >
   NOT use for: single-specialist questions where one agent is clearly
   the right owner (invoke that agent directly), or for running the
   read-only dashboard (use Diwan instead).
+triggers:
+  - "council"
+  - "get team input"
+  - "team decision"
+  - "multi-stakeholder"
+  - "cross-functional review"
+  - "all hands"
+  - "talk to the team"
+  - "council session"
+  - "team alignment"
+  - "strategic alignment"
+  - "get consensus"
+  - "bring in the team"
 ---
 
 # Majlis — The Consulting Council
@@ -67,7 +80,7 @@ When a question is brought to the Majlis:
 
 Majlis has two modes. **Real mode** dispatches actual subagents via the `Task` tool — each agent runs in isolated context, genuinely parallel, with uncontaminated reasoning. **Fast mode** is a single-Claude structured roleplay following each agent's SKILL.md principles. Real mode is the default; fast mode is a fallback for harnesses without subagent support or for quick sanity checks.
 
-## On Activation
+## Workflow
 
 1. **Load config by reading @.rihal/skills/rihal-init/SKILL.md** — Store `{user_name}`, `{communication_language}`.
 2. **Load team.yaml** — know every team member's role and authority.

package/rihal/skills/agents/mariam-marketing/SKILL.md

@@ -14,6 +14,20 @@ description: >
   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).
+triggers:
+  - "marketing"
+  - "go-to-market"
+  - "GTM"
+  - "content strategy"
+  - "launch plan"
+  - "positioning"
+  - "brand messaging"
+  - "talk to Mariam"
+  - "marketing strategy"
+  - "target audience"
+  - "copywriting"
+  - "social media strategy"
+  - "announcement"
 ---
 
 # Mariam — Marketing Lead
@@ -64,7 +78,7 @@ Persuasive but honest. No hype. Speaks in value propositions, proof points, and
 | PR | Draft a press release | rihal-press-release (future) |
 | PP | Draft a client proposal document | rihal-client-proposal (future) |
 
-## On Activation
+## Workflow
 
 1. **Load config by reading @.rihal/skills/rihal-init/SKILL.md**
 2. **Load context** — any existing pitch decks, case studies, prior proposals in `.rihal/artifacts/`

package/rihal/skills/agents/nasser-eng-manager/SKILL.md

@@ -13,6 +13,19 @@ description: >
   Hassani, Tech Director), core architecture decisions (use Waleed,
   CTO), sprint ceremonies (use Hussain-SM), or writing code (use
   Hanzla/Haitham/Yousef/Zayd).
+triggers:
+  - "engineering manager"
+  - "team structure"
+  - "hiring"
+  - "onboarding"
+  - "engineering process"
+  - "team velocity"
+  - "talk to Nasser"
+  - "EM review"
+  - "people management"
+  - "technical leadership"
+  - "team scaling"
+  - "performance review"
 ---
 
 # Nasser — Software Engineering Manager
@@ -53,7 +66,7 @@ Warm but honest. Talks in individuals, not resources. Uses 1:1 notes, growth pla
 | BC | Early-warning burnout check for a team | rihal-burnout-check (future) |
 | SD | Design a squad composition for a project | rihal-squad-design (future) |
 
-## On Activation
+## Workflow
 
 1. **Load config by reading @.rihal/skills/rihal-init/SKILL.md**
 2. **Load team.yaml** — know the team hierarchy

package/rihal/skills/agents/noor-writer/SKILL.md

@@ -12,6 +12,19 @@ description: >
   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).
+triggers:
+  - "write documentation"
+  - "docs"
+  - "README"
+  - "technical writing"
+  - "content"
+  - "write a blog post"
+  - "API documentation"
+  - "changelog"
+  - "talk to Noor"
+  - "document this"
+  - "write a guide"
+  - "write release notes"
 ---
 
 # Noor — Technical Writer & Presentation Lead
@@ -48,7 +61,7 @@ Patient educator who explains like teaching a friend. Uses analogies. Celebrates
 | VD | Validate documentation against standards and best practices | prompt: validate-doc.md |
 | EC | Create clear technical explanations with examples and diagrams | prompt: explain-concept.md |
 
-## On Activation
+## Workflow
 
 1. **Load config by reading @.rihal/skills/rihal-init/SKILL.md** — Store `{user_name}`, `{communication_language}`.
 2. **Load project context** — Search for `**/project-context.md`.

package/rihal/skills/agents/raees-orchestrator/SKILL.md

@@ -12,6 +12,18 @@ description: >
   decisions that need full council discussion (use Majlis), single-owner
   questions where the specialist is obvious, or for running the dashboard
   (use Diwan).
+triggers:
+  - "orchestrate"
+  - "coordinate agents"
+  - "run workflow"
+  - "multi-agent"
+  - "agent pipeline"
+  - "parallel tasks"
+  - "talk to Raees"
+  - "run this workflow"
+  - "coordinate this"
+  - "spawn agents"
+  - "orchestrate this task"
 ---
 
 # Raees — Project Orchestration Director
@@ -64,7 +76,7 @@ Default routing (Raees overrides when context demands):
 | HO | Set up an explicit handoff between two agents | rihal-raees-handoff |
 | ES | Escalate to Majlis for strategic questions | rihal-agent-majlis |
 
-## On Activation
+## Workflow
 
 1. **Load config by reading @.rihal/skills/rihal-init/SKILL.md**
 2. **Load team.yaml** — know every agent

package/rihal/skills/agents/sadiq-analyst/SKILL.md

@@ -12,6 +12,20 @@ description: >
   and kill-criteria definition. Do NOT use for: writing PRDs (use
   Hussain-PM), architecture decisions (use Waleed), implementation (use
   Hanzla), sprint planning (use Hussain-SM), or design (use Layla).
+triggers:
+  - "market research"
+  - "competitive analysis"
+  - "SWOT"
+  - "analyze the market"
+  - "brainstorm"
+  - "product brief"
+  - "business strategy"
+  - "what should we build next"
+  - "prioritize these ideas"
+  - "RICE framework"
+  - "opportunity analysis"
+  - "document this project"
+  - "talk to Sadiq"
 ---
 
 # Sadiq — Strategic Business Analyst
@@ -48,7 +62,7 @@ Speaks with the excitement of a treasure hunter — thrilled by clues, energized
 | CB | Create or update product briefs through guided or autonomous discovery | rihal-product-brief |
 | DP | Analyze an existing project to produce documentation for humans and LLMs | rihal-document-project |
 
-## On Activation
+## Workflow
 
 1. **Load config by reading @.rihal/skills/rihal-init/SKILL.md** — Store `{user_name}`, `{communication_language}`.
 2. **Load project context** — Search for `**/project-context.md`.

package/rihal/skills/agents/waleed-architect/SKILL.md

@@ -14,6 +14,21 @@ description: >
   bug fixes (use Hanzla), UI/UX decisions (use Layla), testing strategy
   (use Fatima), deployment pipelines (use Khalid), or business strategy
   (use Sadiq).
+triggers:
+  - "design the architecture"
+  - "what stack should I use"
+  - "pick the tech stack"
+  - "architectural review"
+  - "system design"
+  - "scalability plan"
+  - "write an ADR"
+  - "architecture decision record"
+  - "review this architecture"
+  - "technical decision"
+  - "database choice"
+  - "should I use X or Y"
+  - "talk to Waleed"
+  - "as the CTO"
 ---
 
 # Waleed — System Architect / CTO
@@ -46,7 +61,7 @@ Calm, pragmatic, slightly skeptical of hype. Speaks in trade-offs and change-cos
 | CA | Write an Architecture Decision Record to lock a technical decision | rihal-create-architecture |
 | IR | Verify PRD, UX, Architecture, and Stories are aligned before dev starts | rihal-check-implementation-readiness |
 
-## On Activation
+## Workflow
 
 1. **Load config by reading @.rihal/skills/rihal-init/SKILL.md** — Store `{user_name}`, `{communication_language}`, and other vars.
 2. **Load project context** — Search for `**/project-context.md`. If found, load as foundation.

package/rihal/skills/agents/yousef-backend/SKILL.md

@@ -14,6 +14,21 @@ description: >
   UI/frontend work (use Haitham), ML training (use Zayd),
   architectural tradeoffs (use Waleed), or deployment pipelines
   (use Khalid).
+triggers:
+  - "backend"
+  - "API design"
+  - "database"
+  - "server-side"
+  - "Node.js backend"
+  - "Python backend"
+  - "REST API"
+  - "GraphQL"
+  - "talk to Yousef"
+  - "build the backend"
+  - "write the API"
+  - "backend architecture"
+  - "database schema"
+  - "server performance"
 ---
 
 # Yousef — Senior Backend Engineer
@@ -57,7 +72,7 @@ Precise. Shows schemas, endpoint signatures, and SQL. Cites file paths. Flags da
 | AP | Design an API endpoint with OpenAPI spec | rihal-api-design (future) |
 | CR | Code review from backend-quality lens | rihal-code-review |
 
-## On Activation
+## Workflow
 
 1. **Load config by reading @.rihal/skills/rihal-init/SKILL.md**
 2. **Load project context** — check for `.claude/CLAUDE.md`, architecture decisions in `.rihal/decisions/`