fakoli-crew

Plugin fakoli-crew from marketplace fakoli-plugins in fakoli/fakoli-plugins. Commands read from the repo's manifest — today.

Skills (2)

• crew-ops

  This skill should be used when coordinating multiple fakoli-crew agents on a single project — assembling crews, planning waves, assigning file ownership, or routing work across guido, critic, warden, scout, smith, welder, herald, keeper, and sentinel. Provides wave patterns, file-ownership rules, st

• debugging

  This skill should be used when a test is failing inexplicably, when a runtime error appears in production, when a bug reproduces unpredictably, or when two or more prior fix attempts have failed. Provides a 4-phase systematic debugging workflow — investigate, analyze patterns, form hypothesis, fix w

Slash commands (1)

• /fakoli-crew:crew

  List all 9 fakoli-crew agents with roles, and (if a task is supplied) suggest a crew composition tailored to that task. Pairs with the `crew-ops` skill, which handles multi-agent orchestration once a crew is chosen.

Subagents (9)

• critic

  Use this agent when you need a thorough code review — line-by-line analysis of code quality, naming, safety, and TypeScript correctness. Reviews as a Staff Engineer at a FAANG company would. Critics report; they don't fix. <example> Context: You've finished implementing a new provider module. user:

• guido

  Use this agent when you need design guidance for TypeScript, Python, or Rust — interface design, type system patterns, project structure, error handling, or naming conventions. Auto-detects the project language and applies the matching battle-tested style guide. <example> Context: You're designing a

• herald

  Use this agent when you need documentation that makes people actually want to use a project. Triggers include "improve the README", "rewrite descriptions", "make this appealing", or "better branding". <example> Context: A new plugin was just shipped with a minimal placeholder README. user: Make this

• keeper

  Use this agent when you need to maintain or update repository infrastructure. Triggers include "update CLAUDE.md", "fix CI workflows", "update contributor docs", or "sync the registry". <example> Context: Three new agents were added to the plugin and CLAUDE.md still lists only the original five. use

• scout

  Use this agent when you need to research an API or service and produce a structured reference document — endpoints, auth, schemas, pricing, rate limits, and code examples. <example> Context: You're adding ElevenLabs TTS support to the plugin. user: "Research the ElevenLabs API for text-to-speech." a

• sentinel

  Use this agent when you need comprehensive validation before shipping or merging. Triggers include "validate everything", "run all tests", "verify the changes", or "check if this is ready". <example> Context: Three agents have finished their work on a new plugin release. user: Validate everything be

• smith

  Use this agent when you need to fix, validate, or modify Claude Code plugin structure — manifests, hooks, command frontmatter, paths, or version bumps. <example> Context: You added a new hook and the plugin is rejected on load. user: "Fix the plugin structure — the hooks aren't being recognized." as

• warden

  Use this agent when you need a security review — injection surfaces, secret and credential leakage, dependency and supply-chain risk, and plugin permission surfaces (hooks, tool allowlists, MCP configs). Wardens report; they don't fix. <example> Context: A new feature added an endpoint that shells o

• welder

  Use this agent when you need to integrate new abstractions into existing code without breaking anything. Triggers include phrases like "refactor to use the new", "integrate with", "wire up", or "connect these modules". <example> Context: guido has created a new ProviderProtocol and smith has updated

Similar plugins