@flower-f/afk-plugins-official

Official built-in plugins for afk-dev.

This package is a resource-only package. It contains plugin manifests, agent definitions, skills, and prompts that are discovered and loaded by @flower-f/afk-node at runtime.

Plugins

• code-review-and-fix — default AFK development workflow with an independent code-review agent plus code-review and fix-triage skills.

Usage

Users do not import this package directly. @flower-f/afk-node resolves the plugin root via the package's package.json location and discovers plugins under the src/ directory.

A plugin is enabled by name in afk-dev.config.json:

{
  "plugins": [
    {
      "name": "code-review-and-fix"
    }
  ]
}

Use a custom plugin by path:

{
  "plugins": [
    {
      "path": "../my-afk-plugin"
    }
  ]
}

Custom plugin paths are resolved relative to afk-dev.config.json.

Plugin manifest

A custom plugin uses an afk-dev.plugin.json manifest plus resources such as agents/, skills/, and prompts/.

{
  "$schema": "node_modules/@flower-f/afk-plugins-official/afk-dev.plugin.schema.json",
  "schemaVersion": 1,
  "name": "docs-plugin",
  "pipelines": [
    {
      "name": "docs-generator",
      "module": "pipelines/docs-generator.mjs",
      "export": "docsGeneratorPipeline"
    }
  ],
  "workflows": [
    {
      "name": "docs",
      "pipeline": "docs-generator",
      "roles": {
        "writer": {}
      },
      "stages": {
        "draft": {
          "role": "writer",
          "label": "draft docs",
          "prompt": "Draft docs for {{task}}"
        }
      }
    }
  ]
}

Use $schema for editor completion and validation. The schema is generated from the runtime Zod manifest schema; run pnpm schema:plugin after changing the manifest schema.

pipelines[].module is resolved relative to the plugin root and must stay inside that root. If export is omitted, AFK loads the module's default export. The exported value must satisfy the WorkflowPipeline contract and its name must match the manifest entry.

Publishing a third-party plugin

Third-party plugins can be published as npm packages (or plain directories) that contain an afk-dev.plugin.json manifest. Pipeline modules contributed by a plugin should depend on @flower-f/afk-core and export a WorkflowPipeline instance.