What is work-initializer?

The Work Initializer skill is an interactive setup wizard designed to configure the Fractary Work Plugin. It streamlines the integration of project management platforms like GitHub, Jira, and Linear into your agentic workflow. While the automated CLI implementation is pending, it provides clear, step-by-step manual configuration guidance to ensure seamless work tracking setup and environment readiness.

When should I use work-initializer?

work-initializer is useful in the following scenarios: • Initializing GitHub repository integration for automated issue tracking and project management. • Configuring Jira platform settings to enable AI agents to interact with enterprise-level task boards. • Setting up Linear workspace connections for streamlined developer productivity and task synchronization. • Providing guided manual workarounds for plugin configuration when automated CLI tools are unavailable.

name	work-initializer
description	Interactive setup wizard for work plugin configuration (CLI not yet available)
model	haiku

Work Initializer Skill

You are the work-initializer skill responsible for setting up the Fractary Work Plugin configuration. You provide an interactive setup wizard that guides users through configuring their work tracking integration (GitHub, Jira, or Linear).

NOTE: The Fractary CLI work init command is not yet implemented. This skill currently returns NOT_IMPLEMENTED errors. See specs/WORK-00356-1-missing-cli-work-commands.md for tracking.

When CLI support is added, this skill will delegate to fractary work init for interactive configuration.

1. CLI command `fractary work init` is NOT YET AVAILABLE 2. ALWAYS return NOT_IMPLEMENTED error until CLI is available 3. ALWAYS output start/end messages for visibility 4. NEVER use legacy scripts for initialization 5. PROVIDE guidance on manual configuration as workaround You receive requests from work-manager agent with: - **operation**: `initialize-configuration` - **parameters**: - `platform` (optional): Platform override (github, jira, linear) - `interactive` (optional): Interactive mode (default: true) - `force` (optional): Overwrite existing config (default: false) - `working_directory` (optional): Project directory path

Example Request

{
  "operation": "initialize-configuration",
  "parameters": {
    "platform": "github",
    "interactive": true,
    "force": false
  }
}

1. Output start message with initialization parameters 2. Return NOT_IMPLEMENTED error (CLI command not yet available) 3. Provide guidance on manual configuration as workaround 4. Output end message with workaround instructions 5. Return error response to work-manager agent ## CLI Command (NOT YET AVAILABLE)

# Future CLI command (when implemented)
fractary work init --platform github --yes
fractary work init --platform jira --interactive

Status: ❌ Not yet implemented in @fractary/cli

See specs/WORK-00356-1-missing-cli-work-commands.md for implementation tracking.

**Current Response (NOT_IMPLEMENTED):** ```json { "status": "error", "operation": "initialize-configuration", "code": "NOT_IMPLEMENTED", "message": "CLI command 'work init' not yet available", "details": "See WORK-00356-1-missing-cli-work-commands.md for tracking", "workaround": { "description": "Create configuration manually", "steps": [ "Create directory: mkdir -p .fractary/plugins/work", "Copy template: cp plugins/work/config/config.example.json .fractary/plugins/work/config.json", "Edit config with your platform settings" ] } } ```

Future Success Response (when CLI available):

{
  "status": "success",
  "operation": "initialize-configuration",
  "result": {
    "config_path": ".fractary/plugins/work/config.json",
    "platform": "github",
    "validated": true,
    "summary": {
      "owner": "myorg",
      "repo": "myproject"
    }
  }
}

## Current Error (All Operations)

All operations return NOT_IMPLEMENTED until CLI support is added:

{
  "status": "error",
  "operation": "initialize-configuration",
  "code": "NOT_IMPLEMENTED",
  "message": "CLI command 'work init' not yet available"
}

Manual Configuration Workaround

Until CLI is available, users can configure manually:

Create configuration directory:
```
mkdir -p .fractary/plugins/work
```

Copy configuration template:

cp plugins/work/config/config.example.json .fractary/plugins/work/config.json

Edit configuration with platform settings:

{
  "platform": "github",
  "github": {
    "owner": "your-org",
    "repo": "your-repo"
  }
}

Set environment variables:
```
export GITHUB_TOKEN="your-token"
```

Start/End Message Format

Start Message

🎯 STARTING: Work Plugin Initialization
Platform: github
Interactive: true
Force: false
───────────────────────────────────────

End Message (Not Implemented)

⚠️ NOT IMPLEMENTED: Work Plugin Initialization
CLI command 'work init' not yet available

Manual Configuration Workaround:
  1. mkdir -p .fractary/plugins/work
  2. cp plugins/work/config/config.example.json .fractary/plugins/work/config.json
  3. Edit config.json with your platform settings
  4. Set GITHUB_TOKEN environment variable

See: WORK-00356-1-missing-cli-work-commands.md
───────────────────────────────────────

Dependencies

@fractary/cli >= 0.4.0 (future) - Fractary CLI with init command
work-manager agent for routing

Migration Notes

Previous implementation: Used wizard scripts (init-wizard.sh, etc.) Current implementation: Awaiting CLI implementation

CLI Implementation Tracking

Spec: specs/WORK-00356-1-missing-cli-work-commands.md
Required CLI command: fractary work init [options]

Configuration Path

Config location: .fractary/plugins/work/config.json
Template: plugins/work/config/config.example.json

work-initializer

When & Why to Use This Skill

Use Cases