Fizzy workflow
Skill izahamyatim/claude-plugin-fizzy/plugins/fizzy/skills/fizzy-workflow
Use for guided Fizzy.do workflows: "set up Fizzy", "configure Fizzy for this project", "sync my work to Fizzy", "review my Fizzy progress", "end of session cleanup". Provides step-by-step guidance for common operations.From its SKILL.md
npx -y skills add izahamyatim/claude-plugin-fizzy --skill fizzy-workflowAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, 320 tokens by cl100k_base, as published. Nobody here has run it
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"
- Check
.claude/fizzy_claude.jsonfor existing config - Verify FIZZY_TOKEN is available
- List boards or create new one
- Save configuration
Sync Todos
Triggers: "sync my work", "sync todos to Fizzy"
- Verify board is configured
- Gather and summarize todos
- Confirm card title
- Execute
fizzy_sync_todos
Progress Review
Triggers: "review my progress", "show Fizzy status"
- Load board config
- Fetch and categorize cards
- Present summary with step counts
Session Cleanup
Triggers: "end of session", "wrap up"
- Review current card from state
- Confirm completion status
- Close card if appropriate
Configuration
| File | Contents |
|---|---|
.claude/fizzy_claude.json | board_id, board_name |
.claude/fizzy_state.json | card_number, card_title, step_map |
Related
- Agent:
fizzy-tasks- Direct operations - Commands:
/fizzy:configure,/fizzy:status
What ships with it: 2 files
4.2 KB alongside SKILL.md
references/
- setup-scenarios.md2.0 KB
- sync-patterns.md2.2 KB
Gives 0 of the 12 instructions most automation workflows skills give in 320 tokens
Counted across 745 of the 1,008 authors here whose files we hold, read 2026-08-07
- Write conventional commit messagesin 36 of 745, across 35 files
- Delete branches after mergein 30 of 745, across 21 files
- Make atomic commitsin 25 of 745, across 15 files
- Write minimal code to pass testsin 22 of 745, across 10 files
- Re-snapshot after navigation or DOM changesin 21 of 745, across 13 files
- Use try-catch for error handlingin 20 of 745, across 8 files
- Run tests before committingin 20 of 745, across 12 files
- Write tests before implementationin 20 of 745, across 8 files
- Configure branch protection rulesin 19 of 745, across 5 files
- Explain the why in commit messagesin 19 of 745, across 9 files
- Refactor code while tests remain greenin 19 of 745, across 6 files
- Interact with elements using refsin 19 of 745, across 11 files
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.