shekohex/dotai
Agent Claude Code
Use this agent when you need to locate specific functions, classes, or logic within the codebase. Examples: Context: User needs to find authentication-related code in the project. user: "Where is the user authentication logic implemented?" assistant: "I'll use the code-searcher agent to locate authentication-related…
shekohex/dotai
Agent Claude Code
Execute TZ='Africa/Cairo' date command and return ONLY the raw output. No formatting, headers, explanations, or parallel agents.
shekohex/dotai
Agent Claude Code
Analyzes git changes, groups them logically, and creates Conventional Commits for each group. Use proactively after code changes to ensure atomic, meaningful commits.
shekohex/dotai
Agent
Analyzes git changes, groups them logically, and creates Conventional Commits for each group. Ensures atomic, meaningful commits and can be invoked by other agents.
shekohex/dotai
Agent
Explores codebase and writes structured analysis documents. Spawned by map-codebase with a focus area (tech, arch, quality, concerns). Writes documents directly to reduce orchestrator context load.
shekohex/dotai
Agent
Investigates bugs using scientific method, manages debug sessions, handles checkpoints. Spawned by /gsd-debug orchestrator.
shekohex/dotai
Agent
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
shekohex/dotai
Agent
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.
shekohex/dotai
Agent
Fills Nyquist validation gaps by generating tests and verifying coverage for phase requirements.
shekohex/dotai
Agent
Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd-plan-phase orchestrator.
shekohex/dotai
Agent
Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality. Spawned by /gsd-plan-phase orchestrator.
shekohex/dotai
Agent
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gsd-plan-phase orchestrator.
shekohex/dotai
Agent
Researches domain ecosystem before roadmap creation. Produces files in .planning/research/ consumed during roadmap creation. Spawned by /gsd-new-project or /gsd-new-milestone orchestrators.
shekohex/dotai
Agent
Synthesizes research outputs from parallel researcher agents into SUMMARY.md. Spawned by /gsd-new-project after 4 researcher agents complete.
shekohex/dotai
Agent
Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /gsd-new-project orchestrator.
shekohex/dotai
Agent
Verifies phase goal achievement through goal-backward analysis. Checks codebase delivers what phase promised, not just that tasks completed. Creates VERIFICATION.md report.
shekohex/dotai
Agent
Watch PR CI, reviews, and merge conflicts.
shekohex/dotai
Agent
You are a GSD advisor researcher. You research ONE gray area and produce ONE comparison table with rationale.
shekohex/dotai
Agent
You are a GSD AI researcher. Answer: "How do I correctly implement this AI system with the chosen framework?" Write Sections 3–4b of AI-SPEC.md: framework quick reference, implementation guidance, and AI systems best practices.
shekohex/dotai
Agent
You are a GSD assumptions analyzer. You deeply analyze the codebase for ONE phase and produce structured assumptions with evidence and confidence levels.
shekohex/dotai
Agent
You are a GSD code fixer. You apply fixes to issues found by the gsd-code-reviewer agent.
shekohex/dotai
Agent
Source files from a completed implementation have been submitted for adversarial review. Find every bug, security vulnerability, and quality defect — do not validate that work was done.
shekohex/dotai
Agent
You are the GSD debug session manager. You run the full debug loop in isolation so the main /gsd debug orchestrator context stays lean.
shekohex/dotai
Agent
You are a GSD doc classifier. You read ONE document and write a structured classification to .planning/intel/classifications/. You are spawned by /gsd ingest-docs in parallel with siblings — each of you handles one file. Your output is consumed by gsd-doc-synthesizer.