rbin-task-flow 1.18.1 → 1.19.1

package/.cursor/rules/coding_standards.mdc

@@ -85,6 +85,29 @@ In **front web** (Next.js, React) or **mobile** (Expo, React Native) projects, e
 - **Validation**: Zod (not class-validator/class-transformer)
 - **Structure**: `src/app/` (controllers), `src/features/` (use-cases, repositories), `src/shared/` (guards, pipes, gateways)
 
+### ESLint — @rbinflow/eslint-config
+
+When the project uses `@rbinflow/eslint-config`, **do not add any other ESLint plugins or configs** — `@rbinflow/eslint-config` already configures everything. The `.eslintrc.cjs` file must stay minimal:
+
+**Available configurations:**
+
+| Project type | extends |
+|--------------|---------|
+| Node.js (no semicolons) | `@rbinflow/eslint-config/node` |
+| Node.js (with semicolons) | `@rbinflow/eslint-config/node-with-semi` |
+| React | `@rbinflow/eslint-config/react` |
+| Next.js | `@rbinflow/eslint-config/next` |
+| Expo | `@rbinflow/eslint-config/expo` |
+
+**Example (.eslintrc.cjs):**
+```javascript
+module.exports = {
+  extends: ['@rbinflow/eslint-config/next'],
+}
+```
+
+**Node.js variants:** `node` uses `semi: false`; `node-with-semi` uses `semi: true`. All other settings are identical. No extra `plugins`, `rules`, or `extends` beyond this.
+
 ---
 
 ## app/ — Routes Only (Front-end & Mobile) / Controllers Only (Backend)

package/.cursor/rules/task_analysis.mdc

@@ -62,6 +62,7 @@ alwaysApply: true
      - Rebuild tasks.json with all tasks in correct order (matching tasks.input.txt order)
      - Rebuild status.json preserving all existing statuses (or updating if needed)
      - Rebuild tasks.status.md with all tasks and correct status marks (synchronized with status.json)
+     - **DO NOT** update or populate `.task-flow/tasks.flow.md` — that file is filled only by `task-flow: generate flow`
      - **ALWAYS regenerate summary section** at the top of tasks.status.md:
        - Count completed tasks (all subtasks done)
        - Count in-progress tasks (some subtasks done)

package/.cursor/rules/task_execution.mdc

@@ -37,6 +37,7 @@ alwaysApply: true
   - `task-flow: report X` - Generate implementation report for task X (simplified - no "task" needed)
   - `task-flow: report X,Y` - Generate reports for multiple tasks (comma-separated)
   - `task-flow: report all` - Generate reports for all tasks
