Generate epics and tasks in Flux from project requirements

GitHub stars
109

Install

/plugin install flux@flux

Run it inside Claude Code after adding the marketplace with /plugin marketplace add sirsjg/flux.

Contents

Discovered from source

Commands 3

Flux Add

Quickly create a task in Flux from a brief description.

Instructions

  1. Parse the user's input to extract:

    • Task title (required)
    • Epic or project context (if mentioned)
    • Any notes or acceptance criteria
  2. If no project is specified, use list_projects to find the most recently updated project or ask which to use.

  3. If an epic is mentioned by name, use list_epics to find the matching epic ID.

  4. Create the task with create_task including:

    • A clear, actionable title
    • Any provided notes
    • Epic association if specified
  5. Confirm creation with the task title and location.

Examples

User: "add task: implement password reset flow" → Creates task "Implement password reset flow" in the active project

User: "flux add: fix the login bug in the auth epic" → Creates task "Fix login bug" in the Authentication epic

User: "add a task to review the API documentation with high priority" → Creates task "Review API documentation" with priority note

Flux Generate

Analyze the current project and generate a structured breakdown of epics and tasks in Flux.

Process

  1. Gather Requirements: Read README.md, PRD documents, specs, or any files the user specifies. If none exist, ask the user to describe what they're building.

  2. Identify the Project: Check if a Flux project exists for this codebase using list_projects. If not, create one with create_project.

  3. Define Epics: Break down the requirements into major features or workstreams. Each epic should represent a distinct deliverable. Create them with create_epic.

  4. Create Tasks: For each epic, create granular tasks that can be completed in a single work session. Include:

    • Clear, actionable titles
    • Detailed notes with acceptance criteria
    • Dependencies on other tasks where applicable
  5. Set Dependencies: Identify task dependencies (e.g., "API endpoint" must be done before "Frontend integration") and set them using the depends_on field.

Output

After generation, summarize what was created:

  • Project name
  • Number of epics and tasks
  • Key dependencies identified
  • Suggested starting point (tasks with no blockers)

Flux Status

Show the current state of your Flux board and suggest what to work on next.

Instructions

  1. Use list_projects to get all projects with their stats.

  2. For the active project (or most recently updated), use list_epics and list_tasks to get the full picture.

  3. Present a summary:

    • Tasks in progress (doing)
    • Blocked tasks and what's blocking them
    • Tasks ready to start (todo with no blockers)
    • Recently completed tasks
  4. Suggest the next task to pick up based on:

    • Unblocking other tasks (high impact)
    • No dependencies (ready to start)
    • Epic progress (finishing an epic)

Output Format

📊 Project: my-app

🔄 In Progress (2)
  • Implement JWT service
  • Design dashboard layout

🚫 Blocked (1)
  • Create login endpoint (waiting on: JWT service)

✅ Ready to Start (3)
  • Set up CI pipeline
  • Write API documentation
  • Add unit tests for auth

💡 Suggested Next: "Set up CI pipeline" - unblocks deployment tasks

MCP servers 1

Sponsors

Details

Marketplace
sirsjg/flux
Source
packages/plugin
Category
Community