@cliangdev/flux-plugin 0.2.0-dev.dc5e2c4 → 0.2.0-dev.e34d43b

package/README.md

@@ -36,7 +36,7 @@ The installer automatically:
 | Command | Purpose |
 |---------|---------|
 | `/flux` | Smart entry point - shows status and guides you to the next step |
-| `/flux:prd` | Create product requirements through guided interview |
+| `/flux:prd` | Create PRDs through discovery, research, and guided writing |
 | `/flux:breakdown` | Break PRDs into epics and tasks with acceptance criteria |
 | `/flux:implement` | Implement tasks with TDD workflow |
 
@@ -143,7 +143,7 @@ Check your current version:
 
 ```bash
 rm -rf ~/.claude/commands/flux.md ~/.claude/commands/flux
-rm -rf ~/.claude/skills/agent-creator ~/.claude/skills/epic-template ~/.claude/skills/flux-orchestrator ~/.claude/skills/prd-template
+rm -rf ~/.claude/skills/agent-creator ~/.claude/skills/epic-template ~/.claude/skills/flux-orchestrator ~/.claude/skills/prd-writer
 rm -f ~/.claude/flux-version
 # Edit ~/.claude.json and remove the "flux" entry from "mcpServers"
 ```
@@ -152,7 +152,7 @@ rm -f ~/.claude/flux-version
 
 ```bash
 rm -rf .claude/commands/flux.md .claude/commands/flux
-rm -rf .claude/skills/agent-creator .claude/skills/epic-template .claude/skills/flux-orchestrator .claude/skills/prd-template
+rm -rf .claude/skills/agent-creator .claude/skills/epic-template .claude/skills/flux-orchestrator .claude/skills/prd-writer
 rm -f .claude/flux-version
 # Edit .claude.json and remove the "flux" entry from "mcpServers"
 ```

package/commands/breakdown.md

@@ -16,10 +16,10 @@ Check if arguments were provided:
 
 ## Pre-checks
 
-1. Call `get_project_context` to ensure Flux is initialized
-   - If not initialized, tell user: "Run `/flux` first to initialize the project."
+1. If no ref provided, call `query_entities` with type=prd, status=APPROVED
+   - If error with `code: "PROJECT_NOT_INITIALIZED"`, tell user: "Run `/flux` first to initialize the project." and exit.
 
-2. If no ref provided, call `query_entities` with type=prd, status=APPROVED
+2. If query successful but no approved PRDs found:
    - If no approved PRDs, tell user: "No approved PRDs found. Approve a PRD first or run `/flux:prd` to create one."
    - If multiple approved PRDs, use AskUserQuestion to let user select which one
 

package/commands/flux.md

@@ -6,27 +6,78 @@ allowed-tools: mcp__plugin_flux_flux__*, AskUserQuestion, Read, Write
 
 # Flux Command
 
-You are the Flux orchestrator. Detect project state and guide the user to the appropriate next action.
+You are the Flux orchestrator - the main entry point for all Flux operations. Your job is to:
+1. Detect project state and guide users to the appropriate next action
+2. Route to specialized commands based on user input
+3. Provide intelligent suggestions based on workflow state
+
+## Available Commands
+
+| Command | Description |
+|---------|-------------|
+| `/flux` | Show project status and suggest next action |
+| `/flux:prd` | Create or refine PRDs through guided interview |
+| `/flux:breakdown` | Break approved PRD into dependency-ordered epics and tasks |
+| `/flux:implement` | Implement tasks with TDD workflow using specialized coding agents |
+| `/flux:linear` | Connect Flux project to Linear for issue tracking |
+
+## Subcommand Routing
+
+When user provides arguments, route to the appropriate command:
+
+| User Input | Action |
+|------------|--------|
+| `/flux` | Show status (see Main Flow) |
+| `/flux version` | Call `get_version` and display result |
+| `/flux status` | Call `render_status` with `{view: "full"}` |
+| `/flux prd` or `/flux prd ...` | Delegate to `/flux:prd` with any additional args |
+| `/flux breakdown` or `/flux breakdown ...` | Delegate to `/flux:breakdown` with any additional args |
+| `/flux implement` or `/flux implement ...` | Delegate to `/flux:implement` with any additional args |
+| `/flux linear` | Delegate to `/flux:linear` |
+| `/flux help` | Show available commands and their purposes |
+
+## Available MCP Tools
+
+These tools are available for programmatic access:
+
+**Entity Management:**
+- `create_prd`, `create_epic`, `create_task` - Create entities
+- `update_entity`, `update_status`, `delete_entity` - Modify entities
+- `get_entity`, `query_entities` - Retrieve entities
+
+**Project:**
+- `init_project` - Initialize new Flux project
+- `get_stats` - Get entity counts by status
+- `get_version` - Get plugin version
+- `render_status` - Visual project status with progress bars
+
+**Relationships:**
+- `add_dependency`, `remove_dependency` - Task/epic dependencies
+- `add_criteria`, `mark_criteria_met` - Acceptance criteria
+
+**Integration:**
+- `configure_linear` - Connect to Linear (interactive mode supported)
 
