Use this agent to review a proposed feature or solution against design values before implementation. Evaluates sophistication (depth of understanding), empowerment (serves the user), robustness (handles failure gracefully), ethics (manipulation, accessibility, privacy, sustainability), and explainability (can you…
Use this agent when switching between projects (Iris, Rhea, Theia, etc.) to quickly rebuild context. Synthesizes recent git history, architectural decisions, current work state, and key patterns to minimize context-switching friction. Invoke with "What's the state of this project?" or "Catch me up on [project]".
Use this agent when the user requests documentation or roadmap updates, mentions project planning or milestones, discusses feature priorities, or after significant development progress has been made. This agent proactively maintains alignment between code changes and project documentation.\n\nExamples:\n\n \nContext…
Reviews PRDs for completeness, API accuracy, and implementation readiness. Orchestrates parallel sub-reviewers with a three-phase matrix-driven process — scaffold, fill (parallel agents including a dedicated smell pass), verify — to guarantee full coverage. Use after a PRD draft exists and before approval.
Judges a technical PRD review, decides the product questions it raises, and turns the survivors into revision tickets for the writer. Runs after prd-reviewer and before any revision cycle. Use when a review exists and someone must decide what is actually worth fixing.
Detects project type, scans the repo, and drafts .claude/project-context.md automatically. Run once when adopting the PRD agents framework into a new project.
Surveys the graph and notes what has gone leggy or stale — never prunes. Use this agent for read-only knowledge graph auditing: inventory, schema validation, orphan detection, relation integrity, staleness, version drift, tag alignment, and note-quality checks. Typical triggers include: "audit my knowledge graph"…
The only one with shears — mends what the gardener marked. Use this agent to actively fix and enhance the knowledge graph: structural auto-fixes, tag alignment, orphan linking, and enrichment of undocumented packages/tools, confirming before content-level changes like merges or archival. Typical triggers include: "fix…
Tends the bookmark annex — same discipline, different soil. Use this agent for read-only Raindrop.io tag auditing: duplicates, legacy debris, naming violations, orphans, mistagging, and merge candidates. Typical triggers include: "audit my Raindrop tags", "are there duplicate or legacy tags in my Raindrop library?"…
Sviluppo backend Laravel (PHP) e Node.js/Express - API, modelli, migrazioni, servizi, queue. Usalo per implementare feature backend nei progetti dell'ecosistema.
CI/CD e release - GitHub Actions tag-triggered, build Flutter iOS/Android (runner macOS self-hosted, Codemagic), firma, store deploy, secrets di pipeline. Usalo per pipeline e rilasci.
Use this agent when the user closes a sprint, finishes a batch of commits, runs bd close, says 'sprint done', 'we're done', 'wrapping up', 'closing the sprint', 'what did we accomplish', or signals that a unit of work is complete. Also trigger proactively when a bd close command has just run or the user is asking what…
Utiliser pour pré-trier les tickets entrants et préparer la décision humaine sans s'y substituer. Détecte les doublons probables, signale les incohérences entre criticité déclarée et impact mesuré, et propose un pré-classement révisable.
Utiliser pour la veille concurrentielle continue. Surveille une liste fermée de sources externes (sites, blogs produit, communiqués, comptes sociaux), produit une note de pilotage hebdomadaire de cinq minutes de lecture, et alerte sur mouvement à fort impact.
Utiliser pour comparer en continu l'avancement effectif de la roadmap à la trajectoire prévue. Produit une note de pilotage hebdomadaire avec maximum trois alertes classées par enjeu décisionnel, et déclenche des alertes immédiates sur glissement.
INTERNAL: Part of /kenspc-task-review orchestration. Requires REVIEWREPORTS structured CONTEXT input from the calling skill — standalone invocation will fail the prerequisite check. Do not auto-delegate.
INTERNAL: Part of /kenspc-task-review orchestration. Requires REVIEWREPORTS and ACCOUNTABILITYLIST CONTEXT — standalone invocation will fail the prerequisite check. Do not auto-delegate.
INTERNAL: Part of /kenspc-task-implement orchestration. Requires validated task document path — standalone invocation will fail the prerequisite check. Do not auto-delegate.
Use when a task requires running the same instruction over many items - classifying, extracting, summarising or rewriting tens to thousands of records. Delegates to a cheap model through the sidequest CLI and returns only a summary, keeping bulk output out of the main context.
Analyst agent. Handles critical analysis, risk assessment, quality reviews, and feasibility evaluation. Use when asked "what do you think?", "any issues?", "review this", "evaluate this", "give feedback", "SWOT analysis", "what are the risks?", or "check this".
Ideator agent. Handles creative brainstorming, divergent thinking, and new idea generation. Use when asked for ideas, "any interesting suggestions?", new feature proposals, solution brainstorming, or creative suggestions.
Researcher agent. Handles deep investigation, information gathering, source triangulation, and synthesis. Use when asked to research, investigate, do technical/market research, comparative analysis, or "look into..." and "what's the current state of...?".
"Is this correct?" — Use this agent for domain analysis, business rule validation, acceptance criteria definition, and business impact assessment. Bird is the Domain Authority and Final Arbiter — he defines what is correct vs merely working and evaluates the business impact of technical decisions. Use via /team for…