+  - `task-flow: generate flow` - Populate tasks.flow.md with dependencies, estimated hours (mid-level dev, billing), and AI model recommendations
 
 - **Workflow Example:**
   ```markdown
@@ -102,6 +103,10 @@ alwaysApply: true
   - See [task_refactor.mdc](mdc:.cursor/rules/task_refactor.mdc) for refactoring code from current commit
   - When user says "task-flow: refactor", improve code quality without changing functionality
 
+- **Task Flow Generation:**
+  - See [task_generate_flow.mdc](mdc:.cursor/rules/task_generate_flow.mdc) for populating tasks.flow.md
+  - When user says "task-flow: generate flow", populate dependencies and model recommendations
+
 - **Task Flow Commands - Natural Language Interpretation:**
   - **CRITICAL**: When user mentions **"task flow"**, they **ALWAYS** refer to **RBIN Task Flow**
   - Common phrases that mean "work on RBIN Task Flow subtasks":

package/.cursor/rules/task_generate_flow.mdc

@@ -0,0 +1,73 @@
+---
+description: Generate task flow with dependencies, estimated hours (billing), and AI model recommendations
+globs: **/*
+alwaysApply: true
+---
+
+- **Task Flow Generation - Dependencies, Hours & Model Recommendations:**
+  - **FAST FORMAT**: `task-flow: generate flow` → Populate tasks.flow.md with dependencies, estimated hours, and model recommendations
+  - When user says "task-flow: generate flow", "generate flow", "gerar flow", or "flow":
+    - **READ**: `.task-flow/.internal/tasks.json` to get all tasks
+    - **READ**: `.task-flow/.internal/status.json` (optional, for context)
+    - **ANALYZE**: For each task, determine dependencies, estimated hours, and model recommendations
+    - **WRITE**: Populate `.task-flow/tasks.flow.md` with the generated flow
+  - **DO NOT**: Populate tasks.flow.md when running `task-flow: sync` — only when `task-flow: generate flow`
+
+- **Generation Process:**
+  1. **Search for current model versions** (quick web search): Codex, Composer (Cursor), Claude (Haiku, Sonnet, Opus). Use the latest available versions in recommendations.
+  2. Read all tasks from tasks.json (id, title, description, subtasks)
+  3. For each task, determine:
+     - **Estimated hours** (dev mediano, cobrança ao cliente): Range in hours for mid-level developer (3-5 years). Formula: subtasks × 2 to subtasks × 3 hours (same as [task_estimate.mdc](mdc:.cursor/rules/task_estimate.mdc)). Round to nearest hour. Purpose: developer billing.
+     - **Dependencies**: Which tasks (if any) must be completed first
+       - Infer from task order, descriptions, subtask content
+       - Task 1 typically has no dependencies
+       - Task N may depend on 1..N-1 if it builds on their output
+       - Use "none" or "nenhuma" when no dependencies
+     - **Model recommendations** (in order, most to least indicated):
+       - **Codex** (variants): include current version from web search
+       - **Composer** (Cursor): include current version from web search
+       - **Claude**: Haiku, Sonnet, Opus — include current version from web search
+     - **Effort**: low, medium, or high (based on subtask count, complexity)
+  4. Output format per task (simple, one line):
+     - `task X - depende da task Y - X-Yh (dev mediano, cobrança) - model1 effort E, model2, model3 effort E`
+     - Or: `task X - nenhuma dependência - X-Yh (dev mediano, cobrança) - model1 effort E, model2, model3 effort E`
+
+- **Output Format for tasks.flow.md:**
+  ```markdown
+  # Task Flow — Dependencies, Hours & Model Recommendations
+
+  <!-- Populated by task-flow: generate flow. Do not edit manually. -->
+  <!-- Horas: dev mediano (3-5 anos), uso para cobrança ao cliente -->
+
+  ## Tasks
+
+  task 1 - nenhuma dependência - 6-9h (dev mediano, cobrança) - codex effort medium, composer, claude sonnet effort medium
+  task 2 - depende da task 1 - 8-12h (dev mediano, cobrança) - codex effort medium, composer, claude sonnet effort medium
+  task 3 - depende da task 2 - 14-21h (dev mediano, cobrança) - codex effort high, composer, claude opus effort high
+  ```
+
+- **Model Recommendation Rules:**
+  - **MUST list multiple models** in order (most to least indicated), not just one
+  - **Order**: Codex first, then Composer, then Claude (unless task clearly favors another order)
+  - **Consider**: Subtask count, description complexity, integration needs
+  - **Effort**: low (1-3 subtasks), medium (4-6), high (7+ or complex)
+  - **VERSIONS**: Do a quick web search for current Codex, Composer, Claude model versions before generating; include them in the output. If search fails or is unclear, use model names only.
+
+- **Dependency Inference Rules:**
+  - Sequential order: Task 2 often depends on 1, Task 3 on 2, etc.
+  - Semantic analysis: If task mentions "using X from task Y" or similar, add dependency
+  - Independent tasks: Can mark as "nenhuma dependência" or "none" to enable parallelization
+
+- **Natural Language Phrases:**
+  - **FAST FORMAT**: `task-flow: generate flow` or `task-flow generate flow`
+  - "generate flow", "gerar flow", "flow", "gerar tasks.flow"
+  - Any variation asking to generate/populate the task flow
+
+- **Integration:**
+  - Uses data from `.task-flow/.internal/tasks.json`
+  - Writes to `.task-flow/tasks.flow.md` (created by `rbin-task-flow init`)
+  - Does NOT run on `task-flow: sync` — only when user explicitly requests `task-flow: generate flow`
+  - Works with [task_execution.mdc](mdc:.cursor/rules/task_execution.mdc) workflow
+
+- **Principle:**
+  > **Populate tasks.flow.md with dependencies (for parallelization), estimated hours for billing (dev mediano), and AI model recommendations in order. Enable users to decide which tasks can run in parallel, how many hours to charge the client, and which model/effort to use for each.**

package/.task-flow/README.md

@@ -15,6 +15,7 @@
 | `task-flow: refactor X` | Refactors specific task(s) (e.g., `task-flow: refactor 1` or `task-flow: refactor 10,11` or `task-flow: refactor all`) |
 | `task-flow: estimate X` | Estimates time for task X (e.g., `task-flow: estimate 1` or `task-flow: estimate 10,11`) |
 | `task-flow: report X` | Generates implementation report for task X (e.g., `task-flow: report 1` or `task-flow: report 10,11`) |
+| `task-flow: generate flow` | Populates tasks.flow.md with dependencies, estimated hours, and AI model recommendations |
 | `task-flow: audit` | Audits codebase against coding standards and suggests incremental improvements |
 | `task-flow: check` | Run lint fix (if available) and build; fix any warnings or errors until both pass |
 | `task-flow: improve changes` | Audit only uncommitted files against coding standards (same as audit, restricted to current change set) |
@@ -106,6 +107,9 @@ Estimates time required to complete task(s) based on the number of subtasks and
 - `task-flow: estimate 10,11` → Shows time estimates for tasks 10 and 11
 - `task-flow: estimate all` → Shows time estimates for all tasks
 
+### `task-flow: generate flow`
+Populates `tasks.flow.md` with: (1) task dependencies (for parallelization), (2) estimated hours, and (3) AI model recommendations (Codex, Composer, Claude) with effort levels. Run after `task-flow: sync` when you want to know which tasks can run in parallel and which model/effort to use.
+
 ### `task-flow: report X` (simplified syntax)
 Generates a detailed implementation report for completed task(s) in Markdown format.
 
@@ -129,4 +133,5 @@ Generates a detailed implementation report for completed task(s) in Markdown for
 
 - `.task-flow/tasks.input.txt` - Edit tasks here (format: `- Task description`)
 - `.task-flow/tasks.status.md` - ⚠️ **DO NOT EDIT** - Automatically updated by AI
+- `.task-flow/tasks.flow.md` - Dependencies, estimated hours, and model recommendations (populated by `task-flow: generate flow`)
 - `.task-flow/.internal/` - ⚠️ **IGNORE** - Internal system files (no need to read or edit)

package/AGENTS.md

@@ -29,7 +29,7 @@ This repo follows the same development norms as in `.cursor/rules/` and `CLAUDE.
 - **Task flow** always means **RBIN Task Flow**.
 - Tasks: `.task-flow/tasks.input.txt` (format: `- Task description`).
 - Status: `.task-flow/tasks.status.md` and `.task-flow/.internal/status.json`.