-## Subcommands
+## Main Flow
 
-- `/flux version` - Show plugin version (call `get_version`)
-- `/flux linear` - Connect to Linear (delegate to `/flux:linear`)
+### Step 0: Check for Subcommands
 
-## Main Flow
+First, check if the user provided arguments (e.g., `/flux prd`, `/flux implement FP-T1`).
+If so, route to the appropriate command as described in Subcommand Routing above.
 
-### Step 1: Get Project Context
+### Step 1: Check Project State
 
-Call `get_project_context` to check project state.
+If no subcommand, call `render_status` with `{view: "summary"}` to show current state.
 
-### Step 2: Route Based on State
+### Step 2: Route Based on Response
 
-**If `initialized: false`:**
+**If error with `code: "PROJECT_NOT_INITIALIZED"`:**
 → Guide through initialization (see Initialization Flow below)
 
-**If `initialized: true`:**
-→ Call `render_status` with `{view: "summary"}` to show current state
-→ Determine next action based on workflow state (see Workflow States)
+**If success:**
+→ Display the rendered status
+→ Analyze workflow state and suggest the most appropriate next action (see Workflow States)
+→ If multiple actions are possible, use AskUserQuestion to let user choose
 
 ## Initialization Flow
 
@@ -148,9 +199,38 @@ When determining actions:
 | 50-80% | Suggest action, wait for confirmation |
 | < 50% | Ask clarifying question |
 
+## Help Output
+
+When user runs `/flux help`, display:
+
+```
+Flux - AI-first workflow orchestration
+
+Commands:
+  /flux              Show project status and next action
+  /flux:prd          Create or refine PRDs
+  /flux:breakdown    Break PRD into epics and tasks
+  /flux:implement    Implement tasks with TDD
+  /flux:linear       Connect to Linear
+
+Shortcuts:
+  /flux prd          Same as /flux:prd
+  /flux breakdown    Same as /flux:breakdown
+  /flux implement    Same as /flux:implement
+  /flux status       Show detailed project status
+  /flux version      Show plugin version
+
+Workflow:
+  1. /flux           Initialize project (first time)
+  2. /flux:prd       Create your first PRD
+  3. /flux:breakdown Break PRD into tasks
+  4. /flux:implement Start coding with TDD
+```
+
 ## Guidelines
 
 - Use `AskUserQuestion` tool for all user choices during initialization
 - Be concise - show status and one clear next action
 - Use `render_status` for visual project overview
 - Apply confidence-based autonomy for decisions
+- When user input matches a subcommand pattern, delegate immediately without calling render_status first

package/commands/implement.md

@@ -53,8 +53,7 @@ The orchestrator resolves all refs to tasks, builds a dependency-ordered queue,
 
 ## Pre-checks
 
-1. Call `get_project_context` to ensure Flux is initialized
-2. Parse arguments and resolve to tasks:
+1. Parse arguments and resolve to tasks (if any tool returns `PROJECT_NOT_INITIALIZED` error, tell user: "Run `/flux` first to initialize the project." and exit):
    - No args: Query for next PENDING task with no blockers
    - PRD ref(s): Expand to all epics → all tasks
    - Epic ref(s): Expand to all tasks

package/commands/linear.md

@@ -21,13 +21,14 @@ The `configure_linear` tool supports progressive discovery:
 
 ## Flow
 
-### Step 1: Verify Project
+### Step 1: Verify Project & Fetch Teams
 
-Call `get_project_context`.
+Call `configure_linear` with `{interactive: true}`.
 
-- If `initialized: false` → Tell user to run `/flux` first, then exit.
-- If `adapter.type === "linear"` and config exists → Already configured, show info and exit.
-- Otherwise → Continue to Step 2.
+- If error with `code: "PROJECT_NOT_INITIALIZED"` → Tell user to run `/flux` first, then exit.
+- If error about Linear API key → Show instructions (see Step 2 error handling).
+- If success with `step: "already_configured"` → Already configured, show info and exit.
+- Otherwise → Continue with team selection (response contains teams list).
 
 ### Step 2: Fetch Teams