tasker-to-beads

Tasker to Beads Transformer

Converts Tasker task definitions into enriched Beads issues that are self-contained and human-readable. This skill performs the "neural" work of understanding spec context, synthesizing narratives, and creating issues that stand alone.

When to Use

• After completing Tasker /plan phase (state is "ready")
• When you want to track implementation progress in Beads
• When multiple people/agents will work on tasks and need persistent context

Prerequisites

1. Tasker planning complete (.tasker/state.json exists, phase is "ready")
2. A target directory for development (beads will be initialized there if needed)

Target Directory Concept

The source project (where tasker planning lives) may be different from the target project (where development happens). For example:

• Source: ~/projects/tasker/ - contains spec, planning artifacts, task definitions
• Target: ~/projects/fathom/ - where the actual Elixir project will be built

When invoked, this skill will:

1. Ask for the target directory if not provided
2. Initialize beads in the target directory if not already done
3. Create issues in the target project's beads system

---

Workflow

Step 0: Determine Target Directory

IMPORTANT: Before proceeding, ask the user where development will happen:

"Where would you like to create the Beads issues? This should be the directory where the actual development will take place (e.g., the project repository being built)."

Common scenarios:

• Same directory: Use current project (e.g., adding features to existing codebase)
• New directory: Create issues in a separate project (e.g., building a new project from a spec)

Step 1: Initialize Target (if needed)

# Check status and see if target needs initialization
tasker transform status -t /path/to/target

# Initialize beads in target directory with custom prefix
# This runs: bd init <PREFIX> && bd onboard
tasker transform init-target /path/to/target FATHOM