-- **Commands** to support: `task-flow: sync`, `task-flow: think`, `task-flow: audit`, `task-flow: check`, `task-flow: improve changes`, `task-flow: status`, `task-flow: run next X`, `task-flow: run X` (or `X,Y` / `all`), `task-flow: review X`, `task-flow: refactor X`, `task-flow: estimate X`, `task-flow: report X`.
+- **Commands** to support: `task-flow: sync`, `task-flow: think`, `task-flow: audit`, `task-flow: check`, `task-flow: improve changes`, `task-flow: status`, `task-flow: run next X`, `task-flow: run X` (or `X,Y` / `all`), `task-flow: review X`, `task-flow: refactor X`, `task-flow: estimate X`, `task-flow: report X`, `task-flow: generate flow`.
 - When running `task-flow: audit`: scan the codebase, score it against `.cursor/rules/coding_standards.mdc`, present a report, and ask the user which improvements to adopt — never impose changes.
 - When running `task-flow: check`: run lint fix if present and fix lint warnings/errors; run build and fix until it passes.
 - When running `task-flow: improve changes`: same as audit but only for files changed and not yet committed (obtain list via `git diff --name-only HEAD`, then audit only those paths).

package/CLAUDE.md

@@ -37,9 +37,11 @@ This project uses RBIN Task Flow for task management:
   - `task-flow: report X` - Generate implementation report for task X (simplified - no "task" needed)
   - `task-flow: report X,Y` - Generate reports for multiple tasks (comma-separated)
   - `task-flow: report all` - Generate reports for all tasks
+  - `task-flow: generate flow` - Populate tasks.flow.md with dependencies, estimated hours (mid-level dev, billing), and AI model recommendations
 - **Files**:
   - `.task-flow/tasks.input.txt` - Define your tasks here
   - `.task-flow/tasks.status.md` - Auto-generated status (DO NOT EDIT manually)
+  - `.task-flow/tasks.flow.md` - Dependencies, estimated hours (mid-level dev, billing), and model recommendations (populated by `task-flow: generate flow`)
   - `.task-flow/.internal/` - Internal system files (ignore)
 
 Follow all rules defined in `.cursor/rules/` for consistent development practices.

package/lib/install.js

@@ -141,7 +141,18 @@ async function copyTaskFlow(targetPath) {
   });
 
   await fs.ensureDir(path.join(taskFlowDest, 'contexts'));
-  await fs.ensureDir(path.join(taskFlowDest, 'docs'));
+
+  const flowPath = path.join(taskFlowDest, 'tasks.flow.md');
+  if (!fs.existsSync(flowPath)) {
+    const flowStub = [
+      '# Task Flow — Dependencies, Hours & Model Recommendations',
+      '',
+      '<!-- Populated by task-flow: generate flow. Do not edit manually. -->',
+      '<!-- Horas: dev mediano (3-5 anos), uso para cobrança ao cliente -->',
+      '',
+    ].join('\n');
+    await fs.writeFile(flowPath, flowStub);
+  }
 
   showSuccess('Task Flow directory (overwritten)');
   showInfo('Protected: .internal/ (your task data is safe)');

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "rbin-task-flow",
-  "version": "1.18.1",
+  "version": "1.19.1",
   "description": "AI-powered task management for Claude and Cursor",
   "main": "index.js",
   "bin": {
@@ -18,7 +18,9 @@
     "cursor",
     "cli",
     "task-management",
-    "ai-powered"
+    "ai-powered",
+    "generate-flow",
+    "tasks-flow"
   ],
   "author": "Rubens de Oliveira",
   "license": "MIT",