FarzamMohammadi
UserThe orchestration layer that turns Claude Code, OpenCode, and other AI coding CLIs into autonomous engineers — driving real work from task intake to merged pull request, with humans in the loop only where it counts. Swappable plugins for any trigger, chat, agent, or git host.
Categories
Indexed Skills (13)
create-plan
Synthesizes requirements and research into robust implementation plans through structured decision-making and expert panel stress-testing. Calibrates process depth to risk level — low stakes get a light plan, full stakes get hard decision gates and a pre-mortem. The plan is a decision record with actionable tasks, not an execution script. Use when you need to turn accumulated findings into a plan with clear choices, sequenced tasks, and verification. Also use when the user says "plan this", "create a plan", "how should we implement this", "design the approach", or "what's the strategy".
investigate-project
Perform end-to-end investigation, analysis, and comparative review of an external open-source project against The Engineer. Use this skill whenever the user wants to analyze, investigate, review, or compare an external project, GitHub repository, or open-source tool. Also trigger when the user mentions adding to considered-projects, doing a competitive analysis, or evaluating whether a project has ideas worth adopting. Takes a GitHub URL as input.
requirements-gathering
Conducts structured requirements gathering through sequential questioning before any research, planning, or implementation begins. Extracts true intent, constraints, edge cases, unknowns, and acceptance criteria from the user through focused one-at-a-time questions. Use this skill whenever the user mentions a new feature, task, ticket, bug fix, or any work item that hasn't been fully scoped yet. Also use when the user says "let's start", "new task", "I need to build", "requirements", "scope this", or "grill me" — even if they jump straight to implementation, redirect to requirements first.
research
Investigates codebases with a facts-before-opinions discipline — building a complete factual picture before interpreting what it means for the work ahead. Produces a structured research document saved to disk, split into observations and implications. Use when you need to understand existing code, patterns, dependencies, and constraints. Also use when the user says "research this", "explore the codebase", "investigate", "what does this code do", or "understand the system".
review
Conducts post-implementation review covering test coverage, lint, type checks, test fixes, and local testing preparation. Runs all automated verification, identifies gaps, fixes issues, and presents a testing checklist so the user can verify the work manually. Use this skill after implementation and commits are done — as the final quality gate before creating an MR. Also use when the user says "review this", "check my work", "run the checks", "verify everything", "is this ready", or "final review". Pairs with /commit (before) and /glab-mr-manager (after).
wrap-session
Wrap up the current session by updating active.md, logging the session, committing, and providing the next session's starter prompt. Use at the end of every working session.
commit
Analyze code changes, group them into logical packages where appropriate, to create sequential, clear, descriptive commits with effective titles and detailed descriptions
expert-panel-review
Run code, architecture, systems, or proposed changes through a panel of world-class engineering perspectives. Each panelist reads the ACTUAL source files before judging. Use this skill whenever the user asks to: review code quality, get expert opinions, assess architecture decisions, evaluate a refactor plan, critique a design, run something 'through expert eyes', get a 'Linus review', assess quality against the best projects, compare to top OSS standards, or get unbiased multi-perspective feedback. Also trigger for: 'what would X think of this', 'is this good enough', 'how does this compare to the best', 'give me honest feedback', 'tear this apart', 'brutal review', 'no-bullshit assessment'. This is for EVALUATING existing code or proposals — not for writing new code or extracting system structure (use system-layer-extraction for that).
system-layer-extraction
Deep architectural investigation that extracts, documents, and maps every system in a codebase. Use this skill whenever the user asks to: extract layers, map systems, analyze architecture, investigate codebase structure, document system boundaries, create a system map, understand how systems relate, audit dependencies, assess isolation, or do any form of comprehensive architectural analysis. Also trigger when the user says things like 'I want to see all the layers', 'map out the systems', 'what are the moving parts', 'how is this structured', or 'give me the full picture of the architecture'. This is NOT for reviewing code quality or individual files — it's for understanding the full system topology.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
commit
Analyze code changes, group them into logical packages where appropriate, to create sequential, clear, descriptive commits with effective titles and detailed descriptions
workflow-orchestrator
Take on a substantial, multi-step effort as a strategic orchestrator — intake the goal, research and plan it solo, execute it through parallel/sequential agent workflows, then personally verify the result end to end. Use this whenever the user wants to tackle something big or ambitious: a large feature, a cross-cutting refactor, a migration, a codebase-wide audit, a "do all of X / sync everything / overhaul Y" task, or any effort that won't fit in one pass and needs to be planned and orchestrated with rigor. Trigger when the user invokes it by name, says things like "orchestrate this / run a workflow / use subagents / plan and build this / take this on end to end," OR simply describes a meaty multi-part task and wants it done thoroughly and efficiently — even if they never say the words "workflow" or "orchestrate." Do NOT use it for small, single-step tasks that one pass handles directly.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.