@cliangdev/flux-plugin 0.1.0 → 0.2.0

package/skills/flux-orchestrator/SKILL.md

@@ -1,21 +1,25 @@
 ---
+name: flux:flux-orchestrator
 description: Orchestrates Flux workflows based on project context
+user-invocable: false
 ---
 
 # Flux Orchestrator Skill
 
-This skill is automatically active when working in a Flux project. It provides context about available tools and workflow patterns.
+This skill is automatically active when working in a Flux project. It provides context about available tools, workflow patterns, and integration options.
 
 ## Available MCP Tools
 
 ### Query Tools
-- `get_project_context` - Check if project initialized, get name/vision/prefix
+- `get_project_context` - Check if project initialized, get name/vision/adapter type
 - `get_stats` - Get PRD/epic/task counts by status
 - `get_entity` - Fetch entity by ref with optional includes (criteria, tasks, dependencies)
 - `query_entities` - Search entities by type, status, parent ref
+- `render_status` - Get formatted project status with progress bars
 
 ### Mutation Tools
 - `init_project` - Initialize new .flux/ directory with project.json and database
+- `configure_linear` - Configure Linear integration (supports interactive mode)
 - `create_prd` - Create a new PRD
 - `create_epic` - Create an epic linked to a PRD
 - `create_task` - Create a task linked to an epic
@@ -29,102 +33,82 @@ This skill is automatically active when working in a Flux project. It provides c
 - `add_criteria` - Add acceptance criterion to epic or task
 - `mark_criteria_met` - Mark criterion as satisfied
 
-## Workflow States
+## Available Commands
 
-The Flux project progresses through these states:
+| Command | Purpose |
+|---------|---------|
+| `/flux` | Project init, status, and workflow routing |
+| `/flux:linear` | Connect project to Linear (interactive setup) |
+| `/flux:prd` | Create or refine PRDs |
+| `/flux:breakdown` | Break approved PRD into epics and tasks |
+| `/flux:implement` | Implement tasks with TDD workflow |
 
-1. **Uninitialized** - No .flux/ directory
-   - Action: Run `/flux` to initialize
+## Workflow States
 
-2. **No PRDs** - Project initialized but empty
-   - Action: Run `/flux:prd` to create first PRD
+```
+Uninitialized → Initialized → PRD Draft → Pending Review → Reviewed → Approved → Breakdown Ready → In Progress → Complete
+                     ↓
+              (optional) Linear Connected
+```
 
-3. **PRD Draft** - PRD created but needs review
-   - Action: Review and submit for approval or refine
+### PRD Status Transitions
+```
+DRAFT → PENDING_REVIEW → REVIEWED → APPROVED → BREAKDOWN_READY → COMPLETED
+          ↓                 ↓
+        DRAFT (revise)    DRAFT (revise)
+```
 
-4. **PRD Pending Review** - PRD submitted for review
-   - Action: Run critique agent, then approve or revise
+### Epic/Task Statuses
+- `PENDING` → `IN_PROGRESS` → `COMPLETED`
+
+## Backend Adapters
 
-5. **PRD Reviewed** - Critique complete
-   - Action: Address feedback, then approve or revise to DRAFT
+Flux supports multiple backends via the adapter pattern:
 
-6. **PRD Approved** - Ready for epic breakdown
-   - Action: Run `/flux:breakdown` to create epics
+| Adapter | Storage | Use Case |
+|---------|---------|----------|
+| `local` | SQLite (.flux/flux.db) | Default, offline-first |
+| `linear` | Linear API | Team collaboration, issue tracking |
 
-7. **Breakdown Ready** - Epics and tasks created
-   - Action: Run `/flux:implement` to start coding
+### Switching to Linear
 
-8. **Implementation In Progress** - Tasks IN_PROGRESS
-   - Action: Continue implementing current task
+Use `configure_linear` with interactive mode:
+1. `{interactive: true}` → returns teams list
+2. `{interactive: true, teamId: "..."}` → returns projects list
+3. `{teamId: "...", projectName/existingProjectId: "..."}` → configures
 
-9. **Complete** - All tasks COMPLETED
-    - Action: Review and create PR
+Or run `/flux:linear` for guided setup.
 
 ## Entity References
 
-All entities have a reference format: `{PREFIX}-{TYPE}{NUMBER}`
+Format: `{PREFIX}-{TYPE}{NUMBER}`
 
 - PRD: `MSA-P1`, `MSA-P2`
 - Epic: `MSA-E1`, `MSA-E2`
 - Task: `MSA-T1`, `MSA-T2`
 
-The prefix is generated from the project name during initialization.
-
-## Status Values
-
-### PRD Statuses (6-stage workflow)
-- `DRAFT` - Initial state, being created/refined
-- `PENDING_REVIEW` - Submitted for critique
-- `REVIEWED` - Critique complete, awaiting approval
-- `APPROVED` - Ready for epic breakdown
-- `BREAKDOWN_READY` - Epics and tasks created
-- `COMPLETED` - All epics done
-
-### Valid PRD Transitions
-```
-DRAFT → PENDING_REVIEW
-PENDING_REVIEW → REVIEWED | DRAFT (revise)
-REVIEWED → APPROVED | DRAFT (revise)
-APPROVED → BREAKDOWN_READY
-BREAKDOWN_READY → COMPLETED
-```
-
-### Epic/Task Statuses
-- `PENDING` - Not started
-- `IN_PROGRESS` - Currently being worked on
-- `COMPLETED` - Done
-
-## Confidence-Based Autonomy
-
-The orchestrator uses confidence levels to determine autonomy:
-
-| Confidence | Behavior | Example |
-|------------|----------|---------|
-| > 80% | Auto-execute, inform user | "I'm creating the epic structure..." |
-| 50-80% | Suggest action, wait for confirmation | "Ready to break down into tasks. Proceed?" |
-| < 50% | Ask clarifying question | "Should we research this technology first?" |
-
-### Confidence Indicators
-- **High confidence (>80%)**: Clear next step, no ambiguity, user has been responsive
-- **Medium confidence (50-80%)**: Reasonable next step, some uncertainty
-- **Low confidence (<50%)**: Multiple valid paths, unclear requirements, unfamiliar tech
-
 ## Available Subagents
 
-### Research Agent
-- **Trigger**: Unfamiliar technology mentioned, confidence < 70%
-- **Purpose**: Gather information about libraries, frameworks, APIs
+### Research Agent (`flux:flux-researcher`)
+- **Trigger**: Unfamiliar technology, confidence < 70%
 - **Tools**: Context7, WebSearch, WebFetch
 
-### Critique Agent
-- **Trigger**: PRD status becomes PENDING_REVIEW
-- **Purpose**: Analyze feasibility, scope, risks
-- **Output**: Structured critique with recommendations
+### Critique Agent (`flux:flux-critic`)
+- **Trigger**: PRD submitted for review
+- **Output**: Feasibility analysis, risks, recommendations
+
+### Coder Agent (`flux:flux-coder`)
+- **Trigger**: Task implementation
+- **Workflow**: TDD - write tests, implement, verify
+
+### Verifier Agent (`flux:flux-verifier`)
+- **Trigger**: After implementation
+- **Purpose**: Verify acceptance criteria coverage
 
 ## Best Practices
 
-1. **Check context first** - Always call `get_project_context` before taking actions
-2. **Use refs, not IDs** - Tools accept human-readable refs like `MSA-E1`
-3. **Validate status transitions** - Use `update_status` which enforces valid transitions
-4. **Include related data** - Use `include` parameter to fetch nested entities in one call
-5. **Handle errors gracefully** - Tools return errors with codes, display user-friendly messages
+1. **Check context first** - Call `get_project_context` before actions
+2. **Use refs, not IDs** - Tools accept `MSA-E1` format
+3. **Use render_status** - For visual project overview
+4. **Validate transitions** - `update_status` enforces valid transitions
+5. **Include related data** - Use `include` param to fetch nested entities

package/skills/prd-template/SKILL.md

@@ -1,5 +1,7 @@
 ---
+name: flux:prd-template
 description: PRD structure and patterns for Flux. Use when creating or refining product requirement documents. PRDs should be concise for humans but detailed enough for AI agents to implement.
+user-invocable: false
 ---
 
 # PRD Template Skill