Get the FREE Ultimate OpenClaw Setup Guide →

fizzy-workflow

Scanned
npx machina-cli add skill keskinonur/claude-plugin-fizzy/fizzy-workflow --openclaw
Files (1)
SKILL.md
1.4 KB

Fizzy.do Guided Workflow Skill

Provides structured workflows for Fizzy.do task management. For direct operations, use the fizzy-tasks agent.

Workflows

Project Setup

Triggers: "set up Fizzy", "configure Fizzy for this project"

  1. Check .claude/fizzy_claude.json for existing config
  2. Verify FIZZY_TOKEN is available
  3. List boards or create new one
  4. Save configuration

Sync Todos

Triggers: "sync my work", "sync todos to Fizzy"

  1. Verify board is configured
  2. Gather and summarize todos
  3. Confirm card title
  4. Execute fizzy_sync_todos

Progress Review

Triggers: "review my progress", "show Fizzy status"

  1. Load board config
  2. Fetch and categorize cards
  3. Present summary with step counts

Session Cleanup

Triggers: "end of session", "wrap up"

  1. Review current card from state
  2. Confirm completion status
  3. Close card if appropriate

Configuration

FileContents
.claude/fizzy_claude.jsonboard_id, board_name
.claude/fizzy_state.jsoncard_number, card_title, step_map

Related

  • Agent: fizzy-tasks - Direct operations
  • Commands: /fizzy:configure, /fizzy:status

Source

git clone https://github.com/keskinonur/claude-plugin-fizzy/blob/main/plugins/fizzy/skills/fizzy-workflow/SKILL.mdView on GitHub

Overview

Fizzy-workflow provides structured, step-by-step workflows for managing Fizzy.do tasks. It covers Project Setup, Sync Todos, Progress Review, and Session Cleanup, each with trigger phrases like 'set up Fizzy' or 'sync my work'. For direct actions, you can leverage the fizzy-tasks agent.

How This Skill Works

Each workflow defines a trigger and a concrete sequence of steps, from config checks to actions like syncing todos. It persists configuration in .claude/fizzy_claude.json and card state in .claude/fizzy_state.json, enabling consistent board and card tracking. Some steps invoke Fizzy.do commands (e.g., fizzy_sync_todos) or the fizzy-tasks agent for direct operations.

When to Use It

  • Starting a new Fizzy.do project and configuring a board (trigger: 'set up Fizzy')
  • Syncing local todos to Fizzy as cards (trigger: 'sync my work' or 'sync todos to Fizzy')
  • Reviewing progress with categorized cards and step counts (trigger: 'review my progress')
  • Wrapping up a session and cleaning up cards (trigger: 'end of session')
  • Verifying board config and readiness before work (trigger: 'show Fizzy status' or check status)

Quick Start

  1. Step 1: Verify .claude/fizzy_claude.json contains board_id and board_name and that FIZZY_TOKEN is available
  2. Step 2: Run 'set up Fizzy' to configure the project board and save state
  3. Step 3: Use 'sync my work' or 'review my progress' as needed; run 'end of session' to wrap up

Best Practices

  • Pre-check config and token before operations
  • Use clear, consistent board and card titles
  • Regularly run Progress Review to categorize cards and count steps
  • Validate sync results before proceeding with next steps
  • Cleanly close or wrap up sessions with Session Cleanup

Example Use Cases

  • Set up Fizzy for a new project by triggering 'set up Fizzy' to create or configure a board and save board_id/board_name.
  • Sync backlog items to Fizzy as cards using 'sync my work' to reflect current work items.
  • Review progress with a categorized summary of cards and step counts via 'review my progress'.
  • Wrap up a session by running 'end of session' to confirm completion and close cards.
  • Switch projects by reusing existing .claude/fizzy_claude.json and .claude/fizzy_state.json to maintain context.

